1a263d3e088e0cc47b111185579d0d8699b8d190: Bug 1466118 part 7 - Avoid a TLS lookup for each compartment check. r=jonco
Jan de Mooij <jdemooij@mozilla.com> - Tue, 21 Aug 2018 12:58:58 +0200 - rev 488143
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1466118 part 7 - Avoid a TLS lookup for each compartment check. r=jonco
ff5cb8442b5d452de5677dbacf9bec9df0bf5a83: Bug 1466118 part 6 - Rename CompartmentChecker to ContextChecks and support realm checks. r=luke
Jan de Mooij <jdemooij@mozilla.com> - Tue, 21 Aug 2018 12:48:03 +0200 - rev 488142
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1466118 part 6 - Rename CompartmentChecker to ContextChecks and support realm checks. r=luke
af49f7a464d573a7008a301b315bd4303996e320: Bug 1466118 part 5 - Replace assertSameCompartmentImpl with JSContext::checkImpl. r=luke
Jan de Mooij <jdemooij@mozilla.com> - Tue, 21 Aug 2018 12:34:18 +0200 - rev 488141
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1466118 part 5 - Replace assertSameCompartmentImpl with JSContext::checkImpl. r=luke
239b363ac50deb1431607b87ede33c918a45a969: Bug 1466118 part 4 - Replace assertSameCompartment with JSContext::check. r=luke
Jan de Mooij <jdemooij@mozilla.com> - Tue, 21 Aug 2018 12:18:21 +0200 - rev 488140
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1466118 part 4 - Replace assertSameCompartment with JSContext::check. r=luke
224b09c2e661110abc9d29c7cca417cb5de5d3b4: Bug 1466118 part 3 - Replace assertSameCompartmentDebugOnly with JSContext::debugOnlyCheck. r=luke
Jan de Mooij <jdemooij@mozilla.com> - Tue, 21 Aug 2018 12:11:52 +0200 - rev 488139
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1466118 part 3 - Replace assertSameCompartmentDebugOnly with JSContext::debugOnlyCheck. r=luke
5cb4cd7c449ecef9226496dc736d7c7325d37473: Bug 1466118 part 2 - Replace releaseAssertSameCompartment with JSContext::releaseCheck. r=luke
Jan de Mooij <jdemooij@mozilla.com> - Tue, 21 Aug 2018 12:07:57 +0200 - rev 488138
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1466118 part 2 - Replace releaseAssertSameCompartment with JSContext::releaseCheck. r=luke
3bf5eb6fe16d1fa91924edc63da909f1b96d1307: Bug 1466118 part 1 - Use variadic templates for assertSameCompartment functions. r=luke
Jan de Mooij <jdemooij@mozilla.com> - Tue, 21 Aug 2018 11:57:49 +0200 - rev 488137
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1466118 part 1 - Use variadic templates for assertSameCompartment functions. r=luke
6c1dc2168514885e6ddf1686d594bd5c555942e9: Bug 1485564 - [wdspec] Re-enable webdriver/tests/minimize_window/user_prompts.py. r=ato
Henrik Skupin <mail@hskupin.info> - Thu, 23 Aug 2018 08:26:19 +0200 - rev 488136
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1485564 - [wdspec] Re-enable webdriver/tests/minimize_window/user_prompts.py. r=ato
1554e5028374930099178f6b6c0549ce89519967: Bug 1418971 - Add Bug 1363233 test case. r=me
Nicolas B. Pierron <nicolas.b.pierron@gmail.com> - Wed, 25 Jul 2018 13:05:15 +0000 - rev 488135
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1418971 - Add Bug 1363233 test case. r=me
c98c8c9888639e1827c525f715986c57e3a18c54: Merge mozilla-central to inbound. a=merge CLOSED TREE
Gurzau Raul <rgurzau@mozilla.com> - Thu, 23 Aug 2018 12:45:44 +0300 - rev 488134
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Merge mozilla-central to inbound. a=merge CLOSED TREE
d9d4bf8a92b36bb8ebadbaecf951e4bfa268d877: Bug 1470490 - Introduce Atomics.notify, make Atomics.wake an alias. r=anba
Lars T Hansen <lhansen@mozilla.com> - Sat, 18 Aug 2018 13:31:38 +0200 - rev 488133
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1470490 - Introduce Atomics.notify, make Atomics.wake an alias. r=anba TC39 has decided to rename Atomics.wake as the more conventional Atomics.notify. The webcompat fallout from this should be roughly zero, as browser currently have disabled SAB as a result of the Spectre kerfuffle. This patch introduces Atomics.notify, and changes a number of names in the code and in test cases as a result, but retains Atomics.wake as an alias until we're happy that we don't need it. A note on nomenclature used in the code: Though Atomics.notify /notifies/ the target agent, we still say that the agent was /woken/ by the notification if it becomes schedulable. An agent can be notified without being woken in obscure implementation-specific settings, normally having to do with waiting in interrupt handlers. Also fixes a completely blatant and impossible-not-to-discover bug in tests/shell/futex.js. Do we never run shell tests marked "slow"? This makes me nervous.
e2b35cf75610a77c6470b370118cbd0517069718: Bug 1480725 - stress test wasm atomics. r=luke
Lars T Hansen <lhansen@mozilla.com> - Thu, 09 Aug 2018 15:47:30 +0200 - rev 488132
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1480725 - stress test wasm atomics. r=luke Atomic operations are stress-tested by having multiple workers work on the same location in ways that would reveal non-atomicity in an incorrect result. We run these tests only on native implementations, not on simulators. Our simulators don't implement atomicity well. This patch has the bare minimum, testing multiple agents that perform the same operation. It's possible to do more, notably, to combine different operations.
aa3d1b33b0e94e6dae117d2e32e5cd007debd36a: Bug 1467632 - Specialize ReadScalar<ExprType>. r=luke
Lars T Hansen <lhansen@mozilla.com> - Tue, 21 Aug 2018 09:17:05 +0200 - rev 488131
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1467632 - Specialize ReadScalar<ExprType>. r=luke Normally ReadScalar uses memcpy from the source stream to the destination object. This is only well-defined if the destination argument is a POD type, which ExprType is not. So specialize ReadScalar for ExprType and make the memcpy target the data payload in that type instead.
a0883c99c897122286c6e1711cada83d9889e093: Bug 1467632 - Make AsmJSGlobal's pod field be POD. r=luke, r=waldo
Lars T Hansen <lhansen@mozilla.com> - Mon, 20 Aug 2018 17:14:19 +0200 - rev 488130
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1467632 - Make AsmJSGlobal's pod field be POD. r=luke, r=waldo The pod member needs to be POD but has members that have evolved no longer to be POD - a ValType and a LitVal. We work around the problem locally by using ValType's representation type PackedTypeCode to represent types, and by specializing LitVal as LitValPOD for use in this structure.
7e7cfbc863e6dd839f31c8d1b4cca3c04b254f5c: Bug 1480572, r=adw,felipe
Gijs Kruitbosch <gijskruitbosch@gmail.com> - Wed, 22 Aug 2018 23:48:14 +0100 - rev 488129
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1480572, r=adw,felipe
a5f23c113987a3e682b2445016709bebca8eb264: Bug 1388973 - Disabled browser_tab_dragdrop.js on Linux, OSX and Win10 asan. r=jmaher
Natalia Csoregi <ncsoregi@mozilla.com> - Thu, 23 Aug 2018 01:27:00 +0300 - rev 488128
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1388973 - Disabled browser_tab_dragdrop.js on Linux, OSX and Win10 asan. r=jmaher
7b78aeca32ed9b21e11e7ff76be8743aced52408: Merge autoland to mozilla-central. a=merge
Cosmin Sabou <csabou@mozilla.com> - Fri, 24 Aug 2018 00:38:43 +0300 - rev 488127
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Merge autoland to mozilla-central. a=merge
77c50281ad2b074a52797cba560444a5585d339c: Bug 1485702 - Remove unused WalkerFront.search's selectorsOnly argument. r=gl
Alexandre Poirot <poirot.alex@gmail.com> - Thu, 23 Aug 2018 15:36:48 +0000 - rev 488126
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1485702 - Remove unused WalkerFront.search's selectorsOnly argument. r=gl Differential Revision: https://phabricator.services.mozilla.com/D4089
0503d6eb70a76db7a941202ae05e1bfc448714b2: Bug 1467352 - Fix test_ext_storage_telemetry intermittency on win64-ccov. r=mixedpuppy
Luca Greco <lgreco@mozilla.com> - Thu, 23 Aug 2018 17:50:50 +0000 - rev 488125
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1467352 - Fix test_ext_storage_telemetry intermittency on win64-ccov. r=mixedpuppy I've been unable to reproduce this intermittent locally (even by creating a "win64 ccov debug" build on Windows 10), but it has been easy enough to trigger on try. The failure is triggered when the test has been completed and it is unloading the test extension1, by the `NS_ERROR_FILE_ACCESS_DENIED` error raised from Extension's `cleanupGeneratedFile` (https://searchfox.org/mozilla-central/rev/f2ac80ab7dbde5400a3400d463e07331194dec94/toolkit/components/extensions/Extension.jsm#1835-1841). By comparing the test behavior when it runs successfully locally and fails on try, I've been finally able to identify what goes wrong when it fails: The reason for the `NS_ERROR_FILE_ACCESS_DENIED` is the ScriptCache entry for the test extension1's content script, which is created when we create and load the test content page which triggers it, this script cache entry should be cleared when the extension shutdown (and it is cleared when the test runs successfully) Then, right after the content script is executed, the contentPage is closed and this is where something goes (intermittently) wrong with the ipc (and the following pipe errors may be related to it: https://treeherder.mozilla.org/logviewer.html#?job_id=194750915&repo=mozilla-central&lineNumber=2692-2702) and, because of that, during the extension shutdown the "Extension:Shutdown" message broadcasted to all the process never reaches the process where the content script cache entry has been created (as well as "Extension:FlushJarCache" message sent to ensure that the jar cache is flushed in every process), and so the XPI file is still kept active by that process and so it fails to be removed on windows (where the usual `NS_ERROR_FILE_ACCESS_DENIED` is raised in this kind of scenarios). The underlying issue doesn't seem to be strictly related to the behavior that this test file is verifying (that is "checking that the expected telemetry data is being collected when the storage APIs are being used"), and so I think that it would be reasonable to prevent the intermittent by fixing the test (and closing the page after we unload the test extension 1 is enough to ensure that the script cache entry is always cleared as expected and the file can be removed successfully when the test is exiting). The following push to try seems to confirm it (the oranges are triggered by another unrelated test which fails intermittently in win64 ccov builds): - https://treeherder.mozilla.org/#/jobs?repo=try&revision=978e21c57ef084c4115703bf827306320e81bcad Differential Revision: https://phabricator.services.mozilla.com/D4067
a56e76cb2c022213a7bbaa74d32521c2a540600f: Bug 1480494 - Update tup toolchain to e948a999a38fefa0ac0d92f6357f82aca2f9cb17; r=chmanchester
Mike Shal <mshal@mozilla.com> - Thu, 23 Aug 2018 16:58:29 +0000 - rev 488124
Push 9719 by ffxbld-merge at Fri, 24 Aug 2018 17:49:46 +0000
Bug 1480494 - Update tup toolchain to e948a999a38fefa0ac0d92f6357f82aca2f9cb17; r=chmanchester This includes a fix for the style build script hang where pthreads fork subprocesses, as well as a fix for ignoring the icecream file lock. MozReview-Commit-ID: 29eNcbNtwB1 Differential Revision: https://phabricator.services.mozilla.com/D4139
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip