New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 662317 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

builds missing from M-55 Release branch

Project Member Reported by hyehia@chromium.org, Nov 4 2016

Issue description

8872.36.0 and 8872.37.0 were missing on 11-01 21:07 for all Google WiFi platforms (Whirlwind, Arkham and Gale)
	
this is affecting our ability to push a beta builds and prepare for stable sign-off.

Looks like on that day the build has been aborted for some reason. 

Below is the root cause:

Traditionally as Chrome OS was the only consumer of the release waterfall, this was not an issue, we only use one or two builds off of the R55 branch in a given week anyway and we had just pushed out a new R55. If we have other groups dependent on the release waterfall having the most recently cut running daily we may need to revisit the procedure.

With the improvements in lab stability this may no longer be a factor, and having two release branches running at the same time might be ok?

 
Not sure this is an (actionable) bug, as mentioned in the description this is a normal process to prevent saturation in the lab when two set of release builders at the same time like this. 

Note that this does not happen very often e.g. stopping beta builders to give precedence/priority to a critical Stable build and the beta being critical build as well 


Status: WontFix (was: Available)
sounds like working as intended, closing

Sign in to add a comment