Feature request: Add link to equivalent waterfall builder from trybot builder |
||
Issue descriptionFeature request: Add link to equivalent waterfall builder from trybot builder. When investigating a try failure it would be good to be able to verify whether the failure is happening on ToT and what CL caused it. Example: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-marshmallow-arm64-rel/146405 fails compile on files unrelated to my CL. It would be helpful to jump to the waterfall builder and bisect the builds to find the culprit CL.
,
Dec 7
No, config schema doesn’t encode builder relationships
,
Dec 7
Check step #2 in the linked build. The text is: """ report builders running builder/tester 'android-marshmallow-arm64-rel' on master 'chromium.android' running builder/tester 'Android Release (Nexus 5X)' on master 'chromium.gpu' """ That points to the equivalent builder(s) for the trybot. Plugging that into https://luci-milo.appspot.com/search takes you to https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/android-marshmallow-arm64-rel where it indeed was failing compile in the same way. Is that sufficient to close this out? Or is there something more you'd like?
,
Dec 7
Might be good to make that a bit more seamless & more apparent.
,
Dec 10
TIL "report builders" and https://luci-milo.appspot.com/search, ty. I'm satisfied though I've had the privilege of reading this bug, I'd leave this one open as a feature request for the UI to make this clearer on the build page. |
||
►
Sign in to add a comment |
||
Comment 1 by qyears...@chromium.org
, Dec 7