"cleanup_temp" is flaky |
|||||
Issue description"cleanup_temp" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 59 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyFwsSBUZsYWtlIgxjbGVhbnVwX3RlbXAM.
,
Oct 26 2016
This looks to me like an infra problem, runit.py is not part of Chromium. It's mentioned in https://chromium.googlesource.com/chromium/src/+/master/docs/using_build_runner.md but doesn't mention which repo it's in, the other mentions are in infra/, so assigning to current trooper and CCing some folks.
,
Oct 26 2016
Script was written ~3 years ago by iannucci@: https://chromiumcodereview.appspot.com/17635005, but it was also modified by others: dnj@, pgervais@, sbc@, xusydoc@.
,
Oct 26 2016
,
Oct 26 2016
Here the problem seems to be that the script isn't there at all, could something have gone wrong with the checkout steps earlier perhaps?
,
Oct 26 2016
I suspect it's related to a recent move to recipes-in-repo. Pawel should know more about it and he's already CC'd.
,
Oct 26 2016
I believe it was caused by https://codereview.chromium.org/2445193002 , reverted in https://codereview.chromium.org/2454563002 . Example failing build: https://build.chromium.org/p/tryserver.blink/builders/linux_precise_blink_rel/builds/4412/steps/steps/logs/stdio : remote_run.py --repository https://chromium.googlesource.com/chromium/tools/build.git Example passing build: https://build.chromium.org/p/tryserver.blink/builders/linux_precise_blink_rel/builds/4416/steps/steps/logs/stdio : remote_run.py --repository https://chromium.googlesource.com/chromium/src.git
,
Oct 26 2016
This was probably caused by my change. I'm not sure why, but the timeline matches up. I'll investigate why it happened. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by foolip@chromium.org
, Oct 26 2016