Issue metadata
Sign in to add a comment
|
Unable to see tryjobs of the older patchsets |
||||||||||||||||||||||
Issue descriptionAffected Version: (2.15-rc2-1818-gdd2c57472e) What steps will reproduce the problem? 1. Open CL https://chromium-review.googlesource.com/c/chromium/src/+/857077 2. Switch to Patchset 1 (Or simply open https://chromium-review.googlesource.com/c/chromium/src/+/857077/1) What is the expected output? Tryjobs triggered from Patchset 1. What do you see instead? Tryjobs triggered from the latest patchset. It used to work until very recently (I only noticed the feature broke today).
,
Jan 10 2018
,
Jan 10 2018
,
Jan 10 2018
,
Jan 10 2018
Issue gerrit:8125 has been merged into this issue.
,
Jan 11 2018
Issue gerrit:8141 has been merged into this issue.
,
Jan 11 2018
It seems quite a few people have seen this problem. Checking previous tryjob results and comparing against the current ones are rather common/crucial in many workflows. Do you have any more info on this regression?
,
Jan 16 2018
Yep, I'm duping this into our main tracking bug, which is blocked on the underlying Gerrit bug. I've escalated and they're looking into it on their side. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by beckysiegel@google.com
, Jan 9 2018