tor-browser

The Tor Browser
git clone https://git.dasho.dev/tor-browser.git
Log | Files | Refs | README | LICENSE

commit e61c42a6baf291ccab83bdd338a73a4c0166641b
parent 8bffb8f28dadfe6a26ecc5ff99c0a9a9182dd774
Author: Mike Conley <mconley@mozilla.com>
Date:   Thu,  2 Oct 2025 20:57:04 +0000

Bug 1990100 - Make nt-trainhop jobs tier 2 on all platforms. r=jmaher,home-newtab-reviewers,nbarrett

Differential Revision: https://phabricator.services.mozilla.com/D266678

Diffstat:
Mbrowser/extensions/newtab/docs/v2-system-addon/train_hopping.md | 6++----
Mtaskcluster/kinds/mochitest/kind.yml | 4++--
2 files changed, 4 insertions(+), 6 deletions(-)

diff --git a/browser/extensions/newtab/docs/v2-system-addon/train_hopping.md b/browser/extensions/newtab/docs/v2-system-addon/train_hopping.md @@ -179,9 +179,9 @@ This means that if we add a new feature to New Tab that is solely contained with This also means we can potentially catch train-hop compatibility failures with these jobs. Anything that causes New Tab to fail to initialize or pass any of its `mochitest-browser` tests will naturally cause the job to fail, which can be an early signal that train-hop compatibility has been broken. -These tests are currently `Tier 3`, so they are hidden by default. They can be revealed by clicking the `3` button in Treeherder, and searching for `trainhop` in the search field. The jobs run on all Tier 1 desktop platforms. +These tests are currently `Tier 2`, so failures do not automatically result in a backout - however, we should strive to fix failures as soon as they occur in order to unblock train-hopping. The jobs run on all Tier 1 desktop platforms. -[This link](https://treeherder.mozilla.org/jobs?repo=mozilla-central&tier=1%2C2%2C3&searchStr=trainhop) should show the most recent `trainhop` jobs occurring on `main`. +[This link](https://treeherder.mozilla.org/jobs?repo=mozilla-central&searchStr=trainhop) should show the most recent `trainhop` jobs occurring on `main`. The Treeherder "group name" for those jobs is `nt-trainhop`, and the symbol for the `mochitest-browser` tests are `Mbc-beta` and `Mbc-release` for the tests running on the most recent Beta and Release versions, respectively. @@ -215,8 +215,6 @@ When attempting to fix the issue, it may be useful to push those changes to `try `./mach try --preset desktop-newtab-trainhop --artifact` -Note that these try jobs are currently `Tier 3`, meaning that they’ll not be visible in Treeherder by default. You must click on the `3` toggle near the top of Treeherder to make them visible. - # Performing a train-hop This procedure involves using internal tooling for signing releases, and is [documented on Confluence.](https://mozilla-hub.atlassian.net/wiki/spaces/FPS/pages/1785135275/Performing+a+train-hop) diff --git a/taskcluster/kinds/mochitest/kind.yml b/taskcluster/kinds/mochitest/kind.yml @@ -1276,7 +1276,7 @@ tasks: windows1.*-64.*(-shippable)?/.*: ['trunk'] default: [] treeherder-symbol: nt-trainhop(Mbc-beta) - tier: 3 + tier: 2 loopback-video: true test-manifest-loader: null # don't load tests in the taskgraph mozharness: @@ -1324,7 +1324,7 @@ tasks: windows1.*-64.*(-shippable)?/.*: ['trunk'] default: [] treeherder-symbol: nt-trainhop(Mbc-release) - tier: 3 + tier: 2 loopback-video: true test-manifest-loader: null # don't load tests in the taskgraph mozharness: