New issue
Advanced search Search tips

Issue 700183 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
hinoka@chromium.org
d...@chromium.org
dpranke@chromium.org
estaab@chromium.org
no...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Waterfall pages point to old stdio log instead of new LogDog stdout log

Project Member Reported by ynovikov@chromium.org, Mar 9 2017

Comment 1 by ynovikov@chromium.org, Mar 9 2017

Components: Infra>Platform>LogDog Infra>Platform>Buildbot
Labels: -PlatformLogDog -PlatformBuildBot

Comment 2 by d...@chromium.org, Mar 9 2017 

Thanks for filing! Agree this should be fixed, I'll look into it.

Comment 3 by ynovikov@chromium.org, Mar 14 2017

Cc: estaab@chromium.org hinoka@chromium.org
 Issue 701219  has been merged into this issue.

Comment 4 by hinoka@chromium.org, Mar 21 2018

Status: WontFix (was: Available)
I believe the waterfall is now deprecated, and ci.chromium.org points to logdog correctly.

Comment 5 by d...@chromium.org, Mar 21 2018 

All logs with LogDog links will link to LogDog on the waterfall. There are some BuildBot logs (e.g., "stdio") that will continue to link to BuildBot those logs are in BuildBot, not LogDog.

The problem here is that "stdio" is not a LogDog link - it's a link to the raw BuildBot output. All BuildBot tasks will have raw output, and we want to be able to see that, so we keep that link around. WontFix is appropriate I think.
►

Sign in to add a comment