Changes:
Update `linux64` regex to in yaml files for suites that have been migrated over to run on ubuntu1804.
Current naming convention: `linux64-asan/opt`.
New naming convention: `linux1804-64-asan/opt`
Future (potential) convention: `linux2004-64-asan/opt`
Using the `linux.*64` regex will result in a match for all three of the names above. This will ensure that we don't need to constantly update the regex for each new version, while being specific enough.
Differential Revision: https://phabricator.services.mozilla.com/D59572
--HG--
extra : moz-landing-system : lando
This also removes the `name` field from FOR_EACH_OPCODE. Disassembly now uses
the UpperCamelCase opcode name.
A few tests look at disassembler output.
Differential Revision: https://phabricator.services.mozilla.com/D59809
--HG--
extra : moz-landing-system : lando
The comment about JSOP_GLOBALTHIS and JSOP_FUNCTIONTHIS may never have been
sensible; JSOP_FUNCTIONTHIS never walks the environment chain, as it is used
only in non-arrow functions, which take `this` as an argument in the CallArgs.
JSOP_LOOPENTRY and JSOP_TRACE are gone. So is JSOP_SPREAD.
"JSOP_POPs" was eccentric in a way that would be unclear with CamelCase.
Differential Revision: https://phabricator.services.mozilla.com/D59799
--HG--
extra : moz-landing-system : lando
baseDomain is used as a key for cookies in a hashmap. For cookie
operations to work properly, the baseDomain generation must be stable.
This is however not the case, because the result can change by updates
to the public suffix list.
Since the stored baseDomain is not reliable, the value must be
recomputed when the database is read.
Differential Revision: https://phabricator.services.mozilla.com/D59430
--HG--
extra : moz-landing-system : lando
The new opcode names are like `JSOp::InitHiddenProp`. This patch creates
aliases with all of the old names, like `JSOP_INITHIDDENPROP`, to keep existing
code working.
Differential Revision: https://phabricator.services.mozilla.com/D59363
--HG--
extra : moz-landing-system : lando
The snake-case identifiers will be handy in Rust. The plan is to write a script
to import FOR_EACH_OPCODE as a similar Rust macro.
Differential Revision: https://phabricator.services.mozilla.com/D59362
--HG--
extra : moz-landing-system : lando
The change to PendingEdge is OK because this default value is never used; the
field's accessor asserts that *this was created using one of the constructors
that requires an explicit JSOp from the caller.
Differential Revision: https://phabricator.services.mozilla.com/D59361
--HG--
extra : moz-landing-system : lando
Later we will turn JSOp into an enum class that requires these casts.
In places where we are overwriting a previously written bytecode,
this casts to jsbytecode rather than uint8_t, following the prevailing
style.
Differential Revision: https://phabricator.services.mozilla.com/D59359
--HG--
extra : moz-landing-system : lando
Move all mochitest, crashtests, and plain reftests currently running on android-hw-p2
against arm7 builds to aarch64 builds (the great majority of geckoview users on P2 are
now using aarch64 builds -- we want to stay relevant). jittest and jsreftest continue
to run on arm7, providing essential arm7 support; aarch64 coverage continues to be
provided by SM(p) on Windows/aarch64 laptops.
Differential Revision: https://phabricator.services.mozilla.com/D59804
--HG--
extra : moz-landing-system : lando
Do not include the problematic manifest on Android. We never run Android
mochitest-browser-chrome anyway. Bug 1435429 and bug 1557417 used a similar approach.
Differential Revision: https://phabricator.services.mozilla.com/D59828
--HG--
extra : moz-landing-system : lando
The WebExtensionInspectedWindow front is modified in order
to be able to parse the eval response.
We're doing it in a similar fashion to the other fronts methods
that can return ObjectFronts: everything is handled client side,
by the front, since an evaluation result can return primitive values,
long string or grips, and we can't define this through protocol.js in
a readable manner.
Some functions and a component are renamed to better represent
what they're doing.
Differential Revision: https://phabricator.services.mozilla.com/D58939
--HG--
rename : devtools/client/inspector/extensions/components/ObjectValueGripView.js => devtools/client/inspector/extensions/components/ExpressionResultView.js
extra : moz-landing-system : lando
- Use MOZ_GTK_HEADERBAR_WINDOW to get decoration style at moz_gtk_header_bar_paint()
- Don't return decoration size for solid-csd as it behaves as a regular window frame.
Depends on D59850
Differential Revision: https://phabricator.services.mozilla.com/D59851
--HG--
extra : moz-landing-system : lando
This patch reverts the `requestLongerTimeout` change for the failing test (`start-service-worker`), and disables the test on asan (all platforms) and when the sw refactor is not enabled
Differential Revision: https://phabricator.services.mozilla.com/D59844
--HG--
extra : moz-landing-system : lando
- Create header bar at GTK_WINDOW_TOPLEVEL
- Use actual header bar widget as window titlebar because gtk_window_set_titlebar() sets "csd" and "solid-csd" styles.
We need to read the styles to get correct decoration type.
Differential Revision: https://phabricator.services.mozilla.com/D59850
--HG--
extra : moz-landing-system : lando
This can be very useful when investigating an
issue happening in CodeMirror.
The build script was broken due to the usage
of absolute paths; this is fixed by adding
a resolve.modules entry in the webpack config.
Differential Revision: https://phabricator.services.mozilla.com/D59843
--HG--
extra : moz-landing-system : lando
Instead, subclass nsTextControlFrame. This simplifies the code and avoids
correctness issues.
I kept the localization functionality though it is not spec compliant. But I
filed a bug to remove it in a followup.
Differential Revision: https://phabricator.services.mozilla.com/D57193
--HG--
extra : moz-landing-system : lando
Carry forward several media telemetry probes that the media team wishes to
continue monitoring. The probes are:
- MEDIA_MKV_CANPLAY_REQUESTED - allows us to monitor if sites are trying to play
mkv files which guides if we should improve support for such files.
- WEBVTT_TRACK_KINDS - allows us to monitor how webvtt is being used and guide
if we should dedicate more resources to areas of webvtt.
- WEB_AUDIO_BECOMES_AUDIBLE_TIME - allows us to monitor if sites are using
resources on audio context that are playing audio and guide if we need to
improve perf for such cases.
- AUTOPLAY_DEFAULT_SETTING_CHANGE - allows us to monitor if users are opting out
of our default autoplay behaviour.
The following probes are kept to help assess playback performance:
- VIDEO_INFERRED_DECODE_SUSPEND_PERCENTAGE
- VIDEO_INTER_KEYFRAME_MAX_MS.
- VIDEO_SUSPEND_RECOVERY_TIME_MS
- VIDEO_VP9_BENCHMARK_FPS
Differential Revision: https://phabricator.services.mozilla.com/D59436
--HG--
extra : moz-landing-system : lando
This is covered in other test suites, but it may be possible for
GeckoView to get this wrong, so add an explicit test.
Differential Revision: https://phabricator.services.mozilla.com/D59935
--HG--
extra : moz-landing-system : lando
This change introduces a content script, fxr-content.js, that runs in content processes associated with an FxR PC window. This new script notifies observers of "tab-content-frameloader-created", which allows for WebExtensions content script to be injected into the content process.
Differential Revision: https://phabricator.services.mozilla.com/D59887
--HG--
extra : moz-landing-system : lando