Closed Bug 1284083 Opened 5 years ago Closed 4 years ago
_pref _maxpages .js | test _pref _maxpages - [test _pref _maxpages : 115] 0 == 1
59 bytes, text/x-review-board-request
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/9c7bde46a67a Disable frequent intermittent toolkit/components/places/tests/expiration/test_pref_maxpages.js. r=test-disabled as suggested by mak on IRC
Assignee: nobody → mak77
Status: NEW → ASSIGNED
Priority: P3 → P2
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/25fc050d41d8 Disable frequent intermittent toolkit/components/places/tests/expiration/test_pref_maxpages.js completely on Linux. r=test-disabled on a CLOSED TREE
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I'll do some Try runs to ensure everything is fine.
ok, the fix works for test_pref_maxpages.js but it seems to cause a different intermittent in test_clearHistory.js, probably because that test is wrongly not using the PlacesTestUtils.clearHistory util (that properly waits for expiration to be finished)
The latest version of the patch looks good on Try!
Comment on attachment 8861945 [details] Bug 1284083 - Fix a race condition in nsPlacesExpiration that may cause intermittent failures. https://reviewboard.mozilla.org/r/133948/#review137488
Attachment #8861945 - Flags: review?(adw) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/c8fbd538c1ee Fix a race condition in nsPlacesExpiration that may cause intermittent failures. r=adw
Status: REOPENED → RESOLVED
Closed: 4 years ago → 4 years ago
Resolution: --- → FIXED
This is happening pretty frequently on Beta as well. Is it safe to uplift?
I'd prefer the test to be disabled in beta, while it's not very unsafe, I'd still like this to ride the train.
You need to log in before you can comment on or make changes to this bug.