Closed
Bug 839225
Opened 12 years ago
Closed 12 years ago
Schedule mozharness b2g crashtests on b2g18
Categories
(Release Engineering :: Applications: MozharnessCore, defect)
Release Engineering
Applications: MozharnessCore
ARM
Gonk (Firefox OS)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ahal, Assigned: ahal)
References
Details
(Whiteboard: [mozharness])
Attachments
(1 file)
|
1.83 KB,
patch
|
mozilla
:
review+
|
Details | Diff | Splinter Review |
Bug 834382 got approval-b2g18+'ed which means we should turn on B2G crashtests on the b2g18 branch also (note they should not be turned on either the mozilla-b2g18v1.0.0 or mozilla-b2g18v1.0.1 branches yet).
|
Assignee | |
Comment 1•12 years ago
|
||
Attachment #711478 -
Flags: review?(aki)
|
||
Comment 2•12 years ago
|
||
Comment on attachment 711478 [details] [diff] [review]
Patch 1.0 - enable crashtests on b2g18
Lgtm, though we may default to all unittests without this line.
Attachment #711478 -
Flags: review?(aki) → review+
|
|
Assignee | |
Comment 3•12 years ago
|
||
http://hg.mozilla.org/build/buildbot-configs/rev/b30ca10e185e
I ended up just leaving it as is since there were other lines that also explicitly defined ALL_UNITTESTS[:].. Might also make it easier to see what's going on.
|
||
Comment 4•12 years ago
|
||
In production
|
||
Comment 5•12 years ago
|
||
These all turned red (due to failed tests followed by a hard timeout) so I've hidden them until ahal can look at them.
|
||
Updated•12 years ago
|
Whiteboard: [mozharness]
|
|
Assignee | |
Comment 6•12 years ago
|
||
This bug can be closed since they're running. I'll make a new bug if we decide to disable them again.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
|
||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
|
||
Updated•11 years ago
|
Component: General Automation → Mozharness
You need to log in
before you can comment on or make changes to this bug.
Description
•