Run browser chrome and puppeteer job on release and beta branches
Categories
(Remote Protocol :: Agent, defect, P1)
Tracking
(firefox87 fixed)
Tracking | Status | |
---|---|---|
firefox87 | --- | fixed |
People
(Reporter: jdescottes, Assigned: whimboo)
References
Details
Attachments
(2 files)
The current puppeteer job only runs on trunk.
As we want to switch puppeteer to use Firefox Release by default instead of Nightly, we should make sure to run the job on beta/release as well in order to catch potential issues with those builds.
See puppeteer job definition at:
https://searchfox.org/mozilla-central/rev/a23e65c5d69a821f61d14c8ec1f69a120e3f77d1/taskcluster/ci/source-test/remote.yml#40
Reporter | ||
Comment 1•4 years ago
•
|
||
Henrik, is this just about modify the job definition (I imagine we can add beta
& release
to run-on-projects) or do you know about any other blocker?
Assignee | ||
Comment 2•4 years ago
|
||
Mostly yes, but lets wait on bug 1693021 first. The webrender flag should only be set for trunk. I will get to it soon.
Assignee | ||
Comment 3•4 years ago
|
||
I was able to get the webrender pieces done via a command line argument, so it's not intersecting with necessary changes in the Taskcluster confiig.
Assignee | ||
Comment 4•4 years ago
|
||
Doh, we even don't run our browser chrome tests on beta/release, and maybe xpcshell tests neither. I will have to take a look at it today!
Assignee | ||
Comment 5•4 years ago
|
||
Note that this was missed when landing the changes via bug 1606604.
Assignee | ||
Comment 6•4 years ago
|
||
Assignee | ||
Comment 7•4 years ago
|
||
Depends on D105449
Comment 9•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/3a652fa3c606
https://hg.mozilla.org/mozilla-central/rev/6d7590bfd8d3
Description
•