New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 896803 link

Starred by 1 user
Status: Verified
Owner:
jclinton@chromium.org
Closed: Oct 19
Cc:
█ dburger@chromium.org
hinoka@chromium.org
█ jinjingl@chromium.org
athilenius@chromium.org
la...@chromium.org
jclinton@chromium.org
mikenichols@chromium.org
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 0
Type: Bug



Sign in to add a comment

Legoland log links broken by changes to Logdog URLs.

Project Member Reported by dgarr...@chromium.org, Oct 18 
It seems that Legoland does not correctly escape Logdog information when generating logging links, which has broken after a recent Logdog update.

Current Logs are not accessable through Legoland web pages.

The workaround is to switch to the Milo build views (linked from Legoland).

Comment 1 by dgarr...@chromium.org, Oct 18

Cc: jinjingl@chromium.org

Comment 2 by jclinton@google.com, Oct 18

Owner: jclinton@chromium.org
Status: Started (was: Untriaged)

Comment 3 by la...@chromium.org, Oct 18 

Legoland needs to escape a "+" as "%2B" because it appears in the URL query string. jclinton@ is working on the fix.

Comment 6 by jclinton@google.com, Oct 19

Status: Verified (was: Started)
Fix deployed to Prod and confirmed working. Sorry for the disruption.
►

Sign in to add a comment