Closed Bug 1300010 Opened 8 years ago Closed 6 years ago

Intermittent toolkit/components/reader/test/browser_readerMode.js | Timed out while polling clipboard for pasted data -

Categories

(Toolkit :: Reader Mode, defect, P4)

Product:
Toolkit
Component:
Reader Mode
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure)

Summary: Intermittent browser/base/content/test/general/browser_readerMode.js | Timed out while polling clipboard for pasted data - → Intermittent toolkit/components/reader/test/browser_readerMode.js | Timed out while polling clipboard for pasted data -
Should this be running in mochitest-clipboard?
Flags: needinfo?(jmaher)
this should have been, iirc there was an issue when we moved this out of bc;
here is a fresh push:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=fd2e1bca0a69b070baea9f0cfe807656b84c9ae3

why are we getting mostly perma fail on:
browser/components/search/test/browser_yahoo_behavior.js

and:
browser/base/content/test/static/browser_all_files_referenced.js

in almost every case these are in a different chunk than the readerMode tests...I do wonder if this is related to moving the test dirs around (didn't we just solve this problem with crash dumps)?

here is the base revision the try push is from:
https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=2a67191bf3fbd6ed150a27bc09fb948a252c538e&filter-searchStr=browser-chrome

this is odd because in win7-opt the readermode tests are in bc1 (non-e10s) and the above 2 failures are not in there- possibly there is more shuffling that takes place?

As it stands, I would love to move this test to clipboard, possibly there is some more work we could do?
Flags: needinfo?(jmaher)
Priority: -- → P4
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.