Closed
Bug 899170
Opened 13 years ago
Closed 13 years ago
No unagi nightly build on m-c generated today
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: marcia, Unassigned)
Details
https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-central-unagi/2013/
We are missing the nightly build for today. This happened a few days ago, for reference Bug 896771.
| Reporter | ||
Comment 1•13 years ago
|
||
A request was made by tchung:
can they change the build kickoff times of 1.2 unagi master/M-C builds to closer to 7am PST? The current priority for testing would be 1.1 leos and 1.2 unagis.
| Reporter | ||
Comment 2•13 years ago
|
||
Bumping up priority as we need these builds on a daily basis for smoketesting.
Severity: normal → blocker
Comment 3•13 years ago
|
||
from irc:
1) Since the last 1.2 unagi build tested by QA (20130726030202), we have generated other newer 1.2 unagi builds. QA are able to proceed with testing that most-recent build, generated on Sunday (20130728030202).
2) Callek is now manually kicking 1.2 unagi nightlies.
3) Unclear why last night's 1.2 unagi nightly did not get generated, as several 1.2 unagi nightlies were generated just fine, as were other device builds last night. Investigating, will post findings here.
Comment 4•13 years ago
|
||
Manually triggered on m-c tip just now... Should show up on tbpl at
https://tbpl.mozilla.org/?jobname=unagi&rev=3d40d270c031
I'll leave this open for someone to diagnose why there was no nightly to begin with.
Comment 5•13 years ago
|
||
(In reply to Marcia Knous [:marcia] from comment #1)
> A request was made by tchung:
>
> can they change the build kickoff times of 1.2 unagi master/M-C builds to
> closer to 7am PST? The current priority for testing would be 1.1 leos and
> 1.2 unagis.
Spinning this out to separate bug#899407.
Comment 6•13 years ago
|
||
aside: also see bug#836131 for bug tracking automatic alerting if/when this happens again.
Comment 7•13 years ago
|
||
I don't think there's a bug here, just some info to pass on to QA.
The mozilla-b2g18, mozilla-b2g18_v1_0_1, and mozilla-b2g18_v1_1_0_hd branches always build two nightlies per 24 hours. Everything else builds if there have been code changes, and those compiled OK.
mozilla-central had landings during Saturday, so we got a nightly at 3am Sunday on
https://tbpl.mozilla.org/?jobname=nightly&rev=73b69c146ca6
The next landing was 7am Monday (rev 8c89fe2a5c92) so there was no nightly at 3am Monday. Also, recall that gaia changes for 1.2 are tracked on birch (soon to become b2g-inbound), which is then merged down to inbound and later central by the sheriffs.
Comment 8•13 years ago
|
||
Bumping down to major since this is kind of expected behaviour on m-c. Unfortunately for B2G builds there are other external repositories that could change even if there are no commits on m-c during the day. We solved this for mozilla-b2g18* by always doing nightly builds, regardless of if there are checkins.
As I see it, our options here are:
1) Keep the existing behaviour. If we can find a good place to document how scheduling builds works on the various branches, we should create those docs. My sense is that days without commits on m-c are pretty rare.
2) Always do nightly builds on m-c. If we can restrict this to just B2G builds it would be better.
3) Track external dependencies and take those into consideration when determining whether a nightly build should be done or not.
I prefer 1), since it's less work for me :), but also because I think it's pretty rare to have days without commits on m-c, and we can always trigger nightlies manually with self-serve if required.
Marcia, does that work for you? Were you aware that we don't do nightly builds on mozilla-central if there have been no gecko changes in the past 24 hours?
Severity: blocker → major
Flags: needinfo?(mozillamarcia.knous)
| Reporter | ||
Comment 9•13 years ago
|
||
(In reply to Chris AtLee [:catlee] from comment #8)
[snip]
>
> Marcia, does that work for you? Were you aware that we don't do nightly
> builds on mozilla-central if there have been no gecko changes in the past 24
> hours?
I wasn't aware that we only generate builds when there have been no changes. Docs would help here for sure.
Adding tchung for input. The smoketesters typically start at 9 AM Pacific so anything we could do to make sure there are builds at that time would be great.
Flags: needinfo?(mozillamarcia.knous)
| Reporter | ||
Comment 10•13 years ago
|
||
thcung clarified this in a hallway conversation - QA would like B2G mozilla central builds generated every day for both Gecko and Gaia, and have them delivered in time for the 9 AM Pacific smoketest. So it looks as if we want something closer to Option #2.
| Assignee | ||
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
| Reporter | ||
Comment 11•13 years ago
|
||
Closing this one out since I believe it is resolved.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
| Assignee | ||
Updated•8 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•