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

Status: RESOLVED INACTIVE

(Testing :: General, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: ebalazs [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=140892190&repo=mozilla-central

https://queue.taskcluster.net/v1/task/MJjrrnBpRKmOmKQ-kqn8GA/runs/0/artifacts/public/logs/live_backing.log

Comment 2

[Geoff Brown [:gbrown]]

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

Comment 3

[Intermittent Failures Robot]

8 failures in 857 pushes (0.009 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-inbound: 7
* mozilla-central: 1

Platform breakdown:
* windows7-32: 3
* windows10-64: 3
* osx-10-10: 1
* android-api-16-gradle: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1413161&startday=2017-10-30&endday=2017-11-05&tree=all

Comment 4

[Geoff Brown [:gbrown]]

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