New issue
Advanced search Search tips

Issue 729080 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Trybot logs for gerrit CLs do not link back to the CL

Project Member Reported by ellyjo...@chromium.org, Jun 2 2017

Issue description

For example, this build:

https://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_ng/builds/468969

was for this CL:

https://chromium-review.googlesource.com/c/521344/

but the CL part of the log is:

Change #2663430

Changed by	ellyjones@chromium.org
Changed at	Fri 02 Jun 2017 10:33:36
Repository	https://chromium.googlesource.com/chromium/src
Changed files

no files
Properties

Buildbucket	{u'change_id': None}

 
Cc: hinoka@chromium.org
Components: Infra>Platform>Milo
Hmm, that's odd. Ryan, any ideas what might be happening here?

I don't see the number showing up in milo and patch_issue seems to reference the correct CL.
Status: Available (was: Untriaged)
Status: WontFix (was: Available)
For buildbot, you'll want to click on the red "patch_issue" link on the properties.  In the milo view this is being fixes in bug 728008 to surface it on top of the page. 

The blamelist on the bottom that you're referencing isn't useful for tryjobs (since it's incorrect).  It used to not show up in rietveld mode, but it does in gerrit mode.  You can safely ignore it.

Sign in to add a comment