All users were logged out of Bugzilla on October 13th, 2018

Update base build to KK, start doing full flash, create a 2.1 branch for eideticker/flame

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
4 years ago
a year ago

People

(Reporter: wlach, Unassigned)

Tracking

Trunk
x86_64
Linux

Details

Since 2.1 is being branched, we should run eideticker against builds from there, in addition to b2g-inbound and 2.0.
It looks like we actually should do three things to get eideticker up to date, which we may as well track here:

1. Switch the base build to kitkat
2. Start doing full flashes as opposed to partial ones
3. Create a 2.1 branch for testing (original bug)

Dave Hunt is going to do at least (1) and (2) when he's in London next Tuesday
Assignee: nobody → dave.hunt
Summary: Create a 2.1 branch for eideticker/flame → Update base build to KK, start doing full flash, create a 2.1 branch for eideticker/flame
I've flashed the two devices with Flame KK base builds (v180), updated the download jobs to grab the KK builds, and changed the test jobs to perform a full flash. We have failures most likely related to bug 1021068 but once I can confirm everything looks good I'll update eideticker-ci with the changes.
Landed download of KK builds:
https://github.com/mozilla/eideticker-ci/commit/f4cd3c34f6f763a5d388b6c6113a2f608ff2331c

Landed full flash of builds:
https://github.com/mozilla/eideticker-ci/commit/f198bad447ce2c186f12cf46f463cc849c5ce2ef

Once the currently running jobs have completed I will temporarily shutdown Jenkins to pull in the latest changes from the remote repository. Setting needinfo as a reminder.
Status: NEW → ASSIGNED
Flags: needinfo?(dave.hunt)
Jenkins has been updated with the changes mentioned in comment 3.
Assignee: dave.hunt → nobody
Status: ASSIGNED → NEW
Flags: needinfo?(dave.hunt)

Comment 5

a year ago
Eideticker has been discontinued, see bug 1361056
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX

Updated

a year ago
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.