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

Issue 659555 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

"cleanup_temp" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Oct 26 2016

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.


 

Comment 1 by foolip@chromium.org, Oct 26 2016

@@@STEP_CURSOR@cleanup_temp@@@
@@@STEP_STARTED@@@
python -u /b/rr/tmpygumLc/rw/checkout/scripts/tools/runit.py --show-path python /b/rr/tmpygumLc/rw/checkout/scripts/slave/cleanup_temp.py
in dir /b/rr/tmpygumLc/w:
@@@STEP_LINK@stdout-->stdio@https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Ftryserver.blink%2Flinux_precise_blink_rel%2F4404%2F%2B%2Frecipes%2Fsteps%2Fcleanup_temp%2F0%2Fstdout@@@
 allow_subannotations: False
 base_name: cleanup_temp
 cmd: ['python', '-u', '/b/rr/tmpygumLc/rw/checkout/scripts/tools/runit.py', '--show-path', 'python', '/b/rr/tmpygumLc/rw/checkout/scripts/slave/cleanup_temp.py']
 infra_step: True
 name: cleanup_temp
 nest_level: 0
 ok_ret: frozenset([0])
 trigger_specs: []
full environment:
 AWS_CREDENTIAL_FILE: /b/build/site_config/.boto
 BOTO_CONFIG: /b/build/site_config/.boto
 BUILDBOT_BLAMELIST: [u'jaydasika@chromium.org']
 BUILDBOT_BRANCH: 
 BUILDBOT_BUILDBOTURL: http://build.chromium.org/p/tryserver.blink/
 BUILDBOT_BUILDERNAME: linux_precise_blink_rel
 BUILDBOT_BUILDNUMBER: 4404
 BUILDBOT_CLOBBER: 
 BUILDBOT_GOT_REVISION: None
 BUILDBOT_MASTERNAME: tryserver.blink
 BUILDBOT_REVISION: 
 BUILDBOT_SCHEDULER: None
 BUILDBOT_SLAVENAME: slave504-c4
 CHROME_HEADLESS: 1
 DISPLAY: :0.0
 GIT_USER_AGENT: linux2 git/2.10.1 slave504-c4.c.chromecompute.google.com.internal
 HOME: /home/chrome-bot
 LANG: en_US.UTF-8
 PAGER: cat
 PATH: /home/chrome-bot/slavebin:/b/depot_tools:/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin
 PWD: /b/build/slave/linux_precise_layout/build
 PYTHONPATH: /b/build/site_config:/b/build/scripts:/b/build/scripts/release:/b/build/third_party:/b/build/third_party/requests_2_10_0:/b/build_internal/site_config:/b/build_internal/symsrc:/b/build/slave:/b/build/third_party/buildbot_slave_8_4:/b/build/third_party/twisted_10_2:
 PYTHONUNBUFFERED: 1
 TESTING_SLAVENAME: slave504-c4
 USER: chrome-bot
 USERNAME: chrome-bot

python: can't open file '/b/rr/tmpygumLc/rw/checkout/scripts/tools/runit.py': [Errno 2] No such file or directory
step returned non-zero exit code: 2
@@@STEP_EXCEPTION@@@

Comment 2 by foolip@chromium.org, Oct 26 2016

Cc: dpranke@chromium.org xusydoc@chromium.org phajdan.jr@chromium.org
Owner: serg...@chromium.org
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.
Cc: iannucci@chromium.org
Script was written ~3 years ago by iannucci@: https://chromiumcodereview.appspot.com/17635005, but it was also modified by others: dnj@, pgervais@, sbc@, xusydoc@.
Owner: ----

Comment 5 by foolip@chromium.org, 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?
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.
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