New issue
Advanced search Search tips

Issue 594140 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Win 7 Perf (3) failing since #9007

Project Member Reported by picksi@chromium.org, Mar 11 2016

Issue description

https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%207%20Perf%20(3)

Logs of failed builds contain little information:

Traceback (most recent call last):
  File "C:\b\build\slave\Win_7_Perf__3_\build\src\testing\scripts\gtest_perf_test.py", line 81, in <module>
    sys.exit(common.run_script(sys.argv[1:], funcs))
  File "C:\b\build\slave\Win_7_Perf__3_\build\src\testing\scripts\common.py", line 59, in run_script
    return args.func(args)
  File "C:\b\build\slave\Win_7_Perf__3_\build\src\testing\scripts\gtest_perf_test.py", line 56, in main_run
    rc = common.run_runtest(args, gtest_args + filter_tests)
  File "C:\b\build\slave\Win_7_Perf__3_\build\src\testing\scripts\common.py", line 80, in run_runtest
    cmd_args.paths['runit.py'],
KeyError: 'runit.py'

Not sure what the "KeyError" is, a cause or effect?
 
Cc: dtu@chromium.org
Dave, any recipe changes lately that could have caused this?
Labels: -Infra-Android Infra OS-Windows
not sure if there's an Infra label specifically for windows issues
Owner: bpastene@chromium.org
Status: Assigned (was: Untriaged)
It's probably due to the fact that this bot is failing update_scripts and is unable to pick up the fix. I'll unbreak the step and see if that helps.
Status: Fixed (was: Assigned)
It's passing update_scripts now and has ran a couple green builds. Looks like it's good.

Sign in to add a comment