Open Bug 1607581 Opened 5 years ago Updated 2 years ago

Failure while running some extension tests

Categories

(Testing :: Code Coverage, defect, P3)

defect

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

The priority flag is not set for this bug.
:ekyle, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(klahnakoski)

: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?

Flags: needinfo?(klahnakoski) → needinfo?(sledru)

You are talking about the bot, it isn't ML based. It just uses the triage owner for this :)

Flags: needinfo?(sledru)

:sylvestre Who (or what) is creating these bugs in the codecoverage component?

Flags: needinfo?(sledru)

Kyle, not sure what you mean :)
Here, it was a human called Marco doing it!

Flags: needinfo?(sledru)
Version: Version 3 → Trunk

The priority flag is not set for this bug.
:ekyle, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(klahnakoski)
Flags: needinfo?(klahnakoski)
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.