After enabling the perf for SAB by default on Nightly, some jsreftests fail.
And they all have log like:
tests/test262/shell.js:492: Error: Agents not available item 1
It seems that there are some issues on test262 shell, so the plan of this patch
is to disable these tests and open another follow-up ticket to re-enable them.
So that we could check the impact of enable the perf for SAB without enabling
the functionality of being postMessage'ed on Nightly users.
Differential Revision: https://phabricator.services.mozilla.com/D53966
--HG--
extra : moz-landing-system : lando
This patch mainly enables the pref for SharedArrayBuffer on Nightly.
This change causes some tests to fail. This patch handles the failures for
mochitests and web-platform-tests. The jsreftest will be handled in the next
patch.
For mochitests:
- dom/serviceworkers/test/test_serviceworker_interfaces.js
- dom/tests/mochitest/general/test_interfaces.js
- dom/workers/test/test_worker_interfaces.js
These tests check which interfaces are exposed on the web. Since we are now
exposing SharedArrayBuffer in some configurations, the tests need to be adjusted
accordingly.
For the rest of tests in this patch:
- testing/web-platform/meta/encoding/encodeInto.any.js.ini
This test partially fails because the integration of encoding and SAB is not
completely supported yet.
- testing/web-platform/meta/encoding/streams/decode-utf8.any.js.ini
This test partially fails because the integration of decoding and SAB is not
completely supported yet.
- testing/web-platform/meta/html/webappapis/scripting/processing-model-2/integration-with-the-javascript-agent-formalism/requires-failure.https.any.js.ini
- testing/web-platform/meta/html/webappapis/scripting/processing-model-2/integration-with-the-javascript-agent-formalism/requires-success.any.js.ini
- testing/web-platform/meta/wasm/jsapi/memory/constructor.any.js.ini
- testing/web-platform/meta/wasm/jsapi/memory/grow.any.js.ini
The subtests related to SAB in these tests now pass when SAB is enabled, so we
need to annotate them as failing only in configurations where SAB is disabled.
- testing/web-platform/meta/webaudio/the-audio-api/the-audiobuffer-interface/audiobuffer-copy-channel.html.ini
This test partially fails because there are some issues between SAB and Audio.
Differential Revision: https://phabricator.services.mozilla.com/D48838
--HG--
extra : moz-landing-system : lando
Removes calls to the win32k API.
Replaces hardware and event timers with waitable timers.
Removes handling various task objects through the thread message queue.
Removes ProcessQueuedMessages, CancelTimers functions.
Adds event handle for stopping the TaskQueue thread.
Adds ReplyHandler class as an in between for TaskQueue objects to post tasks to each other without worrying if the other TaskQueue remains valid.
Adds rtc::CriticalSection's for timer_tasks_.
Removes ThreadState scoped class.
Differential Revision: https://phabricator.services.mozilla.com/D43480
--HG--
extra : moz-landing-system : lando
This event is currently sent for each and every message,
and as such duplicates every log entry as displayed when
having the Puppeteer debug logs turned on.
Until we can fix it to behave correctly, it should be
disabled.
Differential Revision: https://phabricator.services.mozilla.com/D54273
--HG--
extra : moz-landing-system : lando
The TestRendered event is dispatched for reftests containing a
reftest-wait class on the root at the time the test would complete if
there wasn't such a class. This occurs after the initial paint is
complete, so any dynamic changes can be performed in such a way that
they are not batched with the initial layout/paint.
Differential Revision: https://phabricator.services.mozilla.com/D52684
--HG--
extra : moz-landing-system : lando
This change surfaces errors faster, and ensures that we don't silently
end up with empty crashreporter symbols if `dump_syms` can't run for
some reason.
Differential Revision: https://phabricator.services.mozilla.com/D43520
--HG--
extra : moz-landing-system : lando
+ rename the title as it is used in the menu
Differential Revision: https://phabricator.services.mozilla.com/D54514
--HG--
rename : devtools/docs/SUMMARY.md => devtools/docs/index.md
extra : moz-landing-system : lando
Wrapping one-off buttons into a container confuses layout that lets the richlist
box to grow unconditionally. This problem is already partially visible by
opening the searchbar continuously, sometimes strings are not properly overflowing
with ellipsis, they are just overflowing.
Setting a width on the panel limits its size properly, though this won't fix the
layout sometimes not properly cutting the richlistbox. It's likely there an
underlying bug in the widget or calculations when widgets are not visible.
This also correctly forces showing at least 3 one-off buttons per row, the
existing code is not sufficient for that because search-one-offs.js sets a
max-width that is smaller than 3 buttons.
Similarly, it corrects a calculation in the urlbar one-offs, where we should
show at least 4 buttons, but due to a not considered margin we only show 3.
Finally, this removes a few rules that are not necessary with the current design.
Differential Revision: https://phabricator.services.mozilla.com/D53968
--HG--
extra : moz-landing-system : lando
The name 'templates' originally came from the fact that JSON-e templates were
used to apply the configuration. Now that these no longer exist, the name
doesn't make any sense.
I'm not sure 'task_configs' is much better, but it at least makes sense given
that these are values that populate 'try_task_config.json'.
Differential Revision: https://phabricator.services.mozilla.com/D51418
--HG--
rename : tools/tryselect/templates.py => tools/tryselect/task_config.py
rename : tools/tryselect/test/test_templates.py => tools/tryselect/test/test_task_configs.py
extra : moz-landing-system : lando
Handles 'env' and 'chemspill-prio' configs in the transforms. The 'rebuild'
task config is purposefully excluded from the full_task_graph and instead
handled at the target_tasks stage. Otherwise if a user ran '--rebuild 20' then
retriggered one of those tasks, they'd instead get another 20 which is almost
certainly not what we want.
Differential Revision: https://phabricator.services.mozilla.com/D51417
--HG--
extra : moz-landing-system : lando
Also converts the 'artifact' from a Template to a TryConfig. So this changes the config from:
{
'templates': {
'artifact': {
'enabled': 1
}
}
}
to:
{
'use-artifact-builds': True
}
Differential Revision: https://phabricator.services.mozilla.com/D51416
--HG--
extra : moz-landing-system : lando
These tests are already covered by Web Platform Tests which are run against
other browsers guaranteeing interop where mochitest does not.
Differential Revision: https://phabricator.services.mozilla.com/D54312
--HG--
extra : moz-landing-system : lando
Now that all of the important metaViewport simulation bugs have been fixed, we would
like to let feature ride the trains, enabled by default.
This means we can also stop setting the pref in tests that rely on it.
Differential Revision: https://phabricator.services.mozilla.com/D53005
--HG--
extra : moz-landing-system : lando