The variant `wayland` expiration is on 2023-03-01
Categories
(Testing :: General, task)
Tracking
(firefox-esr102 unaffected, firefox109 wontfix, firefox110 wontfix, firefox111 fixed)
| Tracking | Status | |
|---|---|---|
| firefox-esr102 | --- | unaffected |
| firefox109 | --- | wontfix |
| firefox110 | --- | wontfix |
| firefox111 | --- | fixed |
People
(Reporter: release-mgmt-account-bot, Assigned: jmaher)
References
(Blocks 1 open bug)
Details
(Whiteboard: [variant-expiration])
Attachments
(1 file)
If the variant is not used anymore, please drop it from the variants.yml file. If there is a need to keep the variant, please submit a patch to modify the expiration date. Variants will not be scheduled to run after the expiration date.
This bug will be closed automatically once the variant is dropped or the expiration date is updated in the variants.yml file.
More information about variants can be found on Firefox Source Docs.
Note: please do not edit the bug summery or close the bug, it could break the automation.
Updated•3 years ago
|
| Reporter | ||
Comment 1•3 years ago
|
||
Set release status flags based on info from the regressing bug 1787329
:jmaher, since you are the author of the regressor, bug 1787329, could you take a look? Also, could you set the severity field?
For more information, please visit auto_nag documentation.
| Reporter | ||
Comment 2•3 years ago
|
||
This bug has the keyword regression, so its type should be defect.
| Assignee | ||
Comment 3•3 years ago
|
||
:stransky- I see you had added a lot of the original Wayland variant logic, but we are not running any tests with this. I know :ahal is working on (or will be soon) a docker wayland image of ubuntu 22.04, so there are resources assigned now to get a formal platform setup for wayland.
Is there usage that you are aware of of the wayland variant? I am happy to keep it if this is being used, otherwise, cleaning up things makes for good code maintenance.
Updated•3 years ago
|
Comment 4•3 years ago
|
||
(In reply to Joel Maher ( :jmaher ) (UTC -8) from comment #3)
:stransky- I see you had added a lot of the original Wayland variant logic, but we are not running any tests with this. I know :ahal is working on (or will be soon) a docker wayland image of ubuntu 22.04, so there are resources assigned now to get a formal platform setup for wayland.
Is there usage that you are aware of of the
waylandvariant? I am happy to keep it if this is being used, otherwise, cleaning up things makes for good code maintenance.
Hello Joel,
wayland variant is not used right now as we're waiting to the new images (ubuntu 22.04). It's no point run Wailand on recent 18.04 images as Wailand is broken there as it's pretty old environment.
So we generally want to run Wayland variants but we can't do that now due to old Ubuntu in Mozilla test suite. That's also block official Wayland support for Mozilla binaries.
| Assignee | ||
Comment 5•3 years ago
|
||
Given this- we are blocked on the new native wayland image in ubuntu 22.04. With that we would be looking to run this as a different platform instead of a variant (as it would be a different machine type/image).
I am proposing we remove the variant- right now in terms of priority we are looking to add Ubuntu 22.04 Wayland which will run a subset of tests, then after that is running live, create an ubuntu 22.04 X11 image to replace the existing 18.04 X11 image and tests.
| Assignee | ||
Comment 6•3 years ago
|
||
Updated•3 years ago
|
| Assignee | ||
Comment 7•3 years ago
|
||
:stransky- this is removing the variant from the configs; ideally in the next couple of months there will be a more modern ubuntu and ideally native Wayland available running tests.
Comment 9•3 years ago
|
||
| bugherder | ||
Updated•3 years ago
|
Description
•