browsertime android fenix and refbrow jobs created for central when they should be "try" only
Categories
(Testing :: Raptor, defect, P1)
Tracking
(Not tracked)
People
(Reporter: rwood, Assigned: rwood)
References
(Blocks 1 open bug)
Details
I think there might be an issue in the raptor taskcluster transform. In browsertime-mobile.yml
if you set the default so the tests on fenix and refbrow will run on 'try' only, like this:
run-on-projects:
by-app:
fenix: []
geckoview: ["mozilla-central", "try"]
refbrow: []
In reality the tests run on all three apps on "mozilla-central" and "try" even though fenix and refbrow should only run on "try". In the browsertime-tp6m-1 test definition in the same config we use this:
apps: ["fenix", "geckoview", "refbrow"]
Perhaps the transform building the jobs out for each app is adding jobs for each app on all branches instead of "try" only for fenix and refbrow? Just guessing.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•4 years ago
|
||
I grabbed a 'parameters.yml' from a D decision task on central then ran (with existing configs/transforms):
./mach taskgraph full -p ../Downloads/parameters.yml —json > rw-taskgraph-before.json
Then I modified the browsertime-tp6m transform and added 'fenix' to the apps list here:
https://searchfox.org/mozilla-central/rev/c61720a7d0c094d772059f9d6a7844eb7619f107/taskcluster/ci/test/browsertime-mobile.yml#57
Then ran taskgraph again:
./mach taskgraph full -p ../Downloads/parameters.yml —json > rw-taskgraph-after.json
And diffed the two .json files and I can see the browsertime android fenix jobs added as expected, and in each one I see:
"run_on_projects": [],
Which is correct! So I don't see how these new jobs would run on central, my understanding is '[]' means try only...
Assignee | ||
Comment 2•4 years ago
|
||
In the patch in Bug 1592063 I added "fenix" to the apps list for browsertime-tp6m (but have by-app: fenix: []
) so after that merges I'll see if those jobs are unexpectedly running on central or if just enabled for try only as expected. Hopefully it's fine and this bug can be closed out.
Assignee | ||
Comment 3•4 years ago
|
||
Good news, it's working fine, with Fenix now included in the 'apps' list in the browsertime-tp6m taskcluster config entry, it is not running on central, only on try as expected. Must have been a one time thing when I first spotted it, or else I was misunderstanding and looking at the wrong jobs.
Assignee | ||
Comment 4•4 years ago
|
||
Meant to add a link to latest central:
Description
•