* Add a script for running wrench under various software rasterizers.
* Add support to wrench for non-blocking event loop.
* Add support to wrench for selecting GL/ES rendering API.
* Update x11 bindings for wrench, to fix a release only crash.
Differential Revision: https://phabricator.services.mozilla.com/D36551
--HG--
extra : moz-landing-system : lando
Android profile runs don't always fully write out the profile data. In
this case, the corrupted profile data is successfully uploaded, but
future profile-use PGO builds try to merge the data and fail. Retrying
the profile-use builds doesn't help, since they all pull from the same
job that published the corrupt data.
We can detect this in the run task by using llvm-profdata merge, and if
the merge fails the task can automatically be retried. Note that the
data gets redundantly merged in the profile-use build, but it may not be
possible to run the merge in the run task on all platforms (eg: OSX), so
we have to keep the merge there as well.
Differential Revision: https://phabricator.services.mozilla.com/D36294
--HG--
extra : moz-landing-system : lando
* Add a script for running wrench under various software rasterizers.
* Add support to wrench for non-blocking event loop.
* Add support to wrench for selecting GL/ES rendering API.
* Update x11 bindings for wrench, to fix a release only crash.
Differential Revision: https://phabricator.services.mozilla.com/D36551
--HG--
extra : moz-landing-system : lando
This patch copies over the same fix that was used for the profile cleanup page
to the installing page, since in some locales it can run into the same problem
of the header string being so long that it causes the next control to get cut
off by the bottom of the window.
Differential Revision: https://phabricator.services.mozilla.com/D36523
--HG--
extra : moz-landing-system : lando
Giving each logical test its own counter variable will help tests to not
interfere with each other. We also make one infinite looping thread
exit so we're not chewing CPU after these tests finish.
Differential Revision: https://phabricator.services.mozilla.com/D36522
--HG--
extra : moz-landing-system : lando
we save the native fonts by their full path now. On macOS, there is no
such thing as a full filesystem path for a CGFont (or at least we don't track it),
so loading a capture falls back to the old logic of using the dummy font.
Differential Revision: https://phabricator.services.mozilla.com/D36604
--HG--
extra : moz-landing-system : lando
This also implicitly deletes its copy-assignment operator and copy-constructor,
which is great since it's a huge footgun.
Differential Revision: https://phabricator.services.mozilla.com/D36549
--HG--
extra : moz-landing-system : lando
This will display something like:
```
error: static_assert failed due to requirement '528UL <= 504UL' "Style struct became larger than the size limit"
static_assert(Actual <= Limit, "Style struct became larger than the size limit");
^ ~~~~~~~~~~~~~~~
note: in instantiation of template class 'AssertSizeIsLessThan<nsStylePosition, 528, 504>' requested here
STYLE_STRUCT_RESET(Position)
^
note: expanded from macro 'STYLE_STRUCT_RESET'
^
note: expanded from macro 'STYLE_STRUCT'
static_assert(AssertSizeIsLessThan<nsStyle##name_, sizeof(nsStyle##name_), kStyleStructSizeLimit>::instantiate, "");
```
Which includes both the size, the limit, and the struct name, as opposed to the
current:
```
error: static_assert failed due to requirement 'sizeof(nsStylePosition) <= kStyleStructSizeLimit' "nsStylePosition became larger than the size limit"
STYLE_STRUCT_RESET(Position)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
note: expanded from macro 'STYLE_STRUCT_RESET'
^~~~~~~~~~~~~~~~~~
note: expanded from macro 'STYLE_STRUCT'
static_assert(sizeof(nsStyle##name_) <= kStyleStructSizeLimit, \
```
Which only includes the name and thus isn't very useful.
Differential Revision: https://phabricator.services.mozilla.com/D36546
--HG--
extra : moz-landing-system : lando
This patch also fixes the Home and Sidebar Touch Bar buttons, since using them after customizing showed that they no longer worked.
Differential Revision: https://phabricator.services.mozilla.com/D35085
--HG--
extra : moz-landing-system : lando
Because IPC call runs asynchronously in both remote decoder process and
content process, ProcessOutput() for buffers prior to Flush() could be
scheduled to run after the flush promise is resolved, and Codec.queueInput()
could be preempted and processes prior sample after flush.
To help check the validness of buffers, a session ID increased by flush
is added to both RemoteDataDecoder and remote codec service and will be
passed through IPC. If the passed ID doesn't agree with current session
ID, it means the buffer doesn't belong to current session and should be
discard.
Differential Revision: https://phabricator.services.mozilla.com/D36382
--HG--
extra : moz-landing-system : lando
This test will leak one `audio-playback` notification to next test, because when we close this test, we would close iframe and send the `inaudible-pause` notification.
It would somehow affect the following test if the next one is also listening to the `audio-playback` notification.
Differential Revision: https://phabricator.services.mozilla.com/D36534
--HG--
extra : moz-landing-system : lando
In these two files, we didn't set the position or size explicitly for those showing cues, so the size should be default (100%) and the position is `auto`.
Therefore, we should remove incorrect `left` and `size` in the reference file.
Differential Revision: https://phabricator.services.mozilla.com/D34034
--HG--
extra : moz-landing-system : lando
As the default `line-height` (normal) is computed, which would vary depending on different platforms. In these tests, we have to fix the number of showing cues, the varied `line-height` would affect how many lines could be showed in the screen.
Therefore, we use `20px/1 Ahem` to fix the line height and 20px is the minimum requirement for using Ahem based on its guideline.
If we use 20px for each text, then we would have 9 lines showing in the screen (180px/20px), so we can reduce the cue numbers in both vtt file and reference files.
In `too_many_cues.vtt`, the first 9 cues would be displayed and the last one won't. In `too_many_cues_wrapped.vtt` the first 8 cues would be displayed and the last one won't because its text is too long to show in one line.
In addtion, because of increasing the font size, we have to reduce the text number in one line to prevent unnecessary line break.
Differential Revision: https://phabricator.services.mozilla.com/D34033
--HG--
extra : moz-landing-system : lando
Bug 1553065 made this redundant by putting the profile-use mozconfig
settings in build/unix/mozconfig.unix. We no longer need them in each
leaf mozconfig.
Differential Revision: https://phabricator.services.mozilla.com/D36543
--HG--
extra : moz-landing-system : lando
If `./mach browsertime` runs browsertime with a globally-installed node, due to
an existing bug in [execa][1], the wrong Python will be executed. We now
specify the full path of the Python binary we wish to use (via the `PYTHON`
environment variable that our fork of browsertime supports) and avoid this
issue altogether.
[1]: https://github.com/sindresorhus/execa/issues/153
Differential Revision: https://phabricator.services.mozilla.com/D35374
--HG--
extra : moz-landing-system : lando
Ciure Andrei
Glenn Watson
Mike Shal
Jared Hirsch
Andreea Pavel
Andreas Farre
Daniel Holbert
Andrew McCreight
alwu
Matt Howell
Matthew Gaudet
Nathan Froyd
Coroiu Cristina
Daniel Varga
Dzmitry Malyshau
Markus Stange
Emilio Cobos Álvarez
harry
Sean Feng
Jared Wein
Tom Prince
John Lin
Jeane Carlos
Mirko Brodesser
Edwin Gao
Maliha Islam
Jeff Gilbert
Barret Rennie