Determine what we should do with the Chromium-nightly browser tests
Categories
(Testing :: Raptor, task, P2)
Tracking
(Not tracked)
People
(Reporter: sparky, Unassigned)
References
Details
(Whiteboard: [fxp-decision])
After we get chromium-as-release running, we’ll need to see if we still want to have the nightly version available. If not, we should disable them.
|
Reporter | |
Updated•3 years ago
|
|
||
Updated•3 years ago
|
|
|
Reporter | |
Comment 1•3 years ago
|
||
:bas, what do you think about this? After the chromium-as-release patch lands, I don't think we'll need to keep running with the chromium-nightly builds since these release ones are more representative.
|
|
Reporter | |
Comment 2•3 years ago
|
||
(In reply to Greg Mierzwinski [:sparky] from comment #1)
:bas, what do you think about this? After the chromium-as-release patch lands, I don't think we'll need to keep running with the chromium-nightly builds since these release ones are more representative.
|
||
Updated•3 years ago
|
|
||
Comment 3•3 years ago
|
||
(In reply to Greg Mierzwinski [:sparky] from comment #2)
(In reply to Greg Mierzwinski [:sparky] from comment #1)
:bas, what do you think about this? After the chromium-as-release patch lands, I don't think we'll need to keep running with the chromium-nightly builds since these release ones are more representative.
Correct, I also think eventually we should only run Chrome on Chrome releases rather than daily, and then actually make sure we run the latest version. Right now in CI you have no idea what you're getting and it can be anywhere between 109 and 112 at the moment it appears.
|
|
Reporter | |
Comment 4•3 years ago
|
||
See these bugs:
(1) https://bugzilla.mozilla.org/show_bug.cgi?id=1844562
(2) https://bugzilla.mozilla.org/show_bug.cgi?id=1844560
Description
•