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

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

530 строки
16 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:
category: mochitest
Bug 1460411 - Add taskcluster configuration for android-x86-7.0 tests; r=me,a=test-only The new platform is disabled for now: Expect no changes, yet.
2018-05-14 17:12:46 +03:00
target:
by-test-platform:
Bug 1498298 - Prepare to run packet.net geckoview tests against x86_64 opt/debug builds; r=me,a=test-only This doesn't actually run anything differently, yet.
2019-01-05 02:46:01 +03:00
android-em-7.*: geckoview-androidTest.apk
Bug 1568861 - Run android-hw mochitest-media against geckoview; r=bc Differential Revision: https://phabricator.services.mozilla.com/D41205 --HG-- extra : moz-landing-system : lando
2019-08-08 16:54:07 +03:00
android-hw.*: geckoview-androidTest.apk
Bug 1460411 - Add taskcluster configuration for android-x86-7.0 tests; r=me,a=test-only The new platform is disabled for now: Expect no changes, yet.
2018-05-14 17:12:46 +03:00
default: null
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 mochitest tasks with linux64/debug on mozilla-central, r=jmaher This duplicates all the mochitest, based tests except with dom.serviceWorkers.parent_intercept set to true. For now they are only run on mozilla-central with linux64/debug. Differential Revision: https://phabricator.services.mozilla.com/D7641 --HG-- extra : moz-landing-system : lando
2018-10-05 22:12:27 +03:00
by-test-platform:
Bug 1640105 - Add socketprocess_networking variant for mochitest r=ahal,jmaher Differential Revision: https://phabricator.services.mozilla.com/D77302
2020-08-10 12:21:03 +03:00
linux.*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 1620204 - enable windows10-aarch64 reftests, crashtests, mochitest-media on beta/release r=jmaher Changes: Specifically enable `mozilla-beta` and `mozilla-release` for windows10-aarch64 `reftest`, `crashtest` and `mochitest-media`. This will exclude `mozilla-esr*` which is part of the `release` tag (https://searchfox.org/mozilla-central/source/taskcluster/taskgraph/util/attributes.py#18-27) Differential Revision: https://phabricator.services.mozilla.com/D65811 --HG-- extra : moz-landing-system : lando
2020-03-07 01:00:19 +03:00
run-on-projects: built-projects
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-run-on-projects:
by-test-platform:
Bug 1602863 - update linux64 platform regex in yaml files to be compatible with linux64 and linux1804 strings r=gbrown 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
2020-01-14 20:35:00 +03:00
linux.*64-qr/debug: ['trunk']
Bug 1650208: run opt builds by default on autoland; shippable builds by default on central r=tomprince,ahal,marco Differential Revision: https://phabricator.services.mozilla.com/D83186
2020-07-27 19:25:40 +03:00
linux.*64-shippable-qr/opt: ['mozilla-central']
linux.*64-shippable/.*: ['mozilla-central']
linux.*64/debug: ['mozilla-central']
windows10-64-shippable(-qr)?/opt: ['mozilla-central']
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
default: []
fission-tier:
by-test-platform:
Bug 1602863 - update linux64 platform regex in yaml files to be compatible with linux64 and linux1804 strings r=gbrown 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
2020-01-14 20:35:00 +03:00
linux.*64.*-qr/debug: 1
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
default: 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 1426586 - Add android hardware test platforms for android-hw, r=gbrown,jmaher
2018-06-23 02:39:32 +03:00
android-hw.*: android_hardware_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 1498298 - Prepare to run packet.net geckoview tests against x86_64 opt/debug builds; r=me,a=test-only This doesn't actually run anything differently, yet.
2019-01-05 02:46:01 +03:00
android-em-7.*:
Bug 1460411 - Add taskcluster configuration for android-x86-7.0 tests; r=me,a=test-only The new platform is disabled for now: Expect no changes, yet.
2018-05-14 17:12:46 +03:00
- android/android_common.py
- android/androidx86_7_0.py
Bug 1426586 - Add android hardware test platforms for android-hw, r=gbrown,jmaher
2018-06-23 02:39:32 +03:00
android-hw.*:
Bug 1472311 - Use android_common.py for android-hw mozharness config; r=bc
2018-07-03 16:33:47 +03:00
- android/android_common.py
Bug 1426586 - Add android hardware test platforms for android-hw, r=gbrown,jmaher
2018-06-23 02:39:32 +03:00
- android/android_hw.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
Bug 1618353 - Rename the mochitest jobs to mochitest-plain. r=ahal Differential Revision: https://phabricator.services.mozilla.com/D64733 --HG-- extra : moz-landing-system : lando
2020-03-02 18:23:13 +03:00
mochitest-plain:
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
description: "Mochitest plain 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: M()
Bug 1598746 - Adjust some mochitest and reftest SCHEDULES.exclusive entries; r=ahal Use finer granularity for some reftest/mochitest SCHEDULES.exclusive entries, so that reftest-plain does not run when only crashtests are modified, and vice versa; similarly, break up mochitest into mochitest/browser-chrome/chrome/ a11y. Use schedules-component instead of category. Differential Revision: https://phabricator.services.mozilla.com/D60085 --HG-- extra : moz-landing-system : lando
2020-03-24 17:55:28 +03:00
schedules-component: mochitest-plain
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
loopback-video: true
Bug 1620460 - turn off all tests except crashtest, reftest and mochitest-media on windows10-aarch64 r=jmaher Changes: Remove all tests other than `reftests`, `crashtests` and `mochitest-media` for windows10-aarch64. Important changes are in `taskcluster/ci/test/test-platforms.yml` and `taskcluster/ci/test/test-sets.yml`. I've gone ahead and removed the windows10-aarch64 specific entries in the YAML files as well. Differential Revision: https://phabricator.services.mozilla.com/D65654 --HG-- extra : moz-landing-system : lando
2020-03-06 03:15:43 +03:00
tier: default
Bug 1664884 - migrate windows10 mochitest plain, gpu from aws to datacenter. r=bc migrate windows10 mochitest plain and gpu fro maws to datacenter. Differential Revision: https://phabricator.services.mozilla.com/D90451
2020-09-16 22:45:24 +03:00
virtualization:
by-test-platform:
windows10-64.*: hardware
default: virtual
Bug 1647720 - Replace fission with fission-xorigin variant, for linux64 mochitest-plain only; r=ahal Differential Revision: https://phabricator.services.mozilla.com/D84611
2020-07-23 16:12:54 +03:00
variants:
by-test-platform:
linux1804-64/opt: ['fission-xorigin']
linux1804-64/debug: ['fission-xorigin']
default: ['fission']
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
chunks:
by-test-platform:
Bug 1585119 - Re-enable many mochitests on android; r=geckoview-reviewers,snorp Most of these tests have been disabled for a long time; they run well in the current test environment. With the additional tests running, task times increase; I have added one more test chunk for android mochitest-plain. These tests were identified from a random sampling of mochitest manifests; I intend to enable more mochitests in future patches. Differential Revision: https://phabricator.services.mozilla.com/D48912 --HG-- extra : moz-landing-system : lando
2019-10-15 18:07:09 +03:00
android-em-7.*: 4
Bug 1411342 - reduce chunks for mochitests on linux now that we run on faster hardware. r=gbrown
2017-10-27 21:06:38 +03:00
linux.*/debug: 16
Bug 1602863 - update linux64 platform regex in yaml files to be compatible with linux64 and linux1804 strings r=gbrown 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
2020-01-14 20:35:00 +03:00
linux.*64-asan/opt: 10
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
linux.*64-tsan/opt: 20
Bug 1602863 - update linux64 platform regex in yaml files to be compatible with linux64 and linux1804 strings r=gbrown 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
2020-01-14 20:35:00 +03:00
linux.*64-.*cov/opt: 10
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
windows10-64-ccov/.*: 10
macosx.*64-ccov/.*: 10
Bug 1411342 - reduce chunks for mochitests on linux now that we run on faster hardware. r=gbrown
2017-10-27 21:06:38 +03:00
default: 5
Bug 1621416 - run Linux tsan mochitests with t-linux-xlarge to prevent retries and out-of-memory crashes. r=jmaher Differential Revision: https://phabricator.services.mozilla.com/D66299 --HG-- extra : moz-landing-system : lando
2020-03-11 22:23:15 +03:00
instance-size:
by-test-platform:
linux.*64-tsan/opt: xlarge # runs out of memory on default/m3.large
default: default
Bug 1548649 - remove all linux32 tests except for shippable, and restrict those tests to web-platform-tests r=jmaher Changes: - edited `linux32-tests` to include only web-platform-tests - removed references to other `linux32` platforms from `test-platforms.yml` other than `linux32-shippable/opt` Differential Revision: https://phabricator.services.mozilla.com/D29792 --HG-- extra : moz-landing-system : lando
2019-05-21 19:04:06 +03:00
e10s: true
Bug 1583695 - Adjust Android test timeouts; r=bc Change the taskcluster max-run-time for mochitests and reftests to use the defaults, now that android tests no longer run anywhere near 7200 seconds. (Also noticed some unrelated tc configuration that is obsolete - tidied that.) Also remove the special 600 second reftest timeout for android debug reftests. Differential Revision: https://phabricator.services.mozilla.com/D47301 --HG-- extra : moz-landing-system : lando
2019-09-26 20:03:18 +03:00
max-run-time: 5400
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
mozharness:
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
mochitest-flavor: plain
extra-options:
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.*:
Bug 1523303 - Align mozharness suite names with the ones in 'moztest.resolve', r=gbrown This officially makes 'moztest.resolve' the source of truth when it comes to suite names. It aligns that file with the names used in both the desktop_unittest and android_emulator_unittest scripts. Differential Revision: https://phabricator.services.mozilla.com/D27555 --HG-- extra : moz-landing-system : lando
2019-04-23 01:32:34 +03:00
- --test-suite=mochitest-plain
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: []
chunked:
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.*: 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
default: true
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
mochitest-a11y:
description: "Mochitest a11y 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: M(a11y)
Bug 1598746 - Adjust some mochitest and reftest SCHEDULES.exclusive entries; r=ahal Use finer granularity for some reftest/mochitest SCHEDULES.exclusive entries, so that reftest-plain does not run when only crashtests are modified, and vice versa; similarly, break up mochitest into mochitest/browser-chrome/chrome/ a11y. Use schedules-component instead of category. Differential Revision: https://phabricator.services.mozilla.com/D60085 --HG-- extra : moz-landing-system : lando
2020-03-24 17:55:28 +03:00
schedules-component: mochitest-a11y
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
loopback-video: true
Bug 1620460 - turn off all tests except crashtest, reftest and mochitest-media on windows10-aarch64 r=jmaher Changes: Remove all tests other than `reftests`, `crashtests` and `mochitest-media` for windows10-aarch64. Important changes are in `taskcluster/ci/test/test-platforms.yml` and `taskcluster/ci/test/test-sets.yml`. I've gone ahead and removed the windows10-aarch64 specific entries in the YAML files as well. Differential Revision: https://phabricator.services.mozilla.com/D65654 --HG-- extra : moz-landing-system : lando
2020-03-06 03:15:43 +03:00
tier: default
Bug 1546100 - Turn off e10s for mochitest-a11y/chrome in task configuration (Backs out effa55bd84bb and 2f12958d4e8c), r=jmaher Turns out these suites were hardcoded to be non-e10s in the mochitest harness. So while it looked like they were working with e10s in treeherder, they were actually still running with it disabled. Turning e10s on causes both suites to permafail due to timeouts. Depends on D28386 Differential Revision: https://phabricator.services.mozilla.com/D28387 --HG-- extra : moz-landing-system : lando
2019-04-22 21:52:24 +03:00
e10s: false
Bug 1620460 - turn off all tests except crashtest, reftest and mochitest-media on windows10-aarch64 r=jmaher Changes: Remove all tests other than `reftests`, `crashtests` and `mochitest-media` for windows10-aarch64. Important changes are in `taskcluster/ci/test/test-platforms.yml` and `taskcluster/ci/test/test-sets.yml`. I've gone ahead and removed the windows10-aarch64 specific entries in the YAML files as well. Differential Revision: https://phabricator.services.mozilla.com/D65654 --HG-- extra : moz-landing-system : lando
2020-03-06 03:15:43 +03:00
run-on-projects: built-projects
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
mozharness:
mochitest-flavor: a11y
mochitest-browser-chrome:
description: "Mochitest browser-chrome run"
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:
Bug 1583353 - [mozharness] Remove '-chunked' mochitest and jittest suite definitions, r=gbrown Having a distinction between -chunked and not adds unnecessary complexity. It's possible to simply remove them because: 1. The mozharness definitions for 'jittest' and 'jittest-chunked' are identical, so it is literally not serving any purpose. 2. The definitions for 'mochitest' only add either '--chunk-by-dir' or '--chunk-by-runtime'. Both of these are no-ops in the mochitest harness unless '--total-chunks' is also supplied. Therefore, if we ever use these suites without chunking (which I don't think we do anyway), then it'll still work fine as those options won't have any affect. Differential Revision: https://phabricator.services.mozilla.com/D51173 --HG-- extra : moz-landing-system : lando
2019-10-31 00:41:24 +03:00
name: mochitest-browser-chrome
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: M(bc)
Bug 1598746 - Adjust some mochitest and reftest SCHEDULES.exclusive entries; r=ahal Use finer granularity for some reftest/mochitest SCHEDULES.exclusive entries, so that reftest-plain does not run when only crashtests are modified, and vice versa; similarly, break up mochitest into mochitest/browser-chrome/chrome/ a11y. Use schedules-component instead of category. Differential Revision: https://phabricator.services.mozilla.com/D60085 --HG-- extra : moz-landing-system : lando
2020-03-24 17:55:28 +03:00
schedules-component: mochitest-browser-chrome
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
loopback-video: true
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-run-on-projects:
by-test-platform:
Bug 1602863 - update linux64 platform regex in yaml files to be compatible with linux64 and linux1804 strings r=gbrown 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
2020-01-14 20:35:00 +03:00
linux.*64(-qr)?/debug: ['trunk']
Bug 1650208: run opt builds by default on autoland; shippable builds by default on central r=tomprince,ahal,marco Differential Revision: https://phabricator.services.mozilla.com/D83186
2020-07-27 19:25:40 +03:00
linux.*64-shippable(-qr)?/opt: ['mozilla-central']
windows10-64-shippable(-qr)?/opt: ['mozilla-central']
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
default: []
Bug 1620460 - turn off all tests except crashtest, reftest and mochitest-media on windows10-aarch64 r=jmaher Changes: Remove all tests other than `reftests`, `crashtests` and `mochitest-media` for windows10-aarch64. Important changes are in `taskcluster/ci/test/test-platforms.yml` and `taskcluster/ci/test/test-sets.yml`. I've gone ahead and removed the windows10-aarch64 specific entries in the YAML files as well. Differential Revision: https://phabricator.services.mozilla.com/D65654 --HG-- extra : moz-landing-system : lando
2020-03-06 03:15:43 +03:00
tier: default
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:
by-test-platform:
Bug 1602863 - update linux64 platform regex in yaml files to be compatible with linux64 and linux1804 strings r=gbrown 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
2020-01-14 20:35:00 +03:00
linux.*64/debug: 1
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
default: 2
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
chunks:
by-test-platform:
Bug 1411342 - reduce chunks for mochitests on linux now that we run on faster hardware. r=gbrown
2017-10-27 21:06:38 +03:00
linux.*/debug: 16
Bug 1602863 - update linux64 platform regex in yaml files to be compatible with linux64 and linux1804 strings r=gbrown 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
2020-01-14 20:35:00 +03:00
linux.*64-asan/opt: 16
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
linux.*64-tsan/opt: 32
Bug 1597797 - Increase test chunks for osx/debug mochitest-browser-chrome; r=jmaher Avoid intermittent task time outs, as seen in bug 1589796. Differential Revision: https://phabricator.services.mozilla.com/D53992 --HG-- extra : moz-landing-system : lando
2019-11-20 21:02:56 +03:00
macosx.*64/debug: 16
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
windows10-64-ccov/.*: 14
Bug 1588160 - Increase test chunks for windows 10 asan browser-chrome; r=ahal Avoid intermittent task timeouts by increasing test chunks. Differential Revision: https://phabricator.services.mozilla.com/D49016 --HG-- extra : moz-landing-system : lando
2019-10-15 18:26:26 +03:00
windows10.*-asan/opt: 9
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
default: 7
max-run-time:
by-test-platform:
Bug 1602863 - update linux64 platform regex in yaml files to be compatible with linux64 and linux1804 strings r=gbrown 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
2020-01-14 20:35:00 +03:00
linux.*64-ccov/.*: 9000
Bug 1572271 - Part 2: Increase the timeout of mochitest-browser-chrome on Windows debug to 90 minutes; r=gbrown Differential Revision: https://phabricator.services.mozilla.com/D42988 --HG-- extra : moz-landing-system : lando
2019-08-22 04:58:38 +03:00
windows7-32/debug: 5400
windows10-64/debug: 5400
Bug 1656625 - disable dock on osx. r=dividehex,bc disble dock on osx. Differential Revision: https://phabricator.services.mozilla.com/D86426
2020-08-12 02:01:50 +03:00
macosx.*64/debug: 5400
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
windows10-64-ccov/.*: 10800
macosx.*64-ccov/.*: 10800
Bug 1411342 - reduce chunks for mochitests on linux now that we run on faster hardware. r=gbrown
2017-10-27 21:06:38 +03:00
linux.*/debug: 5400
Bug 1572393 - Increase Windows 10 x64 QR debug browser-chrome max runtime to 90 minutes. r=gbrown on a CLOSED TREE Reviewers: gbrown Reviewed By: gbrown Subscribers: rjl Bug #: 1572393 Differential Revision: https://phabricator.services.mozilla.com/D41297 --HG-- extra : amend_source : 422bf3b984a6192fc5b24e95a11c5003b219e496
2019-08-09 02:39:37 +03:00
windows10-64-qr/debug: 5400
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
default: 3600
mozharness:
mochitest-flavor: browser
chunked: true
# Bug 1281241: migrating to m3.large instances
Bug 1496791 - Disable linux64-jsdcov completely. r=jmaher This patch removes linux64-jsdcov from the available builds on taskcluster along with any hacks used to run it. It also removes any 'coverage' entries that were added to skip tests. Differential Revision: https://phabricator.services.mozilla.com/D7919 --HG-- extra : moz-landing-system : lando
2018-10-06 00:06:25 +03:00
instance-size: default
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
Bug 1411825 - Stop running browser-screenshots for "-u mochitests" and "-u all". r=ahal MozReview-Commit-ID: 1YbPjs85YIx --HG-- extra : rebase_source : 6725b54ac153c9cb488e21d09211acc514b9314d
2017-10-26 05:39:51 +03:00
browser-screenshots:
description: "Browser Screenshots"
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:
Bug 1523303 - Align mozharness suite names with the ones in 'moztest.resolve', r=gbrown This officially makes 'moztest.resolve' the source of truth when it comes to suite names. It aligns that file with the names used in both the desktop_unittest and android_emulator_unittest scripts. Differential Revision: https://phabricator.services.mozilla.com/D27555 --HG-- extra : moz-landing-system : lando
2019-04-23 01:32:34 +03:00
name: mochitest-browser-chrome-screenshots
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: M(ss)
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
loopback-video: true
run-on-projects:
by-test-platform:
Bug 1650208: run opt builds by default on autoland; shippable builds by default on central r=tomprince,ahal,marco Differential Revision: https://phabricator.services.mozilla.com/D83186
2020-07-27 19:25:40 +03:00
windows7-32(?:-pgo|-shippable)(?:-qr)?/opt: ['mozilla-central']
windows10-64(?:-pgo|-shippable)(?:-qr)?/opt: ['mozilla-central']
(?:windows10-64|windows7-32|linux1804-64|macosx1014-64)(?:-qr)?/opt: ['integration']
linux1804-64-(?:pgo|shippable)(?:-qr)?/opt: ['mozilla-central']
macosx.*64-shippable/opt: ['mozilla-central']
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
default: []
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-run-on-projects: []
fission-tier: 2
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
max-run-time: 3600
mozharness:
mochitest-flavor: browser
allow-software-gl-layers: false
mochitest-chrome:
description: "Mochitest chrome 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: M(c)
Bug 1598746 - Adjust some mochitest and reftest SCHEDULES.exclusive entries; r=ahal Use finer granularity for some reftest/mochitest SCHEDULES.exclusive entries, so that reftest-plain does not run when only crashtests are modified, and vice versa; similarly, break up mochitest into mochitest/browser-chrome/chrome/ a11y. Use schedules-component instead of category. Differential Revision: https://phabricator.services.mozilla.com/D60085 --HG-- extra : moz-landing-system : lando
2020-03-24 17:55:28 +03:00
schedules-component: mochitest-chrome
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
loopback-video: true
Bug 1620460 - turn off all tests except crashtest, reftest and mochitest-media on windows10-aarch64 r=jmaher Changes: Remove all tests other than `reftests`, `crashtests` and `mochitest-media` for windows10-aarch64. Important changes are in `taskcluster/ci/test/test-platforms.yml` and `taskcluster/ci/test/test-sets.yml`. I've gone ahead and removed the windows10-aarch64 specific entries in the YAML files as well. Differential Revision: https://phabricator.services.mozilla.com/D65654 --HG-- extra : moz-landing-system : lando
2020-03-06 03:15:43 +03:00
tier: default
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
chunks:
by-test-platform:
Bug 1555156 - task efficiency: reduce chunks of mochitest-chrome for selected platforms r=jmaher Changes: - default chunk count is now set to 2 - added exception rules to maintain current chunk count (3) for slower platforms and build types Differential Revision: https://phabricator.services.mozilla.com/D32929 --HG-- extra : moz-landing-system : lando
2019-05-29 06:40:29 +03:00
.*-ccov/.*: 3
.*-qr/.*: 3
.*-asan/opt: 3
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: 6
Bug 1602863 - update linux64 platform regex in yaml files to be compatible with linux64 and linux1804 strings r=gbrown 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
2020-01-14 20:35:00 +03:00
(linux.*64|windows.*-..|macosx10..)/debug: 3
Bug 1555156 - task efficiency: reduce chunks of mochitest-chrome for selected platforms r=jmaher Changes: - default chunk count is now set to 2 - added exception rules to maintain current chunk count (3) for slower platforms and build types Differential Revision: https://phabricator.services.mozilla.com/D32929 --HG-- extra : moz-landing-system : lando
2019-05-29 06:40:29 +03:00
default: 2
Bug 1583695 - Adjust Android test timeouts; r=bc Change the taskcluster max-run-time for mochitests and reftests to use the defaults, now that android tests no longer run anywhere near 7200 seconds. (Also noticed some unrelated tc configuration that is obsolete - tidied that.) Also remove the special 600 second reftest timeout for android debug reftests. Differential Revision: https://phabricator.services.mozilla.com/D47301 --HG-- extra : moz-landing-system : lando
2019-09-26 20:03:18 +03:00
max-run-time: 3600
Bug 1546100 - Turn off e10s for mochitest-a11y/chrome in task configuration (Backs out effa55bd84bb and 2f12958d4e8c), r=jmaher Turns out these suites were hardcoded to be non-e10s in the mochitest harness. So while it looked like they were working with e10s in treeherder, they were actually still running with it disabled. Turning e10s on causes both suites to permafail due to timeouts. Depends on D28386 Differential Revision: https://phabricator.services.mozilla.com/D28387 --HG-- extra : moz-landing-system : lando
2019-04-22 21:52:24 +03:00
e10s: 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
mozharness:
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
mochitest-flavor: chrome
Bug 1583695 - Adjust Android test timeouts; r=bc Change the taskcluster max-run-time for mochitests and reftests to use the defaults, now that android tests no longer run anywhere near 7200 seconds. (Also noticed some unrelated tc configuration that is obsolete - tidied that.) Also remove the special 600 second reftest timeout for android debug reftests. Differential Revision: https://phabricator.services.mozilla.com/D47301 --HG-- extra : moz-landing-system : lando
2019-09-26 20:03:18 +03:00
chunked: true
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
mochitest-devtools-chrome:
description: "Mochitest devtools-chrome run"
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:
Bug 1583353 - [mozharness] Remove '-chunked' mochitest and jittest suite definitions, r=gbrown Having a distinction between -chunked and not adds unnecessary complexity. It's possible to simply remove them because: 1. The mozharness definitions for 'jittest' and 'jittest-chunked' are identical, so it is literally not serving any purpose. 2. The definitions for 'mochitest' only add either '--chunk-by-dir' or '--chunk-by-runtime'. Both of these are no-ops in the mochitest harness unless '--total-chunks' is also supplied. Therefore, if we ever use these suites without chunking (which I don't think we do anyway), then it'll still work fine as those options won't have any affect. Differential Revision: https://phabricator.services.mozilla.com/D51173 --HG-- extra : moz-landing-system : lando
2019-10-31 00:41:24 +03:00
name: mochitest-devtools-chrome
Bug 1643811 - [ci] Add a SCHEDULES rule to exclusively run browser-chrome tests when '**/test/browser_*' files are modified, r=gbrown,Gijs Also makes sure that 'mochitest-devtools-chrome' tasks are triggered by the 'mochitest-browser-chrome' component since they use the same manifest / test formats. Depends on D78906 Differential Revision: https://phabricator.services.mozilla.com/D78927
2020-06-09 20:14:09 +03:00
schedules-component: mochitest-browser-chrome
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: M(dt)
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
loopback-video: true
Bug 1620460 - turn off all tests except crashtest, reftest and mochitest-media on windows10-aarch64 r=jmaher Changes: Remove all tests other than `reftests`, `crashtests` and `mochitest-media` for windows10-aarch64. Important changes are in `taskcluster/ci/test/test-platforms.yml` and `taskcluster/ci/test/test-sets.yml`. I've gone ahead and removed the windows10-aarch64 specific entries in the YAML files as well. Differential Revision: https://phabricator.services.mozilla.com/D65654 --HG-- extra : moz-landing-system : lando
2020-03-06 03:15:43 +03:00
tier: default
Bug 1445838 - Increase task timeout on code coverage (ccov) test tasks. r=marco Increases the max-run-time for all test tasks on ccov builds. MozReview-Commit-ID: KtArHMWKgbH --HG-- extra : rebase_source : 61b6831ba39f005992ce3ec5db5568ad9ce95a36
2018-03-15 00:49:48 +03:00
max-run-time:
by-test-platform:
Bug 1603477 - Increase max-run-time for windows ccov devtools; r=marco Differential Revision: https://phabricator.services.mozilla.com/D56960 --HG-- extra : moz-landing-system : lando
2019-12-12 19:54:44 +03:00
windows10-64-ccov/.*: 10800
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
macosx.*64-ccov/.*: 9000
Bug 1602863 - update linux64 platform regex in yaml files to be compatible with linux64 and linux1804 strings r=gbrown 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
2020-01-14 20:35:00 +03:00
linux.*64-ccov/.*: 7200
Bug 1445838 - Increase task timeout on code coverage (ccov) test tasks. r=marco Increases the max-run-time for all test tasks on ccov builds. MozReview-Commit-ID: KtArHMWKgbH --HG-- extra : rebase_source : 61b6831ba39f005992ce3ec5db5568ad9ce95a36
2018-03-15 00:49:48 +03:00
default: 5400
Bug 1433610 - Increase number of chunks for mochitest-devtools-chrome on windows10-64-ccov. r=jmaher --HG-- extra : rebase_source : 144a31db13253fcfeb2d4a33b94fc2a004d73f7a
2018-01-29 13:51:17 +03:00
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/.*: 16
Bug 1602863 - update linux64 platform regex in yaml files to be compatible with linux64 and linux1804 strings r=gbrown 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
2020-01-14 20:35:00 +03:00
linux.*64/debug: 12
Bug 1550826 - add initial support for osx mojave 10.14 to our CI. r=ahal add initial support for osx mojave 10.14 to our CI. Differential Revision: https://phabricator.services.mozilla.com/D30795 --HG-- extra : moz-landing-system : lando
2019-05-14 21:33:12 +03:00
macosx.*64/debug: 8
Bug 1549619 - task efficiency: revisit chunking of mochitest-devtools-chrome r=jmaher Changes: - reduced `linux64/debug` chunking to 14 (from 16) - reduced `linux64-ccov/debug` to 14 (from 16) - increased `windows64-ccov` to 16 (from 10) - maintain all non-ccov debug to 8 - maintain all asan to 8 - reduce everything else to 5 Differential Revision: https://phabricator.services.mozilla.com/D30303 --HG-- extra : moz-landing-system : lando
2019-05-09 19:29:10 +03:00
.*-asan/opt: 8
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: 16
Bug 1549619 - task efficiency: revisit chunking of mochitest-devtools-chrome r=jmaher Changes: - reduced `linux64/debug` chunking to 14 (from 16) - reduced `linux64-ccov/debug` to 14 (from 16) - increased `windows64-ccov` to 16 (from 10) - maintain all non-ccov debug to 8 - maintain all asan to 8 - reduce everything else to 5 Differential Revision: https://phabricator.services.mozilla.com/D30303 --HG-- extra : moz-landing-system : lando
2019-05-09 19:29:10 +03:00
default: 5
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
mozharness:
mochitest-flavor: chrome
chunked: true
instance-size:
by-test-platform:
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
linux.*64-[at]san/opt: xlarge # runs out of memory on default/m3.large
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
default: default
# Bug 1296086: high number of intermittents observed with software GL and large instances
allow-software-gl-layers: false
Bug 1603842 - separate mochitest-gpu tasks into mochitest-chrome-gpu and mochitest-plain-gpu r=ahal,gbrown Changes: Remove references to `mochitest-browser-chrome-gpu` as this suite does not exist. In `test-sets.yml`, split existing `mochitest-gpu` task into `plain` and `chrome` variants. In `mochitest.yml` split the existing `mochitest-gpu` task into `plain` and `chrome` variants with separate symbols on treeherder. Differential Revision: https://phabricator.services.mozilla.com/D66670 --HG-- extra : moz-landing-system : lando
2020-03-17 16:36:28 +03:00
mochitest-plain-gpu:
description: "Mochitest plain GPU run"
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:
Bug 1523303 - Align mozharness suite names with the ones in 'moztest.resolve', r=gbrown This officially makes 'moztest.resolve' the source of truth when it comes to suite names. It aligns that file with the names used in both the desktop_unittest and android_emulator_unittest scripts. Differential Revision: https://phabricator.services.mozilla.com/D27555 --HG-- extra : moz-landing-system : lando
2019-04-23 01:32:34 +03:00
name: mochitest-plain-gpu
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: M(gpu)
Bug 1598746 - Adjust some mochitest and reftest SCHEDULES.exclusive entries; r=ahal Use finer granularity for some reftest/mochitest SCHEDULES.exclusive entries, so that reftest-plain does not run when only crashtests are modified, and vice versa; similarly, break up mochitest into mochitest/browser-chrome/chrome/ a11y. Use schedules-component instead of category. Differential Revision: https://phabricator.services.mozilla.com/D60085 --HG-- extra : moz-landing-system : lando
2020-03-24 17:55:28 +03:00
schedules-component: mochitest-plain
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
loopback-video: true
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-run-on-projects: []
fission-tier: 2
Bug 1620460 - turn off all tests except crashtest, reftest and mochitest-media on windows10-aarch64 r=jmaher Changes: Remove all tests other than `reftests`, `crashtests` and `mochitest-media` for windows10-aarch64. Important changes are in `taskcluster/ci/test/test-platforms.yml` and `taskcluster/ci/test/test-sets.yml`. I've gone ahead and removed the windows10-aarch64 specific entries in the YAML files as well. Differential Revision: https://phabricator.services.mozilla.com/D65654 --HG-- extra : moz-landing-system : lando
2020-03-06 03:15:43 +03:00
tier: default
Bug 1664884 - migrate windows10 mochitest plain, gpu from aws to datacenter. r=bc migrate windows10 mochitest plain and gpu fro maws to datacenter. Differential Revision: https://phabricator.services.mozilla.com/D90451
2020-09-16 22:45:24 +03:00
virtualization:
by-test-platform:
windows10-64.*: hardware
default: virtual-with-gpu
Bug 1548649 - remove all linux32 tests except for shippable, and restrict those tests to web-platform-tests r=jmaher Changes: - edited `linux32-tests` to include only web-platform-tests - removed references to other `linux32` platforms from `test-platforms.yml` other than `linux32-shippable/opt` Differential Revision: https://phabricator.services.mozilla.com/D29792 --HG-- extra : moz-landing-system : lando
2019-05-21 19:04:06 +03:00
e10s: true
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
mozharness:
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
mochitest-flavor: plain
extra-options:
by-test-platform:
Bug 1633296 - mochitest-{plain,chrome}-gpu support --test-suite not --mochitest-suite, r=gbrown. Differential Revision: https://phabricator.services.mozilla.com/D72574
2020-04-27 21:48:26 +03:00
android.*:
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
# note that Android runs fewer suites than other platforms
- --test-suite=mochitest-plain-gpu
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:
Bug 1603842 - separate mochitest-gpu tasks into mochitest-chrome-gpu and mochitest-plain-gpu r=ahal,gbrown Changes: Remove references to `mochitest-browser-chrome-gpu` as this suite does not exist. In `test-sets.yml`, split existing `mochitest-gpu` task into `plain` and `chrome` variants. In `mochitest.yml` split the existing `mochitest-gpu` task into `plain` and `chrome` variants with separate symbols on treeherder. Differential Revision: https://phabricator.services.mozilla.com/D66670 --HG-- extra : moz-landing-system : lando
2020-03-17 16:36:28 +03:00
- --mochitest-suite=mochitest-plain-gpu
mochitest-chrome-gpu:
description: "Mochitest chrome GPU run"
suite:
name: mochitest-chrome-gpu
treeherder-symbol: M(gpu-c)
loopback-video: true
fission-run-on-projects: []
fission-tier: 2
tier: default
Bug 1664884 - migrate windows10 mochitest plain, gpu from aws to datacenter. r=bc migrate windows10 mochitest plain and gpu fro maws to datacenter. Differential Revision: https://phabricator.services.mozilla.com/D90451
2020-09-16 22:45:24 +03:00
virtualization:
by-test-platform:
windows10-64.*: hardware
default: virtual-with-gpu
Bug 1603842 - separate mochitest-gpu tasks into mochitest-chrome-gpu and mochitest-plain-gpu r=ahal,gbrown Changes: Remove references to `mochitest-browser-chrome-gpu` as this suite does not exist. In `test-sets.yml`, split existing `mochitest-gpu` task into `plain` and `chrome` variants. In `mochitest.yml` split the existing `mochitest-gpu` task into `plain` and `chrome` variants with separate symbols on treeherder. Differential Revision: https://phabricator.services.mozilla.com/D66670 --HG-- extra : moz-landing-system : lando
2020-03-17 16:36:28 +03:00
e10s: true
run-on-projects:
by-test-platform:
android.*/.*: []
default: built-projects
mozharness:
mochitest-flavor: chrome
extra-options:
Bug 1633296 - mochitest-{plain,chrome}-gpu support --test-suite not --mochitest-suite, r=gbrown. Differential Revision: https://phabricator.services.mozilla.com/D72574
2020-04-27 21:48:26 +03:00
by-test-platform:
android.*:
# note that Android runs fewer suites than other platforms
- --test-suite=mochitest-chrome-gpu
default:
- --mochitest-suite=mochitest-chrome-gpu
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
mochitest-media:
description: "Mochitest media 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: M(mda)
Bug 1598746 - Adjust some mochitest and reftest SCHEDULES.exclusive entries; r=ahal Use finer granularity for some reftest/mochitest SCHEDULES.exclusive entries, so that reftest-plain does not run when only crashtests are modified, and vice versa; similarly, break up mochitest into mochitest/browser-chrome/chrome/ a11y. Use schedules-component instead of category. Differential Revision: https://phabricator.services.mozilla.com/D60085 --HG-- extra : moz-landing-system : lando
2020-03-24 17:55:28 +03:00
schedules-component: mochitest-plain
Bug 1445838 - Increase task timeout on code coverage (ccov) test tasks. r=marco Increases the max-run-time for all test tasks on ccov builds. MozReview-Commit-ID: KtArHMWKgbH --HG-- extra : rebase_source : 61b6831ba39f005992ce3ec5db5568ad9ce95a36
2018-03-15 00:49:48 +03:00
max-run-time:
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
windows10-64-ccov/.*: 7200
macosx.*64-ccov/.*: 7200
Bug 1445838 - Increase task timeout on code coverage (ccov) test tasks. r=marco Increases the max-run-time for all test tasks on ccov builds. MozReview-Commit-ID: KtArHMWKgbH --HG-- extra : rebase_source : 61b6831ba39f005992ce3ec5db5568ad9ce95a36
2018-03-15 00:49:48 +03:00
default: 5400
Bug 632954 - Enable tests on Android PGO; r=jmaher CLOSED TREE Differential Revision: https://phabricator.services.mozilla.com/D22827 --HG-- extra : source : 429c96e4de3234447b0aaf00214422ad84e98b83 extra : amend_source : c4e8383c36aad43b314c0125f7574c50ade76aac
2019-03-19 02:53:38 +03:00
run-on-projects:
by-test-platform:
Bug 1650208: run opt builds by default on autoland; shippable builds by default on central r=tomprince,ahal,marco Differential Revision: https://phabricator.services.mozilla.com/D83186
2020-07-27 19:25:40 +03:00
android-hw-.*(?<!-shippable)/opt: ['autoland']
Bug 1637542: Disable {linux64,win32,win64} opt and linux64 artifact builds on autoland. r=jmaher The opt builds were originally disabled in bug 1522111, but were re-enabled when webgpu was added. Differential Revision: https://phabricator.services.mozilla.com/D76906
2020-05-27 20:53:38 +03:00
android-hw-.*-api-16/(?:debug|pgo)?: ['trunk', 'mozilla-beta', 'mozilla-release']
Bug 1623355 - Part 3/9 - Rename android pgo tests to -shippable/opt and adjust run-on-platforms to cope. r=aki This keeps all tests that were running as pgo, continuing to run in the same places. Differential Revision: https://phabricator.services.mozilla.com/D74306
2020-05-21 19:29:34 +03:00
android-hw-.*-api-16-shippable/opt: ['trunk', 'mozilla-beta', 'mozilla-release']
Bug 1638260 - Remove all the 'try' values in run-on-projects r=ahal They are not doing anything as try will choose jobs anyway. And this is misleading for developers on what it is doing. Differential Revision: https://phabricator.services.mozilla.com/D75490
2020-05-15 18:01:19 +03:00
windows10-aarch64/.*: ['mozilla-central', 'mozilla-beta', 'mozilla-release']
Bug 632954 - Enable tests on Android PGO; r=jmaher CLOSED TREE Differential Revision: https://phabricator.services.mozilla.com/D22827 --HG-- extra : source : 429c96e4de3234447b0aaf00214422ad84e98b83 extra : amend_source : c4e8383c36aad43b314c0125f7574c50ade76aac
2019-03-19 02:53:38 +03:00
default: built-projects
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 1521879 - Part 7: Create new CI jobs for media mochitests with socket process enabled. r=ahal Differential Revision: https://phabricator.services.mozilla.com/D17942 --HG-- extra : moz-landing-system : lando
2019-02-26 00:52:13 +03:00
by-test-platform:
Bug 1610975: Enable socketprocess mochitests on android. r=jmaher Depends on D63198 Differential Revision: https://phabricator.services.mozilla.com/D63225 --HG-- extra : moz-landing-system : lando
2020-02-19 21:04:07 +03:00
android.*: ['socketprocess']
Bug 1662628 - disable mochitest-webgl2-ext, mochitest-webgl1-ext and mochitest-media on mac ccov r=jmaher,aryx Differential Revision: https://phabricator.services.mozilla.com/D89301
2020-09-08 16:54:09 +03:00
macosx.*64-ccov/.*: []
Bug 1607940 - Add webgl-ipc (gli) CI variant. r=ahal,jmaher Differential Revision: https://phabricator.services.mozilla.com/D83290
2020-07-22 01:56:54 +03:00
default: ['fission', 'socketprocess', 'webgl-ipc']
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
loopback-video: true
Bug 1577037 - Stop running all Fennec functional tests; r=bc Stop running all Fennec functional (non-performance) tests: - stop running all Android 4.3 tests - switch android-em-7 cppunit and android-hw jittest from the Fennec apk to the geckoview apk (no difference in behavior expected) - stop running Android 7.0 marionette tests, since they also run against Fennec - remove android-em-4.* references from taskcluster configs - remove android instance: extra-large references from taskcluster configs, since they only affect aws, which is no longer used for Android Android-hw raptor tests running against Fennec remain; I will prepare a separate patch for those. Differential Revision: https://phabricator.services.mozilla.com/D43684 --HG-- extra : moz-landing-system : lando
2019-09-04 18:58:36 +03:00
instance-size: large
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
chunks:
by-test-platform:
Bug 1498298 - Prepare to run packet.net geckoview tests against x86_64 opt/debug builds; r=me,a=test-only This doesn't actually run anything differently, yet.
2019-01-05 02:46:01 +03:00
android-em-7.*: 1
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
windows10-64.*: 1
Bug 1555454 - migrate mochitest-media to macosx1014 and turn off permafail tests r=gbrown,jmaher Changes: - rebalance chunk - turn off three tests that are nearly permafail Differential Revision: https://phabricator.services.mozilla.com/D34932 --HG-- extra : moz-landing-system : lando
2019-06-20 07:10:29 +03:00
macosx.*64.*/.*: 2
Bug 1605122 - Run Windows aarch64 mochitest-media as 1 chunk; r=jmaher aarch64 mochitest-media, when scheduled as 2 chunks, has only one manifest in one chunk -- and that manifest is skipped on aarch64! The other chunk runs fine, so we may as well run the suite as a single chunk. Differential Revision: https://phabricator.services.mozilla.com/D57804 --HG-- extra : moz-landing-system : lando
2019-12-19 18:33:55 +03:00
windows10-aarch64/.*: 1
Bug 1548965 - task efficiency: revisit mochitest-media chunking r=jmaher,gbrown Changes: - `android-hw` chunks reduced to 1 (from 3) - `windows10-aarch64` chunks reduced to 2 (from 3) - linux64.*/opt chunks reduced to 2 (from 3) - windows7.*/opt chunks reduced to 2 (from 3) Differential Revision: https://phabricator.services.mozilla.com/D30299 --HG-- extra : moz-landing-system : lando
2019-05-09 02:37:44 +03:00
windows7-32-shippable/.*: 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(-shippable|-devedition|-.*qr)/opt: 2
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
default: 3
mozharness:
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
mochitest-flavor: plain
chunked:
by-test-platform:
Bug 1426586 - Add android hardware test platforms for android-hw, r=gbrown,jmaher
2018-06-23 02:39:32 +03:00
android.*: false
Bug 1550826 - add initial support for osx mojave 10.14 to our CI. r=ahal add initial support for osx mojave 10.14 to our CI. Differential Revision: https://phabricator.services.mozilla.com/D30795 --HG-- extra : moz-landing-system : lando
2019-05-14 21:33:12 +03:00
macosx.*64.*: 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
windows10-64.*: false
default: true
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
tier:
by-test-platform:
Bug 1613690: Get mochitest-media running on android-em again. r=jmaher,jib,bryce Differential Revision: https://phabricator.services.mozilla.com/D63195 --HG-- extra : moz-landing-system : lando
2020-02-19 19:24:21 +03:00
android-em.*: 1
Bug 1543521 - demote windows10-aarch64 related tasks to tier 2 for the time being r=gbrown,jmaher Changes: - make windows10-aarch64 tests tier-2 by default Differential Revision: https://phabricator.services.mozilla.com/D27006 --HG-- extra : moz-landing-system : lando
2019-04-11 01:48:40 +03:00
windows10-aarch64.*: 2
Bug 1553955 - Promote mochitest-media to tier 1 on android-hw and demote to tier 2 on android-em r=jmaher Changes: __mochitest__ - demote `android-em` to tier 2 - promote `android-hw` to tier 1 - expand regex for `run-on-projects` specification to include all `android-em` instances, and restrict to `try` Differential Revision: https://phabricator.services.mozilla.com/D32541 --HG-- extra : moz-landing-system : lando
2019-05-25 00:58:40 +03:00
android-hw.*: 1
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
default: default
mochitest-plain-headless:
description: "Mochitest plain headless run"
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:
Bug 1583353 - [mozharness] Remove '-chunked' mochitest and jittest suite definitions, r=gbrown Having a distinction between -chunked and not adds unnecessary complexity. It's possible to simply remove them because: 1. The mozharness definitions for 'jittest' and 'jittest-chunked' are identical, so it is literally not serving any purpose. 2. The definitions for 'mochitest' only add either '--chunk-by-dir' or '--chunk-by-runtime'. Both of these are no-ops in the mochitest harness unless '--total-chunks' is also supplied. Therefore, if we ever use these suites without chunking (which I don't think we do anyway), then it'll still work fine as those options won't have any affect. Differential Revision: https://phabricator.services.mozilla.com/D51173 --HG-- extra : moz-landing-system : lando
2019-10-31 00:41:24 +03:00
name: mochitest-plain
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: M(h)
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
loopback-video: true
chunks:
by-test-platform:
Bug 1411342 - reduce chunks for mochitests on linux now that we run on faster hardware. r=gbrown
2017-10-27 21:06:38 +03:00
linux.*/debug: 16
default: 5
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
e10s: true
max-run-time: 5400
allow-software-gl-layers: false
Bug 1546452 - Run fewer headless mochitests; r=jmaher - stop mochitest-headless on windows10 - stop mochitest-headless on linux64/debug - make mochitest-headless tier-2 - make mochitest-headless run on m-c/try Differential Revision: https://phabricator.services.mozilla.com/D28715 --HG-- extra : moz-landing-system : lando
2019-04-25 12:15:29 +03:00
tier: 2
Bug 1638260 - Remove all the 'try' values in run-on-projects r=ahal They are not doing anything as try will choose jobs anyway. And this is misleading for developers on what it is doing. Differential Revision: https://phabricator.services.mozilla.com/D75490
2020-05-15 18:01:19 +03:00
run-on-projects: ['mozilla-central']
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
mozharness:
mochitest-flavor: plain
chunked: true
extra-options:
- --headless
mochitest-valgrind:
description: "Mochitest plain Valgrind run"
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:
Bug 1523303 - Align mozharness suite names with the ones in 'moztest.resolve', r=gbrown This officially makes 'moztest.resolve' the source of truth when it comes to suite names. It aligns that file with the names used in both the desktop_unittest and android_emulator_unittest scripts. Differential Revision: https://phabricator.services.mozilla.com/D27555 --HG-- extra : moz-landing-system : lando
2019-04-23 01:32:34 +03:00
name: mochitest-valgrind-plain
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: M-V()
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: []
tier: 3
loopback-video: true
chunks: 40
max-run-time: 14400
# We could re-enable e10s later.
# There's no intrinsic reason not to use it.
e10s: false
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 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
mozharness:
mochitest-flavor: plain
chunked: true
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
mochitest-webgl1-core:
description: "Mochitest webgl1-core run"
treeherder-symbol: M(gl1c)
Bug 1598746 - Adjust some mochitest and reftest SCHEDULES.exclusive entries; r=ahal Use finer granularity for some reftest/mochitest SCHEDULES.exclusive entries, so that reftest-plain does not run when only crashtests are modified, and vice versa; similarly, break up mochitest into mochitest/browser-chrome/chrome/ a11y. Use schedules-component instead of category. Differential Revision: https://phabricator.services.mozilla.com/D60085 --HG-- extra : moz-landing-system : lando
2020-03-24 17:55:28 +03:00
schedules-component: mochitest-plain
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
virtualization: virtual-with-gpu
Bug 1607940 - Add webgl-ipc (gli) CI variant. r=ahal,jmaher Differential Revision: https://phabricator.services.mozilla.com/D83290
2020-07-22 01:56:54 +03:00
variants:
by-test-platform:
android.*: []
default: ['webgl-ipc']
Bug 1548649 - remove all linux32 tests except for shippable, and restrict those tests to web-platform-tests r=jmaher Changes: - edited `linux32-tests` to include only web-platform-tests - removed references to other `linux32` platforms from `test-platforms.yml` other than `linux32-shippable/opt` Differential Revision: https://phabricator.services.mozilla.com/D29792 --HG-- extra : moz-landing-system : lando
2019-05-21 19:04:06 +03:00
e10s: true
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
loopback-video: true
Bug 1620460 - turn off all tests except crashtest, reftest and mochitest-media on windows10-aarch64 r=jmaher Changes: Remove all tests other than `reftests`, `crashtests` and `mochitest-media` for windows10-aarch64. Important changes are in `taskcluster/ci/test/test-platforms.yml` and `taskcluster/ci/test/test-sets.yml`. I've gone ahead and removed the windows10-aarch64 specific entries in the YAML files as well. Differential Revision: https://phabricator.services.mozilla.com/D65654 --HG-- extra : moz-landing-system : lando
2020-03-06 03:15:43 +03:00
tier: default
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
max-run-time:
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
macosx.*64-ccov/.*: 7200
Bug 1607563 - Run mochitest-webgl/webgpu CI on aarch64 and use 30m timeouts. r=kvark Differential Revision: https://phabricator.services.mozilla.com/D59972 --HG-- extra : moz-landing-system : lando
2020-01-15 22:21:24 +03:00
default: 1800
Bug 1641948: remove android opt builds from non-mozilla-central branches; reduce frequency of fat-aar builds. r=Callek Differential Revision: https://phabricator.services.mozilla.com/D78547
2020-06-11 22:25:07 +03:00
run-on-projects:
by-test-platform:
android-hw-.*(?<!-shippable)/opt: ['mozilla-central', 'mozilla-beta', 'mozilla-release']
Bug 1650208: run opt builds by default on autoland; shippable builds by default on central r=tomprince,ahal,marco Differential Revision: https://phabricator.services.mozilla.com/D83186
2020-07-27 19:25:40 +03:00
android-hw.*aarch.*-shippable/opt: ['mozilla-central']
Bug 1641948: remove android opt builds from non-mozilla-central branches; reduce frequency of fat-aar builds. r=Callek Differential Revision: https://phabricator.services.mozilla.com/D78547
2020-06-11 22:25:07 +03:00
default: built-projects
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
# Bug 1296733: llvmpipe with mesa 9.2.1 lacks thread safety
allow-software-gl-layers: false
mozharness:
mochitest-flavor: plain
mochitest-webgl1-ext:
description: "Mochitest webgl1-ext run"
treeherder-symbol: M(gl1e)
Bug 1598746 - Adjust some mochitest and reftest SCHEDULES.exclusive entries; r=ahal Use finer granularity for some reftest/mochitest SCHEDULES.exclusive entries, so that reftest-plain does not run when only crashtests are modified, and vice versa; similarly, break up mochitest into mochitest/browser-chrome/chrome/ a11y. Use schedules-component instead of category. Differential Revision: https://phabricator.services.mozilla.com/D60085 --HG-- extra : moz-landing-system : lando
2020-03-24 17:55:28 +03:00
schedules-component: mochitest-plain
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
virtualization: virtual-with-gpu
Bug 1607940 - Add webgl-ipc (gli) CI variant. r=ahal,jmaher Differential Revision: https://phabricator.services.mozilla.com/D83290
2020-07-22 01:56:54 +03:00
variants:
by-test-platform:
android.*: []
Bug 1662628 - disable mochitest-webgl2-ext, mochitest-webgl1-ext and mochitest-media on mac ccov r=jmaher,aryx Differential Revision: https://phabricator.services.mozilla.com/D89301
2020-09-08 16:54:09 +03:00
macosx.*64-ccov/.*: []
Bug 1607940 - Add webgl-ipc (gli) CI variant. r=ahal,jmaher Differential Revision: https://phabricator.services.mozilla.com/D83290
2020-07-22 01:56:54 +03:00
default: ['webgl-ipc']
Bug 1606039 - Enable webgl1-core/1-ext/2-core tests on Android HW. r=lsalzman Differential Revision: https://phabricator.services.mozilla.com/D58906 --HG-- extra : moz-landing-system : lando
2020-01-07 22:19:38 +03:00
chunks:
by-test-platform:
android.*: 2
default: 1
Bug 1548649 - remove all linux32 tests except for shippable, and restrict those tests to web-platform-tests r=jmaher Changes: - edited `linux32-tests` to include only web-platform-tests - removed references to other `linux32` platforms from `test-platforms.yml` other than `linux32-shippable/opt` Differential Revision: https://phabricator.services.mozilla.com/D29792 --HG-- extra : moz-landing-system : lando
2019-05-21 19:04:06 +03:00
e10s: true
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: FDWdu1J0end --HG-- extra : rebase_source : a47d88cb2c5eb82e4dfaa9e58d76acbf0736d35d
2018-06-26 06:23:33 +03:00
loopback-video: true
Bug 1620460 - turn off all tests except crashtest, reftest and mochitest-media on windows10-aarch64 r=jmaher Changes: Remove all tests other than `reftests`, `crashtests` and `mochitest-media` for windows10-aarch64. Important changes are in `taskcluster/ci/test/test-platforms.yml` and `taskcluster/ci/test/test-sets.yml`. I've gone ahead and removed the windows10-aarch64 specific entries in the YAML files as well. Differential Revision: https://phabricator.services.mozilla.com/D65654 --HG-- extra : moz-landing-system : lando
2020-03-06 03:15:43 +03:00
tier: default
Bug 1610321 - Increase max-run-time for mochitest-webgl1-ext; r=egao Avoid frequent intermittent test failures for exceeding max-run-time by increasing mochitest-webgl1-ext max-run-time from 30 minutes to 45 minutes. This is immediately an issue on Windows 7 MinGW debug, but other platforms are close to the 30 minute limit, so we may as well increase it across the board. Differential Revision: https://phabricator.services.mozilla.com/D60420 --HG-- extra : moz-landing-system : lando
2020-01-20 21:26:40 +03:00
max-run-time: 2700
Bug 1641948: remove android opt builds from non-mozilla-central branches; reduce frequency of fat-aar builds. r=Callek Differential Revision: https://phabricator.services.mozilla.com/D78547
2020-06-11 22:25:07 +03:00
run-on-projects:
by-test-platform:
android-hw-.*(?<!-shippable)/opt: ['mozilla-central', 'mozilla-beta', 'mozilla-release']
Bug 1650208: run opt builds by default on autoland; shippable builds by default on central r=tomprince,ahal,marco Differential Revision: https://phabricator.services.mozilla.com/D83186
2020-07-27 19:25:40 +03:00
android-hw.*aarch.*-shippable/opt: ['mozilla-central']
Bug 1641948: remove android opt builds from non-mozilla-central branches; reduce frequency of fat-aar builds. r=Callek Differential Revision: https://phabricator.services.mozilla.com/D78547
2020-06-11 22:25:07 +03:00
default: built-projects
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
# Bug 1296733: llvmpipe with mesa 9.2.1 lacks thread safety
allow-software-gl-layers: false
mozharness:
mochitest-flavor: plain
Bug 1606039 - Enable webgl1-core/1-ext/2-core tests on Android HW. r=lsalzman Differential Revision: https://phabricator.services.mozilla.com/D58906 --HG-- extra : moz-landing-system : lando
2020-01-07 22:19:38 +03:00
chunked: true
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
mochitest-webgl2-core:
description: "Mochitest webgl2-core run"
treeherder-symbol: M(gl2c)
Bug 1598746 - Adjust some mochitest and reftest SCHEDULES.exclusive entries; r=ahal Use finer granularity for some reftest/mochitest SCHEDULES.exclusive entries, so that reftest-plain does not run when only crashtests are modified, and vice versa; similarly, break up mochitest into mochitest/browser-chrome/chrome/ a11y. Use schedules-component instead of category. Differential Revision: https://phabricator.services.mozilla.com/D60085 --HG-- extra : moz-landing-system : lando
2020-03-24 17:55:28 +03:00
schedules-component: mochitest-plain
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
virtualization: virtual-with-gpu
Bug 1607940 - Add webgl-ipc (gli) CI variant. r=ahal,jmaher Differential Revision: https://phabricator.services.mozilla.com/D83290
2020-07-22 01:56:54 +03:00
variants:
by-test-platform:
android.*: []
default: ['webgl-ipc']
Bug 1606039 - Enable webgl1-core/1-ext/2-core tests on Android HW. r=lsalzman Differential Revision: https://phabricator.services.mozilla.com/D58906 --HG-- extra : moz-landing-system : lando
2020-01-07 22:19:38 +03:00
chunks:
by-test-platform:
android.*: 2
default: 1
Bug 1548649 - remove all linux32 tests except for shippable, and restrict those tests to web-platform-tests r=jmaher Changes: - edited `linux32-tests` to include only web-platform-tests - removed references to other `linux32` platforms from `test-platforms.yml` other than `linux32-shippable/opt` Differential Revision: https://phabricator.services.mozilla.com/D29792 --HG-- extra : moz-landing-system : lando
2019-05-21 19:04:06 +03:00
e10s: true
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
loopback-video: true
Bug 1620460 - turn off all tests except crashtest, reftest and mochitest-media on windows10-aarch64 r=jmaher Changes: Remove all tests other than `reftests`, `crashtests` and `mochitest-media` for windows10-aarch64. Important changes are in `taskcluster/ci/test/test-platforms.yml` and `taskcluster/ci/test/test-sets.yml`. I've gone ahead and removed the windows10-aarch64 specific entries in the YAML files as well. Differential Revision: https://phabricator.services.mozilla.com/D65654 --HG-- extra : moz-landing-system : lando
2020-03-06 03:15:43 +03:00
tier: default
Bug 1607563 - Run mochitest-webgl/webgpu CI on aarch64 and use 30m timeouts. r=kvark Differential Revision: https://phabricator.services.mozilla.com/D59972 --HG-- extra : moz-landing-system : lando
2020-01-15 22:21:24 +03:00
max-run-time: 1800
Bug 1641948: remove android opt builds from non-mozilla-central branches; reduce frequency of fat-aar builds. r=Callek Differential Revision: https://phabricator.services.mozilla.com/D78547
2020-06-11 22:25:07 +03:00
run-on-projects:
by-test-platform:
android-hw-.*(?<!-shippable)/opt: ['mozilla-central', 'mozilla-beta', 'mozilla-release']
Bug 1650208: run opt builds by default on autoland; shippable builds by default on central r=tomprince,ahal,marco Differential Revision: https://phabricator.services.mozilla.com/D83186
2020-07-27 19:25:40 +03:00
android-hw.*aarch.*-shippable/opt: ['mozilla-central']
Bug 1641948: remove android opt builds from non-mozilla-central branches; reduce frequency of fat-aar builds. r=Callek Differential Revision: https://phabricator.services.mozilla.com/D78547
2020-06-11 22:25:07 +03:00
default: built-projects
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: FDWdu1J0end --HG-- extra : rebase_source : a47d88cb2c5eb82e4dfaa9e58d76acbf0736d35d
2018-06-26 06:23:33 +03:00
# Bug 1296733: llvmpipe with mesa 9.2.1 lacks thread safety
allow-software-gl-layers: false
mozharness:
mochitest-flavor: plain
Bug 1606039 - Enable webgl1-core/1-ext/2-core tests on Android HW. r=lsalzman Differential Revision: https://phabricator.services.mozilla.com/D58906 --HG-- extra : moz-landing-system : lando
2020-01-07 22:19:38 +03:00
chunked: true
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
mochitest-webgl2-ext:
description: "Mochitest webgl2-ext run"
treeherder-symbol: M(gl2e)
Bug 1598746 - Adjust some mochitest and reftest SCHEDULES.exclusive entries; r=ahal Use finer granularity for some reftest/mochitest SCHEDULES.exclusive entries, so that reftest-plain does not run when only crashtests are modified, and vice versa; similarly, break up mochitest into mochitest/browser-chrome/chrome/ a11y. Use schedules-component instead of category. Differential Revision: https://phabricator.services.mozilla.com/D60085 --HG-- extra : moz-landing-system : lando
2020-03-24 17:55:28 +03:00
schedules-component: mochitest-plain
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
virtualization: virtual-with-gpu
Bug 1607940 - Add webgl-ipc (gli) CI variant. r=ahal,jmaher Differential Revision: https://phabricator.services.mozilla.com/D83290
2020-07-22 01:56:54 +03:00
variants:
by-test-platform:
android.*: []
Bug 1662628 - disable mochitest-webgl2-ext, mochitest-webgl1-ext and mochitest-media on mac ccov r=jmaher,aryx Differential Revision: https://phabricator.services.mozilla.com/D89301
2020-09-08 16:54:09 +03:00
macosx.*64-ccov/.*: []
Bug 1607940 - Add webgl-ipc (gli) CI variant. r=ahal,jmaher Differential Revision: https://phabricator.services.mozilla.com/D83290
2020-07-22 01:56:54 +03:00
default: ['webgl-ipc']
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
chunks: 4
Bug 1548649 - remove all linux32 tests except for shippable, and restrict those tests to web-platform-tests r=jmaher Changes: - edited `linux32-tests` to include only web-platform-tests - removed references to other `linux32` platforms from `test-platforms.yml` other than `linux32-shippable/opt` Differential Revision: https://phabricator.services.mozilla.com/D29792 --HG-- extra : moz-landing-system : lando
2019-05-21 19:04:06 +03:00
e10s: true
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
loopback-video: true
Bug 1620460 - turn off all tests except crashtest, reftest and mochitest-media on windows10-aarch64 r=jmaher Changes: Remove all tests other than `reftests`, `crashtests` and `mochitest-media` for windows10-aarch64. Important changes are in `taskcluster/ci/test/test-platforms.yml` and `taskcluster/ci/test/test-sets.yml`. I've gone ahead and removed the windows10-aarch64 specific entries in the YAML files as well. Differential Revision: https://phabricator.services.mozilla.com/D65654 --HG-- extra : moz-landing-system : lando
2020-03-06 03:15:43 +03:00
tier: default
Bug 1610598 - Increase max-run-time for mochitest-webgl2-ext; r=jmaher Avoid intermittent test failures for exceeding max-run-time by increasing mochitest-webgl2-ext max-run-time from 30 minutes to 45 minutes. This is immediately an issue on Windows 7 (MinGW) debug, but other platforms are close to the 30 minute limit, so we may as well increase it across the board. Differential Revision: https://phabricator.services.mozilla.com/D60560 --HG-- extra : moz-landing-system : lando
2020-01-21 23:14:56 +03:00
max-run-time: 2700
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
# Bug 1296733: llvmpipe with mesa 9.2.1 lacks thread safety
allow-software-gl-layers: false
mozharness:
mochitest-flavor: plain
chunked: true
mochitest-webgl2-deqp:
description: "Mochitest webgl2-deqp run"
treeherder-symbol: M(gl2d)
Bug 1598746 - Adjust some mochitest and reftest SCHEDULES.exclusive entries; r=ahal Use finer granularity for some reftest/mochitest SCHEDULES.exclusive entries, so that reftest-plain does not run when only crashtests are modified, and vice versa; similarly, break up mochitest into mochitest/browser-chrome/chrome/ a11y. Use schedules-component instead of category. Differential Revision: https://phabricator.services.mozilla.com/D60085 --HG-- extra : moz-landing-system : lando
2020-03-24 17:55:28 +03:00
schedules-component: mochitest-plain
Bug 1419475 - Re-enable some mochitest suites using virtual-with-gpu that were failing with Windows ccov builds. r=jmaher --HG-- extra : rebase_source : 71c3556631b15e7f4aaee3d6c12a7176afff7953
2018-11-26 12:45:41 +03:00
run-on-projects: [] # Don't run this for now.
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
virtualization: virtual-with-gpu
Bug 1607940 - Add webgl-ipc (gli) CI variant. r=ahal,jmaher Differential Revision: https://phabricator.services.mozilla.com/D83290
2020-07-22 01:56:54 +03:00
variants:
by-test-platform:
android.*: []
default: ['webgl-ipc']
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
chunks: 4
Bug 1548649 - remove all linux32 tests except for shippable, and restrict those tests to web-platform-tests r=jmaher Changes: - edited `linux32-tests` to include only web-platform-tests - removed references to other `linux32` platforms from `test-platforms.yml` other than `linux32-shippable/opt` Differential Revision: https://phabricator.services.mozilla.com/D29792 --HG-- extra : moz-landing-system : lando
2019-05-21 19:04:06 +03:00
e10s: true
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
loopback-video: true
Bug 1620460 - turn off all tests except crashtest, reftest and mochitest-media on windows10-aarch64 r=jmaher Changes: Remove all tests other than `reftests`, `crashtests` and `mochitest-media` for windows10-aarch64. Important changes are in `taskcluster/ci/test/test-platforms.yml` and `taskcluster/ci/test/test-sets.yml`. I've gone ahead and removed the windows10-aarch64 specific entries in the YAML files as well. Differential Revision: https://phabricator.services.mozilla.com/D65654 --HG-- extra : moz-landing-system : lando
2020-03-06 03:15:43 +03:00
tier: default
Bug 1607563 - Run mochitest-webgl/webgpu CI on aarch64 and use 30m timeouts. r=kvark Differential Revision: https://phabricator.services.mozilla.com/D59972 --HG-- extra : moz-landing-system : lando
2020-01-15 22:21:24 +03:00
max-run-time: 1800
Bug 1471112 - Split mochitest-gl into mochitest-webgl[1,2]-[core,ext] - r=gbrown Also include webgl2-deqp, which we would like to run eventually, but not yet. MozReview-Commit-ID: CY4hYCI95ws --HG-- extra : rebase_source : 9973df0f905bb65d2e8b8c66a6a57e8869e527c1
2018-06-26 06:23:33 +03:00
# Bug 1296733: llvmpipe with mesa 9.2.1 lacks thread safety
allow-software-gl-layers: false
mozharness:
mochitest-flavor: plain
chunked: true
Bug 1545147 - Run remote agent's mochitests in a distinct "remote" job. r=ahal Differential Revision: https://phabricator.services.mozilla.com/D32028 --HG-- extra : moz-landing-system : lando
2019-06-17 16:57:03 +03:00
Bug 1585683 - Add mochitest-webgpu jobs, add subsuite = webgpu. r=jmaher,kvark Differential Revision: https://phabricator.services.mozilla.com/D58892 --HG-- extra : moz-landing-system : lando
2020-01-08 01:42:07 +03:00
mochitest-webgpu:
description: "Mochitest webgpu run"
treeherder-symbol: M(webgpu)
Bug 1598746 - Adjust some mochitest and reftest SCHEDULES.exclusive entries; r=ahal Use finer granularity for some reftest/mochitest SCHEDULES.exclusive entries, so that reftest-plain does not run when only crashtests are modified, and vice versa; similarly, break up mochitest into mochitest/browser-chrome/chrome/ a11y. Use schedules-component instead of category. Differential Revision: https://phabricator.services.mozilla.com/D60085 --HG-- extra : moz-landing-system : lando
2020-03-24 17:55:28 +03:00
schedules-component: mochitest-plain
Bug 1585683 - Add mochitest-webgpu jobs, add subsuite = webgpu. r=jmaher,kvark Differential Revision: https://phabricator.services.mozilla.com/D58892 --HG-- extra : moz-landing-system : lando
2020-01-08 01:42:07 +03:00
virtualization: virtual-with-gpu
e10s: true
loopback-video: true
Bug 1646511: disable webgpu tests for mingw builds on autoland r=marco Differential Revision: https://phabricator.services.mozilla.com/D81139
2020-07-01 22:54:04 +03:00
run-on-projects:
by-test-platform:
.*mingw.*: ["release"]
Bug 1650208: run opt builds by default on autoland; shippable builds by default on central r=tomprince,ahal,marco Differential Revision: https://phabricator.services.mozilla.com/D83186
2020-07-27 19:25:40 +03:00
.*shippable.*: ["mozilla-central"]
Bug 1646511: disable webgpu tests for mingw builds on autoland r=marco Differential Revision: https://phabricator.services.mozilla.com/D81139
2020-07-01 22:54:04 +03:00
default: ["trunk"]
Bug 1620460 - turn off all tests except crashtest, reftest and mochitest-media on windows10-aarch64 r=jmaher Changes: Remove all tests other than `reftests`, `crashtests` and `mochitest-media` for windows10-aarch64. Important changes are in `taskcluster/ci/test/test-platforms.yml` and `taskcluster/ci/test/test-sets.yml`. I've gone ahead and removed the windows10-aarch64 specific entries in the YAML files as well. Differential Revision: https://phabricator.services.mozilla.com/D65654 --HG-- extra : moz-landing-system : lando
2020-03-06 03:15:43 +03:00
tier: default
Bug 1585683 - Add mochitest-webgpu jobs, add subsuite = webgpu. r=jmaher,kvark Differential Revision: https://phabricator.services.mozilla.com/D58892 --HG-- extra : moz-landing-system : lando
2020-01-08 01:42:07 +03:00
max-run-time:
by-test-platform:
macosx.*64-ccov/.*: 7200
Bug 1607563 - Run mochitest-webgl/webgpu CI on aarch64 and use 30m timeouts. r=kvark Differential Revision: https://phabricator.services.mozilla.com/D59972 --HG-- extra : moz-landing-system : lando
2020-01-15 22:21:24 +03:00
default: 1800
Bug 1585683 - Add mochitest-webgpu jobs, add subsuite = webgpu. r=jmaher,kvark Differential Revision: https://phabricator.services.mozilla.com/D58892 --HG-- extra : moz-landing-system : lando
2020-01-08 01:42:07 +03:00
# Bug 1296733: llvmpipe with mesa 9.2.1 lacks thread safety
allow-software-gl-layers: false
mozharness:
mochitest-flavor: plain
Bug 1545147 - Run remote agent's mochitests in a distinct "remote" job. r=ahal Differential Revision: https://phabricator.services.mozilla.com/D32028 --HG-- extra : moz-landing-system : lando
2019-06-17 16:57:03 +03:00
mochitest-remote:
description: "Mochitest for the remote agent (/remote folder)"
suite:
name: mochitest-remote
treeherder-symbol: M(remote)
loopback-video: true
Bug 1621754 - run mochitest-remote shippable but not opt on autoland, r=jmaher. Differential Revision: https://phabricator.services.mozilla.com/D73038
2020-04-29 18:13:32 +03:00
run-on-projects:
by-test-platform:
Bug 1650208: run opt builds by default on autoland; shippable builds by default on central r=tomprince,ahal,marco Differential Revision: https://phabricator.services.mozilla.com/D83186
2020-07-27 19:25:40 +03:00
.*shippable.*: ["mozilla-central"]
(linux1804-64|windows7-32|windows10-64|macosx1014-64)(?:-qr)?/opt: ['integration']
Bug 1638260 - Remove all the 'try' values in run-on-projects r=ahal They are not doing anything as try will choose jobs anyway. And this is misleading for developers on what it is doing. Differential Revision: https://phabricator.services.mozilla.com/D75490
2020-05-15 18:01:19 +03:00
default: ["trunk"]
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-run-on-projects: []
fission-tier: 2
Bug 1545147 - Run remote agent's mochitests in a distinct "remote" job. r=ahal Differential Revision: https://phabricator.services.mozilla.com/D32028 --HG-- extra : moz-landing-system : lando
2019-06-17 16:57:03 +03:00
max-run-time: 5400
mozharness:
mochitest-flavor: browser
Bug 1617626 - [remote] Enable trace level logs for browser-chrome tests in CI. r=ahal Differential Revision: https://phabricator.services.mozilla.com/D68644 --HG-- extra : moz-landing-system : lando
2020-03-30 23:37:17 +03:00
extra-options:
- --setpref=remote.log.level=Trace