5382cec9e30609f76ad88a1fe6150e1c589b7f3b: Bug 1564724 - Remove the old hand-written StaticPrefList.h. r=glandium
Nicholas Nethercote <nnethercote@mozilla.com> - Thu, 18 Jul 2019 04:15:55 +0000 - rev 483276
Push 90283 by nnethercote@mozilla.com at Thu, 18 Jul 2019 04:19:41 +0000
Bug 1564724 - Remove the old hand-written StaticPrefList.h. r=glandium Differential Revision: https://phabricator.services.mozilla.com/D37816
468208580c1d7fa9444b825c9c2e8457c3f7d86e: Merge mozilla-central to autoland. a=merge CLOSED TREE
Ciure Andrei <aciure@mozilla.com> - Thu, 18 Jul 2019 06:48:24 +0300 - rev 483275
Push 90282 by aciure@mozilla.com at Thu, 18 Jul 2019 03:48:50 +0000
Merge mozilla-central to autoland. a=merge CLOSED TREE
c05f610525761ddb7f8bed9927f9f9c45bcb507e: Merge inbound to mozilla-central. a=merge
Ciure Andrei <aciure@mozilla.com> - Thu, 18 Jul 2019 06:46:41 +0300 - rev 483274
Push 90282 by aciure@mozilla.com at Thu, 18 Jul 2019 03:48:50 +0000
Merge inbound to mozilla-central. a=merge
bcdcbeb490e137f4d093f63394080917d6cd7ca4: Bug 1566182: Annotate mochitests that fail with Fission enabled. r=mccr8
Kris Maglione <maglione.k@gmail.com> - Mon, 15 Jul 2019 16:19:32 -0700 - rev 483273
Push 90282 by aciure@mozilla.com at Thu, 18 Jul 2019 03:48:50 +0000
Bug 1566182: Annotate mochitests that fail with Fission enabled. r=mccr8 My preference was to annotate most of the failing tests with `fail-if` so that if they start passing, the `fail-if` needs to be removed and they need to keep passing. That doesn't work for tests that timeout, or which trigger failures from their cleanup functions, however, so those tests need skip-if. And tests with fail in their cleanup functions likely leave the browser in an inconsistent state for subsequent tests, anyway, so really should be skipped regardless. There are some remaining tests which still fail because of crashes. I chose not to skip them here, but to fix the crashes in separate bugs instead. Differential Revision: https://phabricator.services.mozilla.com/D38247
1e5438504d0ecfbecaa5b8c614161dced49c55c4: Bug 1567013: Change gen_dll_blocklist_defs.py to use the DLL name for dupe detection; r=bytesized
Aaron Klotz <aklotz@mozilla.com> - Thu, 18 Jul 2019 03:29:45 +0000 - rev 483272
Push 90281 by aklotz@mozilla.com at Thu, 18 Jul 2019 03:30:46 +0000
Bug 1567013: Change gen_dll_blocklist_defs.py to use the DLL name for dupe detection; r=bytesized Differential Revision: https://phabricator.services.mozilla.com/D38423
daf3f25dd398e6925dc00d064600528a2bc75a00: Bug 1566955: Make EnsureMTA fully thread-safe; r=Jamie
Aaron Klotz <aklotz@mozilla.com> - Thu, 18 Jul 2019 00:48:41 +0000 - rev 483271
Push 90280 by aklotz@mozilla.com at Thu, 18 Jul 2019 03:27:59 +0000
Bug 1566955: Make EnsureMTA fully thread-safe; r=Jamie Until now we asserted that EnsureMTA was being called from the main thread unless the current thread was already in the MTA. This patch makes MTA thread initialization thread-safe by using a C++11 "magic static," thus allowing EnsureMTA to be safely invoked from any thread. Differential Revision: https://phabricator.services.mozilla.com/D38422
024783b4dcd4f78175e32355a116af5d900895bc: Bug 1564131 - re-enable syncing of builtin themes. r=rpl
Mark Hammond <mhammond@skippinet.com.au> - Thu, 18 Jul 2019 01:25:50 +0000 - rev 483270
Push 90279 by mhammond@mozilla.com at Thu, 18 Jul 2019 01:26:53 +0000
Bug 1564131 - re-enable syncing of builtin themes. r=rpl Differential Revision: https://phabricator.services.mozilla.com/D37837
8fb19fe327fe0fee91ad13fd18148a0519874b3b: Bug 1566018 - Return the URL of the manifest from manifest validation in object r=Ola,baku
Marcos Cáceres <mcaceres@mozilla.com> - Wed, 17 Jul 2019 14:04:19 +0000 - rev 483269
Push 90278 by mcaceres@mozilla.com at Thu, 18 Jul 2019 01:12:47 +0000
Bug 1566018 - Return the URL of the manifest from manifest validation in object r=Ola,baku returns a moz_manifest_url member when `{checkConformance: true}` Differential Revision: https://phabricator.services.mozilla.com/D38311
2ab78a0e3a04c3aa65b8c3d1022403e5371d858a: Bug 1562437 - Call Mutex::Shutdown when the watchdog thread exits r=nbp
Paul Bone <pbone@mozilla.com> - Wed, 17 Jul 2019 10:02:12 +0000 - rev 483268
Push 90277 by pbone@mozilla.com at Thu, 18 Jul 2019 00:45:12 +0000
Bug 1562437 - Call Mutex::Shutdown when the watchdog thread exits r=nbp Differential Revision: https://phabricator.services.mozilla.com/D38265
f849276c790ba70178e494d47d9a31528426d70f: Bug 1561712 - test for downloads with COOP enabled r=nika
Junior Hsu <juhsu@mozilla.com> - Wed, 17 Jul 2019 23:34:07 +0000 - rev 483267
Push 90276 by juhsu@mozilla.com at Thu, 18 Jul 2019 00:27:53 +0000
Bug 1561712 - test for downloads with COOP enabled r=nika Differential Revision: https://phabricator.services.mozilla.com/D37145
3d0e35ab6850e792933737ac827b08ebd1fa49a6: Bug 1564724 - Generate StaticPrefList.h from StaticPrefList.yaml. r=glandium
Nicholas Nethercote <nnethercote@mozilla.com> - Thu, 18 Jul 2019 00:08:20 +0000 - rev 483266
Push 90275 by nnethercote@mozilla.com at Thu, 18 Jul 2019 00:09:39 +0000
Bug 1564724 - Generate StaticPrefList.h from StaticPrefList.yaml. r=glandium This commit introduces StaticPrefList.yaml, which encodes the same information as StaticPrefList.h. The .yaml file was generated with a script, which is not part of this commit because it only needs to be used once. (I will attach it to the bug, however.) The commit doesn't remove StaticPrefList.h, I will do that in the next commit. (This makes things it easier to rerun the header-to-YAML script if/when necessary.) The commit does modify the comment at the top of StaticPrefList.h; that modified comment can also be seen at the top of StaticPrefList.yaml. This commit also adds a script that converts the YAML to a header file. This script becomes part of the build. I have done my best to verify that the conversion is correct by comparing the original .h file with the one generated from the YAML file. They are identical, modulo removed comments and the processing of preprocessor directives. Differential Revision: https://phabricator.services.mozilla.com/D37526
606676e2dd214e37cee9bae611072918cbd87df7: Bug 1224848 - Attempt to reduce intermittent test failures in the newly added PDF.js `FullZoom` tests by re-ordering the event registrations and zoom calls. r=bdahl
Jonas Jenwald <jonas.jenwald@gmail.com> - Wed, 17 Jul 2019 17:33:49 +0000 - rev 483265
Push 90274 by apavel@mozilla.com at Wed, 17 Jul 2019 23:54:21 +0000
Bug 1224848 - Attempt to reduce intermittent test failures in the newly added PDF.js `FullZoom` tests by re-ordering the event registrations and zoom calls. r=bdahl Differential Revision: https://phabricator.services.mozilla.com/D38289
ba21fb94343458e7019c2239350e69b7de72fcff: Bug 1561650 - Ignore unused modifier keys on keydown events in <tree> r=vporof
Geoff Lankow <geoff@darktrojan.net> - Wed, 17 Jul 2019 13:07:28 +0000 - rev 483264
Push 90273 by geoff@darktrojan.net at Wed, 17 Jul 2019 23:37:08 +0000
Bug 1561650 - Ignore unused modifier keys on keydown events in <tree> r=vporof Differential Revision: https://phabricator.services.mozilla.com/D38248
060374c521b673ac48444b6cff1b8cfd1bc72e50: Bug 1530715 - Run mach vendor rust on a CLOSED TREE. r=bustage
Emilio Cobos Álvarez <emilio@crisal.io> - Thu, 18 Jul 2019 01:20:49 +0200 - rev 483263
Push 90272 by emilio@crisal.io at Wed, 17 Jul 2019 23:22:10 +0000
Bug 1530715 - Run mach vendor rust on a CLOSED TREE. r=bustage
6106cb75019449efa18338250f500a4d3fb00874: Bug 1566899 - Rename js/src/dbg to js/src/debugger for a clearer name that doesn't conflict with some people's long-standing use of dbg as having "debug build object directory" connotations. r=jorendorff
Jeff Walden <jwalden@mit.edu> - Wed, 17 Jul 2019 22:48:46 +0000 - rev 483262
Push 90271 by jwalden@mit.edu at Wed, 17 Jul 2019 22:54:57 +0000
Bug 1566899 - Rename js/src/dbg to js/src/debugger for a clearer name that doesn't conflict with some people's long-standing use of dbg as having "debug build object directory" connotations. r=jorendorff Differential Revision: https://phabricator.services.mozilla.com/D38372
63d7dc4650c30e7c6262c510a6f1041e18d0c054: Bug 1564724 - Tweak StaticPrefList.h. r=glandium
Nicholas Nethercote <nnethercote@mozilla.com> - Wed, 17 Jul 2019 22:36:35 +0000 - rev 483261
Push 90270 by nnethercote@mozilla.com at Wed, 17 Jul 2019 22:44:04 +0000
Bug 1564724 - Tweak StaticPrefList.h. r=glandium Minor things to ease the transition to StaticPrefList.yaml. - Rename apz_touch_drag_enabled() to the correct apz_drag_touch_enabled(), and media_mwf_low_latency_force_disabled() to the correct media_wmf_low_latency_force_disabled(). - Change some trailing C-style comments to C++-style comments. This makes life easier for the script I wrote to convert StaticPrefList.h to StaticPrefList.yaml, which will be used for the next patch. - Avoid comments on #define lines, because they aren't handled in the YAML input. - Convert a multi-line `#if` condition to a single line, because Preprocessor.py doesn't handle multi-line conditions. - Remove one unnecessary `#undef PREF_VALUE` directive. - Move intl.charset.detector.iso2022jp.allowed to the correct section, so the YAML processing script won't complain. - Change an `int` pref to `int32_t`, again so the YAML processing script won't complain. - Change OS_OPENBSD to XP_OPENBSD, because the former isn't defined for preprocessor.py. (It's also only defined in C/C++ when chromium-config.h is included, which isn't always the case.) Differential Revision: https://phabricator.services.mozilla.com/D37815
539bbdbe61483c73f9695ebb6c7a8d8d7b92c8b9: Bug 1566730 - Switch the diffoscope docker image to Debian 10. r=nalexander
Mike Hommey <mh+mozilla@glandium.org> - Wed, 17 Jul 2019 21:54:25 +0000 - rev 483260
Push 90269 by mh@glandium.org at Wed, 17 Jul 2019 22:40:50 +0000
Bug 1566730 - Switch the diffoscope docker image to Debian 10. r=nalexander Differential Revision: https://phabricator.services.mozilla.com/D38274
0e11ebbb3d79189dd96aeddd317f32986b400ca5: Bug 1530715 - P42: Remove unnecessary mutex. r=padenot
Chun-Min Chang <chun.m.chang@gmail.com> - Wed, 10 Jul 2019 08:06:56 +0000 - rev 483259
Push 90268 by archaeopteryx@coole-files.de at Wed, 17 Jul 2019 22:39:46 +0000
Bug 1530715 - P42: Remove unnecessary mutex. r=padenot There are three potential data-race operations that may run at the same time: 1. Data callback and stream reinitialization 2. Data callback and stream destroying 3. Stream reinitialization and stream destroying The case 1 and 2 won't happen as long as the AudioOutputUnitStop is called at the beginning of stream reinitialization and stream destorying. The AudioOutputUnitStop requires to lock a mutex inside CoreAudio framework that is also used by the data callback. Thus, if there is a running callback, which holds the mutex inside CoreAudio framework, when AudioOutputUnitStop is called, then the calling will block the current thread until the data callback ends since it is waiting for the mutex. By calling AudioOutputUnitStop at the beginning of the stream reinitialization and stream destroying, the data race of case 1 and 2 can be avoided. On the other hand, the case 3 won't happen since the stream initialization and destroying is run on the same task queue. The two tasks on the same serial task queue are impossible to be run at the same time. The mutex in AudioUnitStream is unnecessary because it's used for the case 3. Differential Revision: https://phabricator.services.mozilla.com/D34076
cb5ec80eef4653d861fc7def7b34a6331468f28e: Bug 1530715 - P41: Remove OwnedCriticalSection in cubeb stream. r=padenot
Chun-Min Chang <chun.m.chang@gmail.com> - Wed, 10 Jul 2019 08:06:58 +0000 - rev 483258
Push 90268 by archaeopteryx@coole-files.de at Wed, 17 Jul 2019 22:39:46 +0000
Bug 1530715 - P41: Remove OwnedCriticalSection in cubeb stream. r=padenot The custom mutex, OwnedCriticalSection, in the current code comes with the C-to-Rust translation work of cubeb_audiouniut.cpp. Its design is in C style and not fitted well in the Rust. Rust has a better mutex design. In the previous patches, all the data that may be touched on the different threads are moved into a struct wrapped by a Rust mutex. Those data will be touched in the critical sections created by the Rust mutex. Therefore, this custom mutex becomes redundant. It's time to say goodbye to it. Differential Revision: https://phabricator.services.mozilla.com/D34074
0332b07abeca7c976e862fea743b535b90c7532d: Bug 1530715 - P40: Move stream setup and close into a struct within a mutex. r=padenot
Chun-Min Chang <chun.m.chang@gmail.com> - Wed, 10 Jul 2019 08:07:00 +0000 - rev 483257
Push 90268 by archaeopteryx@coole-files.de at Wed, 17 Jul 2019 22:39:46 +0000
Bug 1530715 - P40: Move stream setup and close into a struct within a mutex. r=padenot The core stream data that will be touched on the different threads when the stream is created, reinitialized, destoryed should be used in the critical section. Those core data are initialized in stream-setup and destroyed in stream-close. The stream-setup and stream-close is run in the critical section so they won't be executed at the same time. Currently, the critical section is created by our custom mutex. However, this custom mutex will be removed in the later mutex replacement. Instead of running these two operations in the critical sections created by the custom mutex, they should be moved into a struct wrapped by a standard Rust mutex. As a result, at the end when the custom mutex is removed, these two operations are still in the critical sections that are created by the Rust mutex. Differential Revision: https://phabricator.services.mozilla.com/D34073
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip