Failure while running some extension tests
Categories
(Testing :: Code Coverage, defect, P3)
Tracking
(Not tracked)
People
(Reporter: marco, Unassigned)
References
Details
The following xpcshell tests are failing:
- xpcshell-remote.ini:toolkit/components/extensions/test/xpcshell/test_ext_proxy_speculative.js
- xpcshell-remote.ini:toolkit/components/extensions/test/xpcshell/test_ext_proxy_startup.js
- xpcshell-remote.ini:toolkit/components/extensions/test/xpcshell/test_ext_runtime_id.js
- xpcshell-remote.ini:toolkit/components/extensions/test/xpcshell/test_ext_shadowdom.js
Comment 1•5 years ago
|
||
The priority flag is not set for this bug.
:ekyle, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 2•5 years ago
|
||
:sylvestre I am guessing that the "code coverage" aspect of these tasks is being used by the ML to send me these crashes. How should I deal with them? How do I inform the ML it got it wrong? Is there a default product/component to return these items?
Comment 3•5 years ago
|
||
You are talking about the bot, it isn't ML based. It just uses the triage owner for this :)
Comment 4•5 years ago
|
||
:sylvestre Who (or what) is creating these bugs in the codecoverage component?
Comment 5•5 years ago
|
||
Kyle, not sure what you mean :)
Here, it was a human called Marco doing it!
Comment 6•5 years ago
|
||
The priority flag is not set for this bug.
:ekyle, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•5 years ago
|
Updated•2 years ago
|
Description
•