All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=814200

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=6e272ead6c39eafd1ab0f608055a877e332c1174c407474e11bb639e88aca1e8


Bot(s) for this bug's original alert(s):

chromium-rel-mac12

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/11d88987840000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/11d88987840000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/13afb057840000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/13afb057840000

This is weird, the bots aren't finding anything but the graph has clearly changed.  I note the ref has not.

Annie what do you make of this?

Really sorry about this, looks like there was a swarming failure and it's not actually a no-repro. Better reporting for this is on Dave's list this week (https://github.com/catapult-project/catapult/issues/4231).

Dave, Simon, any idea whether the swarming failure is transient, or does something need to be fixed before retrying?

From the swarming output:

Traceback (most recent call last):
  File "../../testing/test_env.py", line 288, in <module>
    sys.exit(main())
  File "../../testing/test_env.py", line 284, in main
    return run_executable(sys.argv[1:], os.environ.copy())
  File "../../testing/test_env.py", line 248, in run_executable
    '-vpython-tool', 'install',
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 535, in check_call
    retcode = call(*popenargs, **kwargs)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 522, in call
    return Popen(*popenargs, **kwargs).wait()
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 710, in __init__
    errread, errwrite)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 1335, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

+robbie

Never seen this before, not sure who the right person is for this, vpython seems to be missing?

There were a few dozen of jobs with this error yesterday. It's being tracked in issue 812693. The CL is in Chromium, so we don't currently have a way to bisect over that range.

WontFix-ing since this is only 65KiB.

Eep, sorry I missed the cc here. I think the underlying swarming failure is fixed now, though.