837517 - possible rebuild of gonk snapshot after backout?

Status: RESOLVED WORKSFORME

(Release Engineering :: General, defect)

Description

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Spinning out of bug#837175

>
> Releng, if your snapshots contain the
> cdc0b4456aef26c5e0e26c1f0766db25671d8947 changest, please regenerate them
> once I've landed the backout.
>
...which landed <30mins later.

Depending on timing of when we built our last snapshot, we may/maynot need to rebuild this. Filing to track investigate, and rebuild if needed.

Comment 1

[Justin Wood (:Callek)]

FYI: We have a current snapshot request open (pending fix of another bug)  in Bug 837019, the dependant bug for that is Bug 836105.

We also have a bug on file for forking the gonk snapshots based on train, Bug 836627

Most recent snapshot happened in Bug 833096, landed on 2013-01-22 09:49:45 EST  (Code changes listed in bug)

The backout happens to be the tipmost sha1 in https://github.com/mozilla-b2g/gonk-misc/compare/22629c7597d0d658fb472f76f2bf35e7eaaf98fd...2f8c7d3546bda16b02a61b422786919875c19f15

So based on armen's docs for the snapshot he did looks like our current snapshot does indeed have the backout.

RESO/WFM based on that, but thanks for filing new so we were sure to check