1790085 - Running a single xpcshell-test locally which has failures causes it to be run twice.

Status: RESOLVED FIXED

(Testing :: XPCShell Harness, defect, P2)

Description

[Mark Banner (:standard8)]

If I change an xpcshell-test to make it fail, and then run it as a single test, it will run twice.

e.g. using this command:

./mach xpcshell-test toolkit/components/search/tests/xpcshell/test_engine_selector.js

Runs the test twice when it fails.

This has two issues. Firstly, you get a duplicated test failures summary, and duplicated logs. I find the test failures summary especially confusing, because "why is my test code being run twice?".

Secondly, when running with --jsdebugger you do your debugging, and let the debugger exit. At which point the test restarts (puzzled: "why did it do that?"), and you manually have to ctrl-c it to stop it.

Maybe we could alter the change that bug 1781782 to make it so that it only re-runs single tests on automation?

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1781782

:jmaher, since you are the author of the regressor, bug 1781782, could you take a look? Also, could you set the severity field?

For more information, please visit auto_nag documentation.

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

I think that is reasonable- thanks for filing this bug

Comment 3

[Joel Maher ( :jmaher ) (UTC -8)]

Attachment: Bug 1790085 - retry xpcshell tests only in CI, not locally. r=gbrown!

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/132b92a60892
retry xpcshell tests only in CI, not locally. r=gbrown

Comment 5

[Cristina Cozmuta (:CrissCozmuta)]

https://hg.mozilla.org/mozilla-central/rev/132b92a60892

Comment 6

[Mark Banner (:standard8)]

Thank you.