Disable failing B2G emulator crashtests

RESOLVED FIXED in mozilla21

Status

defect
RESOLVED FIXED
7 years ago
6 years ago

People

(Reporter: ahal, Assigned: ahal)

Tracking

unspecified
mozilla21
ARM
Gonk (Firefox OS)
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(b2g18+ fixed)

Details

Attachments

(3 attachments)

Assignee

Description

7 years ago
We need to disable failing crashtests on various branches before enabling them on emulator arm builds there.
Attachment #705997 - Flags: review?(jgriffin)
Assignee

Comment 1

7 years ago
If we want to run crashtests on the b2g18 branch we'll need to land this there first. I'll let release drivers decide whether we want to enable more tests there or not.
tracking-b2g18: --- → ?
Comment on attachment 705997 [details] [diff] [review]
Patch 1.0 - disable crashtests

rubber stamp, applied!
Attachment #705997 - Flags: review?(jgriffin) → review+
Assignee

Updated

7 years ago
Blocks: 834390
https://hg.mozilla.org/mozilla-central/rev/382dae2711c9
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla21
Assignee

Comment 5

6 years ago
Dietrich, I'm a little confused how to proceed. This is a test-only change, but we were asked to refrain from checking them in by our partners as we may break their automation.

Does this mean that I now need to get tef+, leo+ or shira+? Or can I go ahead and land without them. FWIW this patch shouldn't affect anything our partners are doing as it's just some test disabling.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee

Updated

6 years ago
Flags: needinfo?(dietrich)
Assignee

Comment 6

6 years ago
I found https://etherpad.mozilla.org/B2G-Clarifications, looks like I can go ahead and land this on the b2g18 branch. I'm probably not going to worry about v1.0.0 and v1.0.1 unless people ask for it.
Flags: needinfo?(dietrich)
Assignee

Comment 7

6 years ago
https://hg.mozilla.org/releases/mozilla-b2g18/rev/54ae714b53d8
Status: REOPENED → RESOLVED
Closed: 7 years ago6 years ago
Resolution: --- → FIXED
Assignee

Updated

6 years ago
Blocks: 839225
Assignee

Comment 8

6 years ago
With the retrigger there were a bunch of additional failure on the b2g18 branch that weren't present on m-c. They are hidden on b2g18 for now but we need to disable some more tests.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee

Comment 9

6 years ago
This patch disables the failures that show up on tbpl. Because each chunk is timing out, I wouldn't be surprised if we need some follow-up patches to disable further failures.
Attachment #712984 - Flags: review?(jgriffin)
Attachment #712984 - Flags: review?(jgriffin) → review+
Assignee

Comment 10

6 years ago
https://hg.mozilla.org/releases/mozilla-b2g18/rev/b8d06a2cdca0

I'll wait to see if this greens up crashtests or another patch is needed before closing.
Assignee

Comment 11

6 years ago
Still a bunch of load failures (and even a hard timeout with no failures). I'll try running this locally to see if I can get it green there before pushing to b2g18 again.
Assignee

Comment 12

6 years ago
For some reason remote xul isn't working on b2g18, even though this line should be fixing it: http://mxr.mozilla.org/mozilla-b2g18/source/layout/tools/reftest/b2g_start_script.js#32

Since afaik we don't care about xul on b2g, I'd rather just disable those tests than fix the problem. This patch greens up crashtests for me locally.
Attachment #716138 - Flags: review?(jgriffin)
Comment on attachment 716138 [details] [diff] [review]
Patch 3.0 - disable all xul crashtests

Review of attachment 716138 [details] [diff] [review]:
-----------------------------------------------------------------

Seems like a good idea.
Attachment #716138 - Flags: review?(jgriffin) → review+
Assignee

Comment 15

6 years ago
Looking good!
Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.