Closed
Bug 752373
Opened 12 years ago
Closed 12 years ago
Stop running Android crashtest-1 until someone's ready to fix it
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Assigned: philor)
References
Details
Attachments
(1 file, 1 obsolete file)
1.72 KB,
patch
|
bear
:
review+
philor
:
checked-in+
|
Details | Diff | Splinter Review |
In February, I hid Android crashtest-1 in bug 663657 because it constantly timed out, I split crashtests into 3 chunks in bug 721409, then I eventually gave up and rehid it in bug 728119. It still times out constantly - over the last 20 pushes on inbound, it has managed 8 green runs out of 36, which is pretty good for it, since if you look at the busy part of Friday afternoon, it's more like 0% success. When someone hypothetically wants to fix it, it'll be easy enough for them to revert this patch, and in the meantime, we can find much better uses for 2 hours plus of Tegra time per push.
Attachment #621468 -
Flags: review?(bear)
Updated•12 years ago
|
Attachment #621468 -
Flags: review?(bear) → review+
Assignee | ||
Comment 1•12 years ago
|
||
Gah, I started out looking at the patch where I added c3 to both XUL and native, and I *still* forgot to comment out c1 for both.
Attachment #621468 -
Attachment is obsolete: true
Attachment #621474 -
Flags: review?(bear)
Updated•12 years ago
|
Attachment #621474 -
Flags: review?(bear) → review+
Assignee | ||
Comment 2•12 years ago
|
||
Comment on attachment 621474 [details] [diff] [review] both commented out http://hg.mozilla.org/build/buildbot-configs/rev/9310ac098d1f
Attachment #621474 -
Flags: checked-in+
Comment 3•12 years ago
|
||
in production now
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•