Is chrome-bot up? |
||
Issue descriptionI noticed that a change was made to chromeos-base/chromeos-chrome/chromeos-chrome-9999.ebuild, but an uprev on the stable ebuild didn't happen. https://chromium.git.corp.google.com/chromiumos/overlays/chromiumos-overlay/+/0c7feb1bd24e1fab33676c204a0cc49674fab04c
,
Apr 11 2017
This is a question for the Infra team. I've spoken with dgarrett@, and he says that this is normal behavior. The chromeos-chrome ebuild will uprev when the Chrome PFQ uprevs Chrome.
,
Apr 11 2017
Thanks. Don, when does the PFQ normally uprev Chrome? In this case where was no new Chrome version to build, but we'd like to pick the change to the chrome 9999 ebuild. Should we do something like https://chromium-review.googlesource.com/c/469228/ to manually uprev it?
,
Apr 11 2017
That ebuild is very much a special case. I think it uprevs every time the PFQ is successful. However, it's been broken for several days. It looks closer to fixed, but not yet fixed (mix of Chrome and ChromeOS bugs, apparently). PFQ builds do include the 9999 changes while they test for uprev. Manual uprevs are possible, but should only be done if the gardener thinks it's safe, and only with the command line tool which does a lot of sanity checking of the special requirements for prebuilts related to that ebuild.
,
Apr 11 2017
Don, is there a bug tracking the fix? If I want to do the manual uprev, would alemate@ be the right person to ask for approval? Any instructions on the command line tool?
,
Apr 11 2017
I don't know the current state, or what the bugs might be. The current gardener should, and they should do the uprev, if it's needed.
,
Apr 11 2017
Thanks Don. |
||
►
Sign in to add a comment |
||
Comment 1 by wonderfly@google.com
, Apr 11 2017Components: Infra>Client>ChromeOS
Owner: reinauer@chromium.org
Status: Assigned (was: assin)