Closed
Bug 1525738
Opened 10 months ago
Closed 10 months ago
Stop running Android 7.0 x86_64 geckoview-junit until it stops hanging
Categories
(Testing :: General, enhancement, P2)
P2
Tracking
(firefox67 fixed)
RESOLVED
FIXED
mozilla67
Tracking | Status | |
---|---|---|
firefox67 | --- | fixed |
People
(Reporter: gbrown, Assigned: gbrown)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
581 bytes,
patch
|
mbrubeck
:
review+
snorp
:
feedback+
|
Details | Diff | Splinter Review |
Android 7.0 x86_64 geckoview-junit tests are perma-fail and have been for many weeks. We run these as tier 3, so failures don't bother anyone, but I suspect no one is using the test results either. Can we turn them off, or run them less often, to save some packet.net time/money?
![]() |
Assignee | |
Comment 1•10 months ago
|
||
A review of recent treeherder data suggests this task runs about 128 times (84 hours) per day, broken down as:
mozilla-central 4 runs / 2.8 hours
mozilla-inbound 22 runs / 14.9 hours
autoland 90 runs / 56.7 hours
try 12 runs / 10.6 hours
![]() |
Assignee | |
Comment 2•10 months ago
|
||
OK with you to stop running Android 7.0 x86_64 geckoview-junit, until it is in better shape?
Attachment #9042507 -
Flags: review?(mbrubeck)
Attachment #9042507 -
Flags: feedback?(snorp)
Comment 3•10 months ago
|
||
Yeah, that's fine as long as we're still running on x86.
Updated•10 months ago
|
Attachment #9042507 -
Flags: feedback?(snorp) → feedback+
Updated•10 months ago
|
Attachment #9042507 -
Flags: review?(mbrubeck) → review+
Pushed by gbrown@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/a90e2dd8b1a5 Stop running Android 7.0 x86_64 geckoview-junit tests; r=mbrubeck
Comment 5•10 months ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 10 months ago
status-firefox67:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
![]() |
||
Comment 6•10 months ago
|
||
bugherder |
Updated•10 months ago
|
Blocks: geckoview-junit-x86_64
You need to log in
before you can comment on or make changes to this bug.
Description
•