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)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Assigned: philor)

References

Details

Attachments

(1 file, 1 obsolete file)

Attached patch commented out (obsolete) — 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)
Attachment #621468 - Flags: review?(bear) → review+
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)
Attachment #621474 - Flags: review?(bear) → review+
in production now
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: