New issue
Advanced search Search tips

Issue 828478 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocked on:
issue 792780

Blocking:
issue 821414
issue 821961



Sign in to add a comment

Pinpoint is broken

Project Member Reported by beccahughes@chromium.org, Apr 3 2018

Issue description

All my pinpoint jobs are failing due to INFRA_FAILURE:

Traceback (most recent call last):
  File "/base/data/home/apps/s~chromeperf/pinpoint:dev-dtu-0a85465e.408677720206101898/dashboard/pinpoint/models/quest/execution.py", line 99, in Poll
    self._Poll()
  File "/base/data/home/apps/s~chromeperf/pinpoint:dev-dtu-0a85465e.408677720206101898/dashboard/pinpoint/models/quest/find_isolate.py", line 73, in _Poll
    self._CheckBuildStatus()
  File "/base/data/home/apps/s~chromeperf/pinpoint:dev-dtu-0a85465e.408677720206101898/dashboard/pinpoint/models/quest/find_isolate.py", line 103, in _CheckBuildStatus
    raise BuildError('Build failed: ' + status['build']['failure_reason'])
BuildError: Build failed: INFRA_FAILURE

e.g.

https://pinpoint-dot-chromeperf.appspot.com/job/16af0b40c40000
 
Owner: jchin...@chromium.org
Assigning to current infra trooper
Owner: simonhatch@chromium.org
Simon, could you take a look at this? Thanks!
Cc: simonhatch@chromium.org
Components: -Infra>Client>Perf Speed>Bisection
Owner: dtu@chromium.org
+dtu

Comment 4 by dtu@chromium.org, Apr 3 2018

Blockedon: 792780
Status: Fixed (was: Untriaged)
This is because of the builder migration today.
https://bugs.chromium.org/p/chromium/issues/detail?id=792780#c65

I've updated the Pinpoint configurations so we should be good to go now.
Status: Assigned (was: Fixed)
Thanks, although I tried to rerun the jobs and got a different error this time:

Traceback (most recent call last):
  File "/base/data/home/apps/s~chromeperf/pinpoint:dev-dtu-f2bde269.408767502487382406/dashboard/pinpoint/models/quest/execution.py", line 99, in Poll
    self._Poll()
  File "/base/data/home/apps/s~chromeperf/pinpoint:dev-dtu-f2bde269.408767502487382406/dashboard/pinpoint/models/quest/find_isolate.py", line 73, in _Poll
    self._CheckBuildStatus()
  File "/base/data/home/apps/s~chromeperf/pinpoint:dev-dtu-f2bde269.408767502487382406/dashboard/pinpoint/models/quest/find_isolate.py", line 103, in _CheckBuildStatus
    raise BuildError('Build failed: ' + status['build']['failure_reason'])
BuildError: Build failed: INVALID_BUILD_DEFINITION
Possibly related: https://ci.chromium.org/buildbot/tryserver.chromium.perf/Win%20x64%20Builder/840?

Traceback (most recent call last):
  File "C:\b\rr\tmpnrl_tu\rw\checkout\scripts\slave\.recipe_deps\recipe_engine\recipe_engine\run.py", line 287, in _new_run
    recipe_result = recipe_script.run(api, self.properties, self.environ)
  File "C:\b\rr\tmpnrl_tu\rw\checkout\scripts\slave\.recipe_deps\recipe_engine\recipe_engine\loader.py", line 98, in run
    self.run_steps, properties, environ, self.PROPERTIES, api=api)
  File "C:\b\rr\tmpnrl_tu\rw\checkout\scripts\slave\.recipe_deps\recipe_engine\recipe_engine\loader.py", line 626, in invoke_with_properties
    arg_names, **additional_args)
  File "C:\b\rr\tmpnrl_tu\rw\checkout\scripts\slave\.recipe_deps\recipe_engine\recipe_engine\loader.py", line 589, in _invoke_with_properties
    return callable_obj(*props, **additional_args)
  File "C:\b\rr\tmpnrl_tu\rw\checkout\scripts/slave\recipes\pinpoint/builder.py", line 18, in RunSteps
    bot = api.chromium_tests.trybots[mastername]['builders'][buildername]
  File "C:\b\rr\tmpnrl_tu\rw\checkout\scripts\slave\.recipe_deps\recipe_engine\recipe_engine\types.py", line 66, in __getitem__
    return self._d[key]
KeyError: 'Win x64 Builder'
Blocking: 821414 821961
Pinpoint being broken is blocking our performance bugs. Adding them as blocking here.

Comment 8 by dtu@chromium.org, Apr 3 2018

Status: Fixed (was: Assigned)
Landed a master restart to update Buildbot. Please try again!
https://chrome-internal-review.googlesource.com/c/infradata/master-manager/+/601219
Thank you it's working now :)

Sign in to add a comment