Stop running Android crashtest-1 until someone's ready to fix it

RESOLVED FIXED

Status

RESOLVED FIXED
6 years ago
3 months ago

People

(Reporter: philor, Assigned: philor)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

6 years ago
Created attachment 621468 [details] [diff] [review]
commented out

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

6 years ago
Attachment #621468 - Flags: review?(bear) → review+
(Assignee)

Comment 1

6 years ago
Created attachment 621474 [details] [diff] [review]
both commented out

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

6 years ago
Attachment #621474 - Flags: review?(bear) → review+
in production now
(Assignee)

Updated

6 years ago
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.