some canaries are running out of time |
|||||||||
Issue descriptionOak-release build 923 timed out. Earlier and later builds are also close to the 8-hour limit. https://uberchromegw.corp.google.com/i/chromeos/builders/oak-release/builds/923 So I started playing around with viceroy: https://viceroy.corp.google.com/chromeos/build_details?build_config=oak-release&build_number=922 More precisely, the master-release: https://viceroy.corp.google.com/chromeos/build_details?waterfall=chromeos&build_config=master-release&build_number=&milestone_version=&experimental=False&duration=1d&refresh=-1 Failed builds that probably timed out at the most recent build cycles: caroline-release/453 pyro-release/437 snappy-release/422 reef-release/891 caroline-release/452 pyro-release/436 snappy-release/421 reef-release/890 <none> pyro-release/434 snappy-release/419 reef-release/888 Other builders seem to have a solid 1-hour of wiggle room. I wonder if these platforms share the same builder, and if there is something wrong with it.
,
Mar 3 2017
ok I did a few things to oak-release, we'll see if the builder is faster starting with 925...
,
Mar 3 2017
marcheu@ can you list the steps you did. Will help folks in the future.
,
Mar 3 2017
,
Mar 3 2017
@3: yeah if/once I have something that works I'll make a list, then I'll try to get it deployed more broadly. For now my changes didn't take because they weren't persistent and builders reboot at each build, so we'll have to wait a little longer for results.
,
Mar 7 2017
,
Mar 21 2017
,
Apr 3 2017
Is this still happening now?
,
Jun 20 2017
,
Jun 20 2017
Shall we give Stefan a chance to add any findings he may have collected based on comment #5?
,
Jul 17 2017
ChromeOS Infra P1 Bugscrub. P1 Bugs in this component should be important enough to get weekly status updates. Is this already fixed? -> Fixed Is this no longer relevant? -> Archived or WontFix Is this not a P1, based on go/chromeos-infra-bug-slo rubric? -> lower priority. Is this a Feature Request rather than a bug? Type -> Feature Is this missing important information or scope needed to decide how to proceed? -> Ask question on bug, possibly reassign. Does this bug have the wrong owner? -> reassign. Bugs that remain in this state next week will be downgraded to P2.
,
Jul 24 2017
ChromeOS Infra P1 Bugscrub. Issue untouched in a week after previous message. Downgrading to P2.
,
Jun 8 2018
Hi, this bug has not been updated recently. Please acknowledge the bug and provide status within two weeks (6/22/2018), or the bug will be closed. Thank you.
,
Jun 12 2018
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by marc...@chromium.org
, Mar 3 2017