Reenable browser_sandbox_test.js on Linux 22.04 when browser.nova.enabled is true
Categories
(Core :: Security: Process Sandboxing, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox155 | --- | fixed |
People
(Reporter: aryx, Assigned: jld)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Skip rule added: "os == 'linux' && os_version == '22.04' && arch == 'x86_64' && debug && nova",
| Reporter | ||
Comment 1•8 days ago
|
||
This bug reportedly affects only Linux 22.04. The test does not run with this environment in production by default and the failure might be an issue with the Wayland graphical display system on Linux. Feel free to remove the bug from blocking nova tests and to re-enable test. (This is message is an update to several bugs.)
Comment 2•3 days ago
|
||
It feels highly unlikely that a front-end change like Nova could cause any problem with that test. And I miss any ancillary information about how this test is failing in this bug and Jed was not able to reproduce any failure.
Can we just re-enable it and see what happens? The bulk disabling happened in bug 2057902 but also there I cannot find any details about the why.
| Assignee | ||
Comment 3•2 days ago
|
||
Nova is a Firefox frontend revamp, and browser_sandbox_test is a suite
of lower-level sandbox policy tests written in C++, so any failures were
likely coincidental, and we should reenable the test and investigate any
new failures that result.
Updated•2 days ago
|
| Assignee | ||
Comment 4•2 days ago
|
||
(In reply to Jens Stutte [:jstutte] from comment #2)
Can we just re-enable it and see what happens?
As one of the sandboxing module owners: Yes, we can.
Comment 6•1 day ago
|
||
| bugherder | ||
Description
•