Disable some a11y diagnostic asserts in IPC fuzzing
Categories
(Core :: Disability Access APIs, enhancement)
Tracking
()
People
(Reporter: decoder, Assigned: decoder)
Details
(Keywords: sec-other, Whiteboard: [adv-main105-])
Attachments
(1 file)
The a11y code has some diagnostic asserts that the IPC fuzzer trips very frequently. We should disable these asserts only when we are doing IPC fuzzing (through the FUZZING_SNAPSHOT
ifdef).
(Marked s-s until we unhide all the other IPC fuzzing bugs).
Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Comment 2•2 years ago
|
||
Is there any bug open for those two asserts failing? Seems like the right path would be to actually fix those issues. Are there many more of these kinds of asserts that get tripped that would make that task untenable?
Assignee | ||
Comment 3•2 years ago
|
||
(In reply to Eitan Isaacson [:eeejay] from comment #2)
Is there any bug open for those two asserts failing? Seems like the right path would be to actually fix those issues. Are there many more of these kinds of asserts that get tripped that would make that task untenable?
From what I can tell, there is no actual issue. The asserts are simply not correct in the setting of IPC fuzzing. We are directly sending (wrong) data to parent actors, so the failures are expected (at least from what I can tell, looking at the code).
Comment 4•2 years ago
|
||
Disable some diagnostic asserts in a11y for IPC fuzzing. r=eeejay
https://hg.mozilla.org/integration/autoland/rev/c90f430279dfc9fcc3987a6d91f958fd8ed31221
https://hg.mozilla.org/mozilla-central/rev/c90f430279df
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•1 year ago
|
Description
•