Closed Bug 1413161 Opened 2 years ago Closed Last month

Permaorange test-verify browser/base/content/test/general/browser_e10s_about_page_triggeringprincipal.js | Test timed out -

Categories

(Testing :: General, defect, P5)

Version 3
defect

Tracking

(Not tracked)

RESOLVED INACTIVE

People

(Reporter: intermittent-bug-filer, Assigned: gbrown)

References

Details

(Keywords: intermittent-failure)

Duplicate of this bug: 1413174
Test verification was triggered by the change in bug 1412778, but that change certainly did not cause the failure -- it was a pre-existing condition.

I see no other bugs open for this test, so there's possibly nothing to worry about here.

These failures happened during step 1 of test verification, where the test is repeated multiple times in one browser session. Failures of this type often indicate that the test fails to restore state at the end of the test, or that the test relies on state set up by a previous test.

In this case, running locally on Ubuntu, I consistently see test passes when I run the whole directory of tests, but fail consistently when I run just this test:

  mach mochitest browser/base/content/test/general/browser_e10s_about_page_triggeringprincipal.js
Blocks: 1406204

This test is now skipped on verify runs, so it won't cause further trouble.

Assignee: nobody → gbrown
Status: NEW → RESOLVED
Closed: Last month
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.