mozilla
/
gecko-dev
зеркало из https://github.com/mozilla/gecko-dev.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
gecko-dev/taskcluster/ci/test/xpcshell.yml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

98 строки
3.3 KiB
YAML
Исходник Обычный вид История

Bug 1550816: Enforce consistent indenting in taskcluster yaml; r=aki Differential Revision: https://phabricator.services.mozilla.com/D30684 --HG-- extra : moz-landing-system : lando
2019-05-11 00:19:48 +03:00
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
---
Bug 1410250 - Stop keying entire 'mozharness' section by-test-platform, r=dustin Many of the 'test' tasks key the entire 'mozharness' section by-test-platform. This is bad because: A) Configuration under 'mozharness' can't be shared across platforms B) We can't use the 'job-defaults' simplification since merging is naive Instead of keying the entire 'mozharness' section, this change keys only the specific configuration that needs it. MozReview-Commit-ID: EaPlOzsESQ3 --HG-- extra : rebase_source : 12d81013fd4e18403799c92df06f855bf7162a05
2017-10-19 21:35:04 +03:00
job-defaults:
Bug 1523303 - [taskgraph] Define suite "categories" rather than flavours task configs, r=gbrown Currently we have the concept of a "suite" and a "flavour" in our task configuration. Typically, the "suite" refers to the high-level test harness like "mochitest" or "reftest", whereas the flavour is more specific, e.g "browser-chrome-instrumentation" or "crashtest". However the line between suite and flavour is not applied with any semblance of consistency which results in inconsistent naming throughout the tree. This patch gets rid of the concept of "flavours" entirely (at least when it comes to task configuration). A suite is a type of test run, for example: - mochitest-plain - mochitest-devtools-chrome - mochitest-browser-chrome-instrumentation - jsreftest - reftest - firefox-ui-functional-remote etc There is no confusion here between suites and flavours because flavours don't exist. However, there are a couple of places where we *do* need to know what "test harness" is used to run a suite. These cases are: 1. For SCHEDULES moz.build rules 2. For the desktop_unittest.py mozharness script which takes arguments like --mochitest-suite=browser (this is not a compelling use of this information and should be refactored to work more like the android_emulator_unittest.py script) So to get this information, this patch introduces a new concept of a "category" which is the overall "test harness" that runs the suite. For many suites, the "category" is identical to the suite name. Unlike flavours, "categories" have no bearing on how we call or refer to the suite. Differential Revision: https://phabricator.services.mozilla.com/D27554 --HG-- extra : moz-landing-system : lando
2019-04-22 23:44:01 +03:00
suite: xpcshell
Bug 1539932 - [ci] Handle serviceworker/socketprocess test variants more generically, r=jmaher We are starting to spin off more and more "variants" of test suites. These are usually just duplicates of our pre-existing tasks, except with an additional pref set. Currently there are two variants (serviceworker-e10s and socketprocess-e10s), but a third will be added soon (fission). This change ensures we handle these types of requests in a consistent and well defined manner. It also splits tasks in a loop, so we don't accidentally risk combinatorial explosion. Variants should typically be reserved for very large changes that will impact the entire codebase (think e10s). Differential Revision: https://phabricator.services.mozilla.com/D28061 --HG-- extra : moz-landing-system : lando
2019-04-18 17:40:08 +03:00
variants:
Bug 1470266 - [ci] Schedule serviceworker-e10s xpcshell tasks with linux64/debug on mozilla-central, r=jmaher Differential Revision: https://phabricator.services.mozilla.com/D11380 --HG-- extra : moz-landing-system : lando
2018-11-09 01:08:16 +03:00
by-test-platform:
Bug 1602832 - P2: Create 'socketprocess_networking' test variant r=ahal Differential Revision: https://phabricator.services.mozilla.com/D58112
2020-05-26 17:30:16 +03:00
linux1804-64/debug: ['fission', 'socketprocess_networking']
Bug 1553527 - [ci] Create a new 'fission' test variant r=jmaher Differential Revision: https://phabricator.services.mozilla.com/D32196 --HG-- extra : moz-landing-system : lando
2019-05-24 21:41:01 +03:00
default: ['fission']
Bug 1553225 - Run Android 7.0 xpcshell tests against geckoview apk; r=jmaher Switch the target apk for Android 7.0 xpcshell-test to geckoview. At the same time, update the mach command for local runs to select the geckoview apk rather than the fennec one, by default. Differential Revision: https://phabricator.services.mozilla.com/D42904 --HG-- extra : moz-landing-system : lando
2019-08-21 21:24:08 +03:00
target:
by-test-platform:
android-em-7.*: geckoview-androidTest.apk
default: null
Bug 1601397 - [ci] Refactor fission configuration for more flexability r=jmaher,gbrown This implements a 'fission-run-by-projects' and 'fission-tier' key that mirrors the non-fission versions. We need to duplicate the keys rather than use something like 'by-variant' due to the order that things are processed in the tests.py transforms. These keys should only be temporary until Fission is running the same as non-Fission. In the meantime they will give us greater control over what runs where. The taskgraph generated before and after this change is identical. Differential Revision: https://phabricator.services.mozilla.com/D56211 --HG-- extra : moz-landing-system : lando
2019-12-06 22:55:14 +03:00
fission-tier: 2
Bug 1410250 - Stop keying entire 'mozharness' section by-test-platform, r=dustin Many of the 'test' tasks key the entire 'mozharness' section by-test-platform. This is bad because: A) Configuration under 'mozharness' can't be shared across platforms B) We can't use the 'job-defaults' simplification since merging is naive Instead of keying the entire 'mozharness' section, this change keys only the specific configuration that needs it. MozReview-Commit-ID: EaPlOzsESQ3 --HG-- extra : rebase_source : 12d81013fd4e18403799c92df06f855bf7162a05
2017-10-19 21:35:04 +03:00
mozharness:
script:
by-test-platform:
Bug 1426586 - Rename android emulator test platforms to android-em, r=gbrown
2018-06-23 02:39:31 +03:00
android-em.*: android_emulator_unittest.py
Bug 1410250 - Stop keying entire 'mozharness' section by-test-platform, r=dustin Many of the 'test' tasks key the entire 'mozharness' section by-test-platform. This is bad because: A) Configuration under 'mozharness' can't be shared across platforms B) We can't use the 'job-defaults' simplification since merging is naive Instead of keying the entire 'mozharness' section, this change keys only the specific configuration that needs it. MozReview-Commit-ID: EaPlOzsESQ3 --HG-- extra : rebase_source : 12d81013fd4e18403799c92df06f855bf7162a05
2017-10-19 21:35:04 +03:00
default: desktop_unittest.py
config:
by-test-platform:
Bug 1546553 - Run Android xpcshell tests on 7.0 x86_64; r=jmaher Differential Revision: https://phabricator.services.mozilla.com/D29844 --HG-- extra : moz-landing-system : lando
2019-05-04 01:11:24 +03:00
android-em-7.*:
- android/android_common.py
Bug 1594735 - Upgrade android emulator used for x86_64 xpcshell tests; r=aerickson Upgrade the emulator used by xpcshell tests to 29.2.1, the same version used by all other android tests. We have delayed this upgrade because of intermittent failures seen on the new emulator not seen previously - bug 1568063. After the packet.net upgrade to Ubuntu 18.04, try runs with the new emulator show that bug 1568063 persists but has less impact than the intermittent failures it resolves: More tests pass consistently with the new emulator than with the old. Differential Revision: https://phabricator.services.mozilla.com/D52851 --HG-- extra : moz-landing-system : lando
2019-11-13 20:46:02 +03:00
- android/androidx86_7_0.py
Bug 1410250 - Stop keying entire 'mozharness' section by-test-platform, r=dustin Many of the 'test' tasks key the entire 'mozharness' section by-test-platform. This is bad because: A) Configuration under 'mozharness' can't be shared across platforms B) We can't use the 'job-defaults' simplification since merging is naive Instead of keying the entire 'mozharness' section, this change keys only the specific configuration that needs it. MozReview-Commit-ID: EaPlOzsESQ3 --HG-- extra : rebase_source : 12d81013fd4e18403799c92df06f855bf7162a05
2017-10-19 21:35:04 +03:00
linux.*:
- unittests/linux_unittest.py
- remove_executables.py
macosx.*:
- unittests/mac_unittest.py
windows.*:
Bug 1539847 - [mozharness] Remove unused testing/mozharness/configs/unittests/win_unittest.py, r=tomprince This also renames win_taskcluster_unittest.py to win_unittest.py for consistency with the other platforms. Differential Revision: https://phabricator.services.mozilla.com/D25401 --HG-- extra : moz-landing-system : lando
2019-04-01 19:07:42 +03:00
- unittests/win_unittest.py
Bug 1410250 - Stop keying entire 'mozharness' section by-test-platform, r=dustin Many of the 'test' tasks key the entire 'mozharness' section by-test-platform. This is bad because: A) Configuration under 'mozharness' can't be shared across platforms B) We can't use the 'job-defaults' simplification since merging is naive Instead of keying the entire 'mozharness' section, this change keys only the specific configuration that needs it. MozReview-Commit-ID: EaPlOzsESQ3 --HG-- extra : rebase_source : 12d81013fd4e18403799c92df06f855bf7162a05
2017-10-19 21:35:04 +03:00
requires-signed-builds:
by-test-platform:
windows10-64-asan/opt: false # No XPCShell on ASAN yet
Bug 1475994 - Add tests for the mingw clang build r=jmaher Differential Revision: https://phabricator.services.mozilla.com/D38032 --HG-- extra : moz-landing-system : lando
2019-08-07 19:47:46 +03:00
windows7-32-mingwclang/opt: false
windows7-32-mingwclang/debug: false
windows10-64-mingwclang/opt: false
windows10-64-mingwclang/debug: false
Bug 1410250 - Stop keying entire 'mozharness' section by-test-platform, r=dustin Many of the 'test' tasks key the entire 'mozharness' section by-test-platform. This is bad because: A) Configuration under 'mozharness' can't be shared across platforms B) We can't use the 'job-defaults' simplification since merging is naive Instead of keying the entire 'mozharness' section, this change keys only the specific configuration that needs it. MozReview-Commit-ID: EaPlOzsESQ3 --HG-- extra : rebase_source : 12d81013fd4e18403799c92df06f855bf7162a05
2017-10-19 21:35:04 +03:00
windows.*: true
default: false
Bug 1388478 - Split tests.yml into several smaller suite-specific files, r=dustin,jmaher This is a simple refactor into separate files. No task definitions should be modified by this patch. Most tasks are moved into suite-specific .yml files. A handful of miscellaneous tasks are defined directly in kind.yml under the 'jobs' key. MozReview-Commit-ID: 7piXDA6tGI0 --HG-- extra : rebase_source : a91fbb6d0bf740a28a042470b3f9d4a4e309d1f0
2017-10-17 23:25:41 +03:00
xpcshell:
description: "xpcshell test run"
Bug 1386857 - [ci] Remove the 'tc' treeherder group prefix from all tasks, r=dustin There are now only a handful of buildbot jobs remaining and the concern over outdated treeherder exclusion profiles has largely been resolved. This does remove the tc() group from a substantial number of tasks which will now show up as top level tasks, potentially adding clutter. In some cases, we might want to re-add a new group (e.g group builds or compiled tests together). However rather than try to predict the best group names for tasks I'm unfamiliar with, I think it's best to land this as is. Then if things are looking too cluttered at the root namespace, file follow-up bugs as needed. MozReview-Commit-ID: 8SMwjDwAOzV --HG-- extra : rebase_source : 2f6d89d11c139bdcd404e7537db799d0e36ee4c3
2018-01-12 23:49:58 +03:00
treeherder-symbol: X(X)
Bug 1388478 - Split tests.yml into several smaller suite-specific files, r=dustin,jmaher This is a simple refactor into separate files. No task definitions should be modified by this patch. Most tasks are moved into suite-specific .yml files. A handful of miscellaneous tasks are defined directly in kind.yml under the 'jobs' key. MozReview-Commit-ID: 7piXDA6tGI0 --HG-- extra : rebase_source : a91fbb6d0bf740a28a042470b3f9d4a4e309d1f0
2017-10-17 23:25:41 +03:00
run-on-projects:
by-test-platform:
windows10-64-asan/opt: [] # No XPCShell on ASAN yet
default: built-projects
chunks:
by-test-platform:
Bug 1596279 - Set the same chunk numbers and timeouts for coverage opt builds as in coverage debug builds. r=jmaher In bug 1596368 we will adjust them, after disabling tests in coverage debug builds. Depends on D53000 Differential Revision: https://phabricator.services.mozilla.com/D53001 --HG-- extra : moz-landing-system : lando
2019-11-14 19:20:24 +03:00
.*-ccov/.*: 6
Bug 1611477 - Increase Android xpcshell test chunks from 3 to 4; r=jmaher Avoid intermittent task timeouts by increasing test chunks for Android xpcshell. Differential Revision: https://phabricator.services.mozilla.com/D61004 --HG-- extra : moz-landing-system : lando
2020-01-25 01:10:17 +03:00
android-em-7.*: 4
Bug 1555454 - migrate xpcshelltests to macosx1014 r=gbrown Changes: - move xpcshell from macosx1010 to macosx1014 - updated regex for macosx1014 xpcshell to run on 2 chunks for all variants (for now) Differential Revision: https://phabricator.services.mozilla.com/D34561 --HG-- extra : moz-landing-system : lando
2019-06-11 21:36:19 +03:00
macosx.*(?!-ccov)...../.*: 2
Bug 1602863 - update references to linux64 in yaml files for xpcshell and mochitest-media to linux1804 r=jmaher Changes: Update references to `linux64` in the YAML files to read `linux1804-64`. Differential Revision: https://phabricator.services.mozilla.com/D59024 --HG-- extra : moz-landing-system : lando
2020-01-08 02:55:56 +03:00
linux1804-64(-qr)?/debug: 6
Bug 1612711 - Enable Mochitests and XPCShell tests for TSan. r=froydnj Differential Revision: https://phabricator.services.mozilla.com/D62628 --HG-- extra : moz-landing-system : lando
2020-02-12 22:03:36 +03:00
.*-tsan/opt: 8
Bug 1548160 - task efficiency: review and reduce chunk count of xpcshell for various platforms r=gbrown,jmaher Changes: - set `macosx64-ccov` tests to 8 chunks (unchanged from m-c) - set windows and linux `ccov` to 6 chunks (from 8) - set `linux64.*/debug` to 6 chunks (from 10 and 8) - set `android-em` to 8 chunks (unchanged) - set default chunks to be 5 (from 8) Differential Revision: https://phabricator.services.mozilla.com/D29713 --HG-- extra : moz-landing-system : lando
2019-05-09 23:59:52 +03:00
windows(7-32|10-64)(-shippable|-devedition|-asan|.*-qr)?/.*: 2
default: 5
Bug 1411358 - Increase Android/debug xpcshell max-run-time; r=me,a=test-only Task run time for these tests is highly variable across chunks: Some run in only 30 minutes, while xpcshell-11 sometimes exceeds 90 minutes. Rather than waste resources on more chunks, I think increasing the max task run time is a reasonable way of avoiding intermittent task time-outs.
2018-06-01 22:11:21 +03:00
max-run-time:
by-test-platform:
Bug 1600146 - Increase macosx and windows 10 opt xpcshell max-run-time; r=egao Increase max-run-times to avoid intermittent task timeouts. Increasing chunks for these tasks is not effective: chunks are very unbalanced due to a group of long-running tests. Differential Revision: https://phabricator.services.mozilla.com/D55182 --HG-- extra : moz-landing-system : lando
2019-11-28 23:58:08 +03:00
macosx.*(?!-ccov)...../.*: 5400
windows(7-32|10-64)(-shippable)?/opt: 5400
Bug 1624013 - Increase max-run-time for ccov xpcshell; r=jmaher Avoid frequent task timeouts in ccov xpcshell by allowing more time. Differential Revision: https://phabricator.services.mozilla.com/D67720 --HG-- extra : moz-landing-system : lando
2020-03-22 11:58:17 +03:00
.*-ccov/.*: 7200
Bug 1617031 - Increase max-run-time for tsan xpcshell; r=bc Avoid intermittent task timeouts by increasing the max-run-time for tsan xpcshell. These tasks are unbalanced (wide variance in run time from one chunk to the next) apparently because the tsan times vary significantly on a test-by-test basis when compared with normal xpcshell tasks on the same base platform. Rather than go to extraordinary measures to balance this particular set of tests, increase the max run time so that timeouts are avoided when one chunk runs particularly long. Differential Revision: https://phabricator.services.mozilla.com/D63741 --HG-- extra : moz-landing-system : lando
2020-02-22 03:20:49 +03:00
.*-tsan/opt: 7200
Bug 1637000: Increase the maximum runtime for xpcshell in android emulator r=gbrown Since we now run those tests in baremetal (which runs more parallel jobs than packet.net), the variance of the time it takes to execute xpcshell tests increased. Differential Revision: https://phabricator.services.mozilla.com/D74703
2020-05-11 19:58:44 +03:00
android-em-7.*: 5400
Bug 1574254 - adjust XPCshell max run times. r=jmaher Differential Revision: https://phabricator.services.mozilla.com/D42481 --HG-- extra : moz-landing-system : lando
2019-08-19 13:54:31 +03:00
default: 2700
Bug 1388478 - Split tests.yml into several smaller suite-specific files, r=dustin,jmaher This is a simple refactor into separate files. No task definitions should be modified by this patch. Most tasks are moved into suite-specific .yml files. A handful of miscellaneous tasks are defined directly in kind.yml under the 'jobs' key. MozReview-Commit-ID: 7piXDA6tGI0 --HG-- extra : rebase_source : a91fbb6d0bf740a28a042470b3f9d4a4e309d1f0
2017-10-17 23:25:41 +03:00
allow-software-gl-layers: false
tier:
by-test-platform:
windows10-64-asan.*: 3
default: default
Bug 1571573 - P1 use node in toolchain-artifact for xpcshell r=tomprince Differential Revision: https://phabricator.services.mozilla.com/D44898 --HG-- extra : moz-landing-system : lando
2019-09-06 00:27:37 +03:00
fetches:
toolchain:
by-test-platform:
linux.*:
- linux64-node
Bug 1525218 - Use minidump_stackwalk toolchain artifacts instead of tooltool packages. r=froydnj Differential Revision: https://phabricator.services.mozilla.com/D59936 --HG-- extra : moz-landing-system : lando
2020-02-06 11:39:54 +03:00
- linux64-minidump-stackwalk
Bug 1604964 - Add fix-stacks toolchain. r=erahm Differential Revision: https://phabricator.services.mozilla.com/D57747 --HG-- extra : moz-landing-system : lando
2020-02-20 23:57:32 +03:00
- linux64-fix-stacks
Bug 1571573 - P1 use node in toolchain-artifact for xpcshell r=tomprince Differential Revision: https://phabricator.services.mozilla.com/D44898 --HG-- extra : moz-landing-system : lando
2019-09-06 00:27:37 +03:00
macosx.*:
- macosx64-node
Bug 1525218 - Use minidump_stackwalk toolchain artifacts instead of tooltool packages. r=froydnj Differential Revision: https://phabricator.services.mozilla.com/D59936 --HG-- extra : moz-landing-system : lando
2020-02-06 11:39:54 +03:00
- macosx64-minidump-stackwalk
Bug 1604964 - Add fix-stacks toolchain. r=erahm Differential Revision: https://phabricator.services.mozilla.com/D57747 --HG-- extra : moz-landing-system : lando
2020-02-20 23:57:32 +03:00
- macosx64-fix-stacks
Bug 1582972 - Use win32-node for aarch64 tests. r=nalexander Bug 1571573 removed the manual download of node by mozharness. That made the tasks use whatever comes from fetches, and for aarch64 tests, it turned out to be a win64 node binary, which doesn't work on aarch64. Differential Revision: https://phabricator.services.mozilla.com/D47707 --HG-- extra : moz-landing-system : lando
2019-10-01 02:28:46 +03:00
win.*aarch64.*:
- win32-node
Bug 1525218 - Use minidump_stackwalk toolchain artifacts instead of tooltool packages. r=froydnj Differential Revision: https://phabricator.services.mozilla.com/D59936 --HG-- extra : moz-landing-system : lando
2020-02-06 11:39:54 +03:00
- win32-minidump-stackwalk
Bug 1582972 - Use win32-node for aarch64 tests. r=nalexander Bug 1571573 removed the manual download of node by mozharness. That made the tasks use whatever comes from fetches, and for aarch64 tests, it turned out to be a win64 node binary, which doesn't work on aarch64. Differential Revision: https://phabricator.services.mozilla.com/D47707 --HG-- extra : moz-landing-system : lando
2019-10-01 02:28:46 +03:00
win.*-64.*:
Bug 1571573 - P1 use node in toolchain-artifact for xpcshell r=tomprince Differential Revision: https://phabricator.services.mozilla.com/D44898 --HG-- extra : moz-landing-system : lando
2019-09-06 00:27:37 +03:00
- win64-node
Bug 1525218 - Use minidump_stackwalk toolchain artifacts instead of tooltool packages. r=froydnj Differential Revision: https://phabricator.services.mozilla.com/D59936 --HG-- extra : moz-landing-system : lando
2020-02-06 11:39:54 +03:00
- win32-minidump-stackwalk
Bug 1604095 - Build `fix-stacks` as 32-bit on Windows, cross-compiling from Linux. r=glandium Also remove some unnecessary stuff from the Mac toolchain configuration. Differential Revision: https://phabricator.services.mozilla.com/D65056 --HG-- extra : moz-landing-system : lando
2020-03-05 03:23:27 +03:00
- win32-fix-stacks
Bug 1571573 - P1 use node in toolchain-artifact for xpcshell r=tomprince Differential Revision: https://phabricator.services.mozilla.com/D44898 --HG-- extra : moz-landing-system : lando
2019-09-06 00:27:37 +03:00
win.*32.*:
- win32-node
Bug 1525218 - Use minidump_stackwalk toolchain artifacts instead of tooltool packages. r=froydnj Differential Revision: https://phabricator.services.mozilla.com/D59936 --HG-- extra : moz-landing-system : lando
2020-02-06 11:39:54 +03:00
- win32-minidump-stackwalk
Bug 1604095 - Build `fix-stacks` as 32-bit on Windows, cross-compiling from Linux. r=glandium Also remove some unnecessary stuff from the Mac toolchain configuration. Differential Revision: https://phabricator.services.mozilla.com/D65056 --HG-- extra : moz-landing-system : lando
2020-03-05 03:23:27 +03:00
- win32-fix-stacks
Bug 1608126 - Enable node for Android xpcshell tests and run node tests on Android; r=valentin Fetch, configure, and run node for Android on the test host, just like Linux tests do. Make the node/HTTP/2 environment variables available to the tests on the device, and use adb port forwarding to connect sockets. Finally, enable tests skipped for node. Differential Revision: https://phabricator.services.mozilla.com/D60204 --HG-- extra : moz-landing-system : lando
2020-01-20 21:06:37 +03:00
android-em-7.*:
Bug 1637379: Optimize android toolchains r=gbrown Create an emulator toolchain Stop including mozboot/sdk-*.zip in our tarball Differential Revision: https://phabricator.services.mozilla.com/D74931
2020-05-21 16:28:10 +03:00
- android-emulator-linux
Bug 1608126 - Enable node for Android xpcshell tests and run node tests on Android; r=valentin Fetch, configure, and run node for Android on the test host, just like Linux tests do. Make the node/HTTP/2 environment variables available to the tests on the device, and use adb port forwarding to connect sockets. Finally, enable tests skipped for node. Differential Revision: https://phabricator.services.mozilla.com/D60204 --HG-- extra : moz-landing-system : lando
2020-01-20 21:06:37 +03:00
- linux64-node
Bug 1525218 - Use minidump_stackwalk toolchain artifacts instead of tooltool packages. r=froydnj Differential Revision: https://phabricator.services.mozilla.com/D59936 --HG-- extra : moz-landing-system : lando
2020-02-06 11:39:54 +03:00
- linux64-minidump-stackwalk