Closed Bug 1082112 Opened 7 years ago Closed 4 years ago
Convince mozharness to treat seccomp sandbox failures as test failures on non-B2G
If a test run contains a sandboxing failure, it should not be considered successful, even if this doesn't result in any TEST-UNEXPECTED-FAILs somehow. See also bug 1081251 (a test that passes despite causing a child process crash), and bug 1081242 (where sandbox failures may need to be made non-fatal on ASAN builds). This isn't so important if the crash reporter is present (and works as expected), but it's disabled on ASAN builds. Also, it would be nice to highlight that line as an error. Bug 945330 accomplishes this on B2G, but it's part of a special case for Android logcat, so it doesn't work for desktop.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
For the historical record: we no longer use sandboxing on ASan builds, due to conflicts with LSan (bug 1287971), so these failures should always be caught in testing via the crash reporter now (and if we somehow also break crash reporting, hopefully its tests will catch that). If in the future we have some kind of sandboxed ASan… maybe we can integrate with the ASan Nightly alternative crash reporter, or maybe we can just write a fake TEST-UNEXPECTED-FAIL to stderr.
You need to log in before you can comment on or make changes to this bug.