Also fixes bug 926980 - load ICU data from an archive file.
Stop invoking ICU's autoconf build system. Instead, have hand-authored
moz.build files under config/external/icu to build what we need. In addition,
we'll commit a pre-built copy of the ICU data file (currently icudt56l.dat)
under config/external/icu/data to avoid having to build ICU host tools to
generate it. config/external/icu/data also contains some assembly files
which can generate an object file containing the ICU data file contents
so that the JS shell (or standalone JS builds) can be linked directly to
the data without having to deal with the external data file. This requires
yasm or GNU as.
Various bits of packaging have been updated to account for the ICU data file.
XPCOM initialization now sets the ICU data directory so ICU can locate its
data file.
The update-icu.sh script has been modified to read the list of C/C++ source
files out of the ICU Makefiles and update `sources.mozbuild` files under
config/external/icu, as well as build a local copy of ICU using its
autoconf build system to generate the ICU data file to be committed in-tree.
MozReview-Commit-ID: 8Pfkzqt6S1W
--HG--
extra : rebase_source : 31426cddddb5543e0191059ba2f2eb069abe7727
BaseMarionetteTestRunner sets up an empty list of test_handlers; however
it is essential for any child class have at least one test_handler,
otherwise the harness is busted. So, I added a test to check that
MarionetteTestRunner sets up the expected test_handlers.
In doing so, I refactor BaseMarionetteTestRunner.__init__ to
split out file i/o into other methods so I can mock them out,
which involves modifying testvars code.
So, I also added a test to make sure the parsing of testvars still
works.
MozReview-Commit-ID: GF5MKy8rN8C
--HG--
extra : rebase_source : eb62a0245848c30d52a75a1b88d6f14c0f890295
extra : histedit_source : 544ad127d177f47b3c439ef4c96cee0ec4a9c160
If the appropriate test_handler isn't available to the runner,
tests specified at the command-line silently omitted. It's possible
for the runner to create an empty test-suite. This patch adds
asserts to detect an empty test-suite early and provide a more
specific error message.
MozReview-Commit-ID: 5XL4XZHCbMu
--HG--
extra : rebase_source : 6cd0443e2ee34f7aabebe41fbc241ad37d60afe8
extra : histedit_source : 4cff2f152b210a9e483fbb39cd506469dd417350
marionette-harness is implemented as a "generic" task and
can be triggered with the following try syntax:
`-p linux64_tc -j marionette-harness -u none -t none`
The Marionette harness tests do not depend on a browser build,
they only exercise Python code.
Add option to testing/docker/desktop-build/bin/build.sh to
execute any in-tree script instead of only `build-linux.sh`.
This feature is used to call
testing/taskcluster/scripts/tester/harness-test-linux.sh, which
in turn executes the mozharness script specified in the environment.
MozReview-Commit-ID: H08v8ow4p8q
--HG--
extra : rebase_source : 0b8caf4c149a7446591808381fc9819ed795bbd5
extra : histedit_source : 191251f01aeee1e683f14d35439aed5eff55c20d
Initial tests for the Marionette Python runner/harness.
MozReview-Commit-ID: 9KSSOOmpzUF
--HG--
extra : rebase_source : 65998f4f67aaed8aa011410fcee5ddfda6b1aa17
extra : histedit_source : 5ecd5ddae826a11ae7f5c89701ee74e9f68682e6
- HW_THREADS doesn't appear to be doing anything.
- USE_ARM_KUSER is not used since bug 675078. This also removes the configure
flag that sets it.
- HAVE_SETBUF and HAVE_SNPRINTF are leftover from bug 944935.
- MOZ_MEMORY_GONK is leftover from bug 804303.
- DEVELOPER_OPTIONS, INTEL_CC, INTEL_CXX, MOZ_ENABLE_QTMOBILITY,
GTK_CONFIG are or even were never used outside configure.
- MOZ_PROFILELOCKING which gradually became a no-op over the years. This
also removes the configure flag that sets it.
- XULRUNNER_STUB_NAME is xulrunner-only, and xulrunner is gone. This
also removes the configure flag that sets it.
- The only use of MOZ_CAN_RUN_PROGRAMS was removed in bug 780561.
- AR_LIST and AR_DELETE have not been used since bug 584474.
- MOZ_COMPONENT_NSPR_LIBS is leftover from bug 1036894.
- MOZ_PNG_ARM_NEON_CHECK is not used since bug 980488.
- MOZ_WEBRTC_LEAKING_TESTS has been no-oped by bug 825510.
- VPX_NEED_OBJ_INT_EXTRACT and NO_INTEGRATED_AS_CFLAGS are not used since
bug 1151175.
- WCHAR_CFLAGS is not used since bug 904985.
In bug 1260996, we straightened things up for the host flags on cross
compile builds, where the situation was that they were effectively empty
by default, and that hasn't changed.
While working on bug 1260996, it has become clear that there is no much
point in setting the host flags from the target flags on non cross
compile builds, especially when the target flags come from the environment.
That creates a discrepancy with cross compilation builds for no real
reason, and there are effectively too few host things to build that it
would matter anyways. The flags that do matter are the ones for C++11,
C99, and optimisations, and they all are set independently of what is
being removed here.
Because closing the handler is not enough (it eventually reopens
itself), the dumping of config.log overwrites the file, and confuses
the process of reading it to dump it in the first place, showing
incomplete logs. The intent from the start was that nothing would be
logged in the FileHandler, so on top of closing it, actively remove it.
