Closed
Bug 1319782
Opened 8 years ago
Closed 7 years ago
Move Linux64 mochitest-plain to Ubuntu 16.04
Categories
(Testing :: General, defect)
Testing
General
Tracking
(firefox56 fixed)
RESOLVED
FIXED
mozilla56
Tracking | Status | |
---|---|---|
firefox56 | --- | fixed |
People
(Reporter: RyanVM, Assigned: sparky)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
Unfortunately, it's not entirely green at the moment.
Permafail across all flavors:
https://treeherder.mozilla.org/logviewer.html#?job_id=31673215&repo=try
https://treeherder.mozilla.org/logviewer.html#?job_id=31673187&repo=try
https://treeherder.mozilla.org/logviewer.html#?job_id=31673258&repo=try
Also makes bug 1210289 permafail on e10s:
https://treeherder.mozilla.org/logviewer.html#?job_id=31673228&repo=try
And LSAN issues like mochitest-media hit (in various directories):
https://treeherder.mozilla.org/logviewer.html#?job_id=31672322&repo=try
https://treeherder.mozilla.org/logviewer.html#?job_id=31672342&repo=try
https://treeherder.mozilla.org/logviewer.html#?job_id=31672273&repo=try
https://treeherder.mozilla.org/logviewer.html#?job_id=31672365&repo=try
Comment 1•8 years ago
|
||
once the existing bugs are cleaned up, I will revisit this, right now I suspect resolving INPUT vs DIV will make a difference in more tests than what I have specifically filed for
Comment 2•8 years ago
|
||
Comment 3•8 years ago
|
||
Adds on the try run in previous comment with rebuild
https://treeherder.mozilla.org/#/jobs?repo=try&revision=0e58a7a54798912a2ba18d4cd9dcc3a0dfebb9e5
Comment 4•8 years ago
|
||
:greg, can you push to try to see if mochitest-plain will work just fine? include android and all linux platforms as well, ideally --rebuild 5
Updated•8 years ago
|
Flags: needinfo?(gmierz2)
Assignee | ||
Comment 5•8 years ago
|
||
Sounds good, here's the try push: https://treeherder.mozilla.org/#/jobs?repo=try&revision=8d191df67e0a14bbde01312a28d827587fa9e8fb
Flags: needinfo?(gmierz2)
Assignee | ||
Comment 6•7 years ago
|
||
Here's the latest try run with mochitest-plain on ubuntu 16.04: https://treeherder.mozilla.org/#/jobs?repo=try&revision=92024ebe593eb53f6e2680fef29b28c465900a89&filter-tier=1&filter-tier=2&filter-tier=3
It's getting better now. Also, even though bug 1357082 is reopened, it's only popped up on windows so far. And there must've been some change that came and helped out the test_ext_webrequest_basic.html error because it's become quite rare, maybe we could skip it or just leave it alone?
There are some other problems that popped up on plain test chunks but none of them are new and are already known so I've retriggered them about 30-40 times to see if the frequency has changed.
Comment 7•7 years ago
|
||
looking at that try run linux32-debug mochitest-e10s-6 is concerning, but it is just timing out; hard to know if that is something expected on non try branches, or if this is related to the 16.04 image; either way, we can figure this out after the move.
:gmierz, please upload a patch and lets migrate!
Flags: needinfo?(gmierz2)
Comment hidden (mozreview-request) |
Comment 9•7 years ago
|
||
mozreview-review |
Comment on attachment 8876843 [details]
Bug 1319782 - Move mochitest plain to Ubuntu 16.04.
https://reviewboard.mozilla.org/r/148178/#review152522
Attachment #8876843 -
Flags: review?(jmaher) → review+
Comment 10•7 years ago
|
||
Pushed by jmaher@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/0932844da783
Move mochitest plain to Ubuntu 16.04. r=jmaher
Assignee | ||
Comment 11•7 years ago
|
||
Great! And yes I agree, chunk 6 is odd, but I've looked at the latest failure frequency here: https://bugzilla.mozilla.org/show_bug.cgi?id=1204281#c359
And it doesn't seem like it increased by any significant amount but I guess only time will tell now.
Flags: needinfo?(gmierz2)
Reporter | ||
Comment 12•7 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox56:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla56
Updated•6 years ago
|
Assignee: nobody → gmierz2
Updated•3 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•