Closed Bug 1093756 Opened 11 years ago Closed 10 years ago

re-enable several tests for e10s

Categories

(Firefox :: General, defect)

defect
Not set
normal
Points:
2

Tracking

()

RESOLVED FIXED
Firefox 42
Tracking Status
e10s + ---
firefox42 --- fixed

People

(Reporter: Gijs, Assigned: tracy)

References

(Blocks 1 open bug)

Details

Attachments

(1 file, 3 obsolete files)

2 INFO TEST-START | chrome://mochitests/content/browser/browser/base/content/test/general/browser_bug581253.js 3 INFO Console message: [JavaScript Error: "The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature." {file: "data:text/plain,nothing%20but%20plain%20text" line: 0}] 4 INFO TEST-PASS | chrome://mochitests/content/browser/browser/base/content/test/general/browser_bug581253.js | the test url is bookmarked 5 INFO Waiting for star button change. 6 INFO Waiting for star button change. 7 INFO Waiting for star button change. 8 INFO Waiting for star button change. 9 INFO Waiting for star button change. 10 INFO Waiting for star button change. (... continues indefinitely until timeout ...) Interestingly, even manually clicking the star button (a) doesn't seem to successfully bookmark the page, and (b) doesn't stop the spam
Flags: qe-verify-
Flags: in-testsuite+
Flags: firefox-backlog+
I just ran browser_bug581253.js in e10s and it passes. Can we morph this bug to re-enable the test case?
Flags: needinfo?(jmathies)
(In reply to [:tracy] Tracy Walker - QA Mentor from comment #1) > I just ran browser_bug581253.js in e10s and it passes. > > Can we morph this bug to re-enable the test case? Seems like the right thing to do.
Flags: needinfo?(jmathies)
Assignee: nobody → twalker
so this would just be removing the skip-if line in browser.ini, right? Jim, let's walk through that tomorrow and see if I can check-in the patch. I have a feeling I didn't do all the hoop jumping a few years back to maintain my check-in rights. Surely there is a way check if I do or not?
Summary: e10s - fix browser_bug581253.js to work in e10s → re-enable browser_bug581253.js for e10s
How about the other tests you found? Lets morph this bug into a more general one and add those too so we can land this all at once.
Ok, I'll get that list together, try a new patch locally. Once I've nailed down which test cases can be re-enabled, I'll push a new patch to try and morph this bug accordingly.
Attached patch re-enable tests (obsolete) — Splinter Review
Attachment #8627845 - Flags: review?(jmathies)
Try runs look good: https://treeherder.mozilla.org/#/jobs?repo=try&revision=a5572d8b1922 This attached patch will re-enable the following tests for e10s: browser_bug623155.js browser_bug678392.js browser_bug880101.js, browser_favicon_change_not_in_document.js browser_identity_UI.js browser_keywordSearch.js browser_parsable_css.js browser_searchSuggestionUI.js browser_syncui.js browser_tabfocus.js browser_visibleTabs_tabPreview.js
Summary: re-enable browser_bug581253.js for e10s → re-enable several tests for e10s
Attachment #8627845 - Flags: review?(jmathies) → review+
How would you like to land this? On your own or through tree drivers/checkin-needed?
Attachment #8627845 - Attachment is obsolete: true
Attachment #8627920 - Flags: review?(jmathies)
Comment on attachment 8627920 [details] [diff] [review] Patch with correct header information for checkin Your summary info isn't complete - "Bug 1093756: Re-enable several test cases under e10s" should be something like: "Bug 1093756: Re-enable several test cases under e10s. r=jimm" Once that's updated, you can carry forward my r+ and add checkin-needed to the bug.
Attachment #8627920 - Flags: review?(jmathies) → review+
Also add more detail - "Re-enable several browser chrome tests under e10s. r=jimm"
Attachment #8627920 - Attachment is obsolete: true
Attachment #8627944 - Flags: review+
Keywords: checkin-needed
(In reply to [:tracy] Tracy Walker - QA Mentor from comment #13) > Created attachment 8627944 [details] [diff] [review] > More detailed summary for checkin patch no problem Tracy, landed this as https://hg.mozilla.org/integration/fx-team/rev/0024c5cfa25b \o/
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
sorry had to back this out from mozilla-central and integration trees for perma failures on OS X like https://treeherder.mozilla.org/logviewer.html#?job_id=11418476&repo=mozilla-inbound
Status: RESOLVED → REOPENED
Flags: needinfo?(twalker)
Resolution: FIXED → ---
There was only one testcase enabled here that was causing perma failures on Mac 10.10. The new patch disables the test case for Mac. New try run for Mac 10.10 is green (sorry didn't run it prior to previous patch, I didn't know 10.10 has to be manual selected in the try code generator). https://treeherder.mozilla.org/#/jobs?repo=try&revision=c7c985f142e1
Attachment #8627944 - Attachment is obsolete: true
Flags: needinfo?(twalker)
Attachment #8631571 - Flags: review?(jmathies)
Attachment #8631571 - Flags: review?(jmathies) → review+
Keywords: checkin-needed
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 42
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: