Some of the variants are multi-platforms, and having
--enable-stdcxx-compat in their definition will break when the option is
moved over to python configure.
While here, prepare for --enable-stdcxx-compat actually doing something
(it currently doesn't), by adding an exception for it in
check_vanilla_allocations.py.
--HG--
extra : rebase_source : ee1647421542209cf0137db703c4f7e7f06cbc91
The only reason autospider builds succeed in running tests at the moment
is that there is a libnspr4 library installed at the system level on
Centos that is binary compatible with what the js shell requires.
While on the long run we should just avoid depending on libnspr4 at all,
in the short term, we should make the effort to make those tests use the
libnspr4 present in dist/bin.
For the tests executed from js/src/Makefile.in, it turns out there is
already a level of wrapping that does that, relying on run-mozilla.sh,
which is only installed on gecko builds. Installing it on standalone js
builds solve half the problem.
The other half is addressed by setting LD_LIBRARY_PATH before invoking
the js shell in the various places it's invoked.
--HG--
extra : rebase_source : 25f4b1f5c78eb84e48046dc83798f07eb02d4a81
This patch fixes several errors in Windows file/path management for
the binjs-decoder jsapi-tests:
- under Windows, files should be explicitly opened as "binary",
otherwise the Windows version of the libc can be creative about
their contents;
- "*.binjs" should not be part of the path;
- I/O functions don't all have the same return value conventions to
notify of an error.
MozReview-Commit-ID: 51rVpRlcUai
--HG--
extra : rebase_source : a7d977c7dc0aecb05c4bbbf4547dedffbd4ec974
This will prevent the test from going permaorange when Gecko 59 merges to Beta.
--HG--
extra : rebase_source : 27a825187cbf27bc6254027ce27681d8730e86b5
Building for some tier-3 platforms imply building without a JIT, and it
happens quite regularly that this setup is broken by API changes in
Spidermonkey.
This adds a new job with JIT disabled, but skip tests for now because
some fail or crash.
--HG--
extra : rebase_source : 3c6e1dfb3cd7d0bff59c494f6230c9f1b55479ed
We need MOZ_UI_LOCALE even when building the JS shell so
config/config.mk variable assignments don't run into issues. But it
doesn't make any sense to configure a UI locale for the JS shell. So
make --enable-ui-locale a normal `option`, but give it a `default`,
which is the value shell-only builds will always see.
--HG--
extra : amend_source : 047759dd6ec446d9d6f8f5992ed9cf6628ce859e
This hook should help us diagnose more easily typoes in our chrome code.
To avoid painting ourselves in a corner in case we need to optimize
exceptions at some later point, the API is restricted to Nightly -
which is where it will be the most useful anyway.
MozReview-Commit-ID: FvDnaALKHox
--HG--
extra : rebase_source : b3cb46b658c0638183fb80fb11f8a50d9aab28d4
Attempting to build Bug 137707 fails with Linux 64 PGO (and only with
Linux 64 PGO) with the following error:
INFO - /builds/worker/workspace/build/src/js/src/irregexp/RegExpEngine.cpp:2326:5: error: assuming signed overflow does not occur when assuming that (X + c) < X is always false [-Werror=strict-overflow]
INFO - for (int i = interval.from(); i <= interval.to(); i++) {
INFO - ^^^
I suspect that this is actually a bug in PGO itself, rather than in
the code. However, replacing `<= interval.to()` with `!= interval.to()
+ 1` seems to do the trick.
MozReview-Commit-ID: IsayKhgkwWq
--HG--
extra : rebase_source : e4f3712b9606177326a00e15102a96c144ec26a8
Some tests need to find out js/src to locate their test
data. Exporting this information as part of the environment.
MozReview-Commit-ID: JAefL2arhJL
--HG--
extra : rebase_source : b99d55c4ab4335ea938d8f3a9c733ea74f02fddf
