New issue
Advanced search Search tips

Issue 722645 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocking:
issue 715942



Sign in to add a comment

Perf try failed with KeyError 'issue'

Project Member Reported by dominicc@chromium.org, May 16 2017

Issue description

I tried to run a perf try job and it failed:

https://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/5104

Also some of the stdio links 404 so it is hard to see what is going on.
 
Labels: -OS-Linux -Type-Bug -Pri-3 Pri-2 Type-Bug-Regression
This is blocking a P2 issues so bumping it up.

What's the right component to use for these issues? Dashboard?
Cc: d...@chromium.org simonhatch@chromium.org
Components: -Speed Speed>Bisection
How did you kick off the try job? I think the missing "issue" is due to not having a rietveld issue. Simon, is that correct?
Did you use the instructions here: https://www.chromium.org/developers/telemetry/performance-try-bots

The logs are really hard to deal with because we make them only visible to Googlers because they are release official builds and we're not allowed to show logs for them outside of Google. dnj: Do you know why no logdog links are showing up?

Speed>Bisection is the right component since they use they same underlying system.

Comment 3 by d...@chromium.org, May 16 2017

I'm confused by "no LogDog links are showing up"? All of the links after the initial setup are LogDog links.
I noticed this try job is using gerrit (https://chromium-review.googlesource.com/c/505671/), this might be the issue?
Re #3: I took a screenshot of where I was trying to click. All the links in red don't work off-corp, only the two in green are logdog. Dominic and I both had trouble finding the correct link.
logdog.png
53.9 KB View Download
Owner: simonhatch@chromium.org
Will take this for now and poke at the recipe.

Comment 7 by d...@chromium.org, May 16 2017

Oh - those "cache" links are trash, probably should be removed from the template. I think the only reason they're still there is that nobody owns them anymore. Just use the normal links next to them.
Project Member

Comment 8 by bugdroid1@chromium.org, May 18 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/53a6b44b40dade4da9546b3f976313f1cd3f0cbe

commit 53a6b44b40dade4da9546b3f976313f1cd3f0cbe
Author: Simon <simonhatch@chromium.org>
Date: Thu May 18 00:46:54 2017

Bisect - Push gerrit changes to prod.

TBR=dtu@chromium.org
Bug:  722645 
Change-Id: I47b593bd74525ec8814f8276a65a1f653168b9e2
Reviewed-on: https://chromium-review.googlesource.com/508182
Reviewed-by: Simon Hatch <simonhatch@chromium.org>
Commit-Queue: Simon Hatch <simonhatch@chromium.org>

[modify] https://crrev.com/53a6b44b40dade4da9546b3f976313f1cd3f0cbe/scripts/slave/recipe_modules/perf_try/build_state.py

Status: Fixed (was: Unconfirmed)
Should work now, successful run through gerrit: https://chromium-review.googlesource.com/c/507568/

Sign in to add a comment