Closed Bug 897141 Opened 6 years ago Closed 6 years ago

Schedule full emulator tests on b2g18

Categories

(Release Engineering :: General, defect)

defect
Not set

Tracking

(blocking-b2g:leo+, b2g18 fixed, b2g-v1.1hd fixed)

RESOLVED FIXED
blocking-b2g leo+
Tracking Status
b2g18 --- fixed
b2g-v1.1hd --- fixed

People

(Reporter: ahal, Assigned: aki)

References

Details

Attachments

(3 files)

There is a frequent intermittent crash on the b2g18 branch (bug 880285) as well as host of other intermittent problems. One theory is that the emulator snapshot keeps getting out of date. Seeing as b2g18 is going to be around for at least another 6 months, we should enable tests on the full stack builds and see how they run.

Because we don't have b2g18 try, we might need to hide them if there are many failures. If so we'll have to decide whether to attempt to fix or disable again and just live with the current setup awhile longer.
Attached patch emu-b2g18Splinter Review
I have the feeling you're going to tell me to refactor mozilla-tests/b2g_config.py (given bug 880273), but taking a shot anyway.

* splitting linux64_gecko away from the emulator/ics_armv7a_gecko loop for simplicity.
* removing 'emulator' from all non-mc branches except b2g18
* removing ics_armv7a_gecko from all mc branches (keeping it on b2g18)

It's ugly.  I don't like the loops, and it looks like they're not going to go away anytime soon.

I imagine the long term fix involves bug 817046.
Attachment #780131 - Flags: review?(armenzg)
Attached patch builder.diffSplinter Review
This is the diff in the builder list.
Comment on attachment 780131 [details] [diff] [review]
emu-b2g18

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

This is something that is already hacky and not clearly going to be riding the trains as with the other bugs.

lgtm.
Attachment #780131 - Flags: review?(armenzg) → review+
Assignee: nobody → aki
In production
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
I retriggered a full-stack build after the reconfig, but I don't see any tests starting.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #6)
> I retriggered a full-stack build after the reconfig, but I don't see any
> tests starting.

Still no sign of these tests...
It's not sendchanging because we're not building the tests zip.
Gotta figure out how to enable those...
This adds the package-tests and upload changes from mozilla-central emulator config.json, and updates the l10n/manifest settings to match the mozilla-b2g18 unagi config.json.
Attachment #785921 - Flags: review?(rail)
Attachment #785921 - Flags: review?(rail) → review+
This needs to land on b2g18 to get the emulator tests running.
blocking-b2g: --- → leo?
leo+
blocking-b2g: leo? → leo+
Ok, scheduled.  https://tbpl.mozilla.org/?tree=Mozilla-B2g18
They probably need some tlc; they're like autumn.
Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
Fwiw we only run reftest-sanity on b2g18, so the failures (most likely) don't have anything to do with the fact that it's a full stack build.

Crashtests are what we are most interested in given that that's where the intermittent failure is most common. There seems to be one perma-orange there, but otherwise they seem stable.
Blocks: 902649
Looking good, thanks! We should be doing this on the v1.1hd branch as well, but I will file a new bug for that.
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.