Canary release numbers incrementing unexpectedly. |
||||||
Issue descriptionThe release versions for ChromeOS should increment once per canary build. However, they are somehow being incremented faster than that. The canary master (which should control these uprevs) has been green for the last few builds. https://uberchromegw.corp.google.com/i/chromeos/builders/master-release But it lists the versions built as: 8013.0.0 8016.0.0 8017.0.0 8019.0.0 8022.0.0 8023.0.0 8025.0.0 8028.0.0 8029.0.0
,
Mar 7 2016
,
Mar 7 2016
I just checked that the master-toolchain-release did build the versions that the canary master should have built. Any fix for this?
,
Mar 7 2016
E.g. it builds the 8027.0.0 https://uberchromegw.corp.google.com/i/chromeos/builders/master-toolchain-release/builds/36
,
Mar 7 2016
Hum. It might be as simple as making sure that builder doesn't set the official flag (if it does). Otherwise, we need to figure out a plan for deciding when/if to uprev release versions.
,
Mar 7 2016
Aviv, are you the right person to pick up this?
,
Mar 7 2016
In Chat, sosa@ also expressed some interest.
,
Mar 7 2016
Who is responsible for the new master? What changed?
,
Mar 7 2016
I believe something changed with: https://bugs.chromium.org/p/chromium/issues/detail?id=577273
,
Mar 7 2016
would there be some flags in the chromeos_config.py to disable using the official release number?
,
Nov 15 2016
Don, I believe you tracked this down to something related to toolchain master, and fixed it a while ago?
,
Nov 15 2016
Any builder using ManifestVersionSync will potentially increment the version. I think it was controlled by chromeos_config.py having the "official" flag set, debug not set, and being a build master (not slave), or a slave that wasn't triggered by a master.
,
Nov 18 2016
Looking in Golden Eye, I think this is now fixed. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by davidri...@chromium.org
, Mar 7 2016