Changes:
- apply an explicit increase in the number of xorg client count to 2048.
- remove the custom.conf file as it was not making any difference in the behavior of the docker image.
Differential Revision: https://phabricator.services.mozilla.com/D76897
This is the logic of tracing the WebGPU API calls at the level of wgpu-core,
serialized into a folder of choosing on the user drive. Traces are extremely portable,
they can be shared (on BugZilla) and then replayed on the developer machine,
which can have a different architecture from the users machine.
The standalone player is introduced in `gfx/wgpu/player`, similar to WebRender's Wrench.
The output dir is controlled by "dom.webgpu.traceDir" pref. No tracing happens if it's empty.
Differential Revision: https://phabricator.services.mozilla.com/D73333
The original patch add `run-on-projects` to `TEST_VARIANTS`, but nothing
currently looks at that. Move it into a `replace` block, which gets merged with
the task definition.
This is enough to handle this specific change, but if more control is needed
per-test, we should revisit how this is handled. Fission supports
`fission-run-on-projects` and `fission-tier` to override those values based on
the variants, but it would probably make sense to generalize those to have more
general way of specifying variant-specific configuration.
Differential Revision: https://phabricator.services.mozilla.com/D76772
This patch attempts to fix the long-running customv8 toolchain tasks by adding a --force to the `fetch v8` call. This additional option prevents `fetch` from checking for existing .gclient files (which should never exist) to help with the long delay we are seeing in this call.
Differential Revision: https://phabricator.services.mozilla.com/D76857
This patch enables a new cron job that runs our recorded sites as live sites once a week through browsertime so we can continuously monitor how well our recordings match with what page the user is seeing.
Differential Revision: https://phabricator.services.mozilla.com/D75575
This allows tasks to opt into dynamic chunking. This means rather than define
the chunks ahead of time, in-tree manifest runtime data is used to guess how
many chunks are needed for a reasonable average task runtime (currently 20
min).
Only suites that are chunked in the taskgraph, and therefore whose manifests
are known ahead of time, can opt into this feature.
Differential Revision: https://phabricator.services.mozilla.com/D76497
This updates the task definition for the win64 searchfox job to closely match
the win64/debug task definition in taskcluster/ci/build/windows.yml. So, instead
of running the build with the mozsearch-plugin on a windows worker, it runs
on a Linux worker and does a cross-compile of windows code. The end result in
terms of searchfox artifacts is equivalent, except for absolute filename paths.
I verified that with mozsearch/mozsearch#299 and mozsearch/mozsearch-mozilla#87
in place, searchfox correctly indexes windows-only C++ and Rust code.
Differential Revision: https://phabricator.services.mozilla.com/D76721
Changes:
- permit existing code in chunking.py and mochitests/runtests.py to load manifest runtime information specifict to the suite
Differential Revision: https://phabricator.services.mozilla.com/D75592
CLOSED TREE
Backed out changeset 93efb53380c2 (bug 1637463)
Backed out changeset 5c8ccda5f1b1 (bug 1637463)
Backed out changeset a5fc1b604238 (bug 1637463)
Changes:
- permit existing code in chunking.py and mochitests/runtests.py to load manifest runtime information specifict to the suite
Differential Revision: https://phabricator.services.mozilla.com/D75592
Tested by running the following code and verifying that the script runs
successfully and generates a reasonable diff with the latest metadata
and matching attachment content:
```
$ cd taskcluster/docker/periodic-updates/
$ tar -czf- -s "#$(git rev-parse --show-cdup)#topsrcdir/#" . $(awk -v d="$(git rev-parse --show-cdup)" '/^# %include/{print d$3}' Dockerfile) | docker build - -t hsts-local
$ docker run -e DO_REMOTE_SETTINGS=1 -e PRODUCT="firefox" -e BRANCH="mozilla-central" -e USE_MOZILLA_CENTRAL=1 hsts-local
```
After that, I opened a shell in the container, built Firefox and ran the
following test, to confirm that the updated records are used correctly:
```
mach test toolkit/mozapps/extensions/test/xpcshell/rs-blocklist/test_blocklist_mlbf_dump.js
```
Differential Revision: https://phabricator.services.mozilla.com/D76158
We originally switched it to use just `public/` becuase iscript broke with the
extra path, but that broke out-of-tree consumers. Now that iscript is fixed,
switch it back.
Differential Revision: https://phabricator.services.mozilla.com/D76409
This sets things up to be a little bit easier and cleaner to modify going
forward. The taskgraph before/after this change is identical.
Differential Revision: https://phabricator.services.mozilla.com/D74452
This patch disables the majority of browsertime desktop tests. First, we disable all of the tests on autoland so no more browsertime tests run there. These benchmark tests that were running there will be enabled on mozilla-central along with the rest of the tests. Finally, all browsertime tests will be further restricted to running on the linx64-shippable platform.
Differential Revision: https://phabricator.services.mozilla.com/D76212
For shippable builds on non-release branches, mozharness defaults to using
`nightly-{project}`. The update channel is encoded in the artifact filenames
for non release-channel builds, so update taskgraph to generate the correct
artifact names on non-release branches.
Differential Revision: https://phabricator.services.mozilla.com/D76274
repack_rust.py was the only toolchain build using a python script directly. we
don't need it to use the `mach python` wrapper, so remove that special casing
from the transform.
Differential Revision: https://phabricator.services.mozilla.com/D75702
