milo links are all named logdog |
|||||||
Issue descriptionhttps://luci-milo.appspot.com/buildbot/chromium.perf/Win%207%20x64%20Perf/565 is an example battor.steady_state.reference on (102b) GPU on Windows on Windows-2008ServerR2-SP1 battor.steady_state.reference on (102b) GPU on Windows on Windows-2008ServerR2-SP1 stdout json.output swarming.summary outdir_json DISABLED_BENCHMARK step_metadata shard #0 The above is what buildbot has. battor.steady_state.reference on (102b) GPU on Windows on Windows-2008ServerR2-SP1 ( 4 ms ) battor.steady_state.reference on (102b) GPU on Windows on Windows-2008ServerR2-SP1 stdout logdog logdog logdog logdog logdog shard #0 The above is what milo shows. We depend on seeing a step log named "swarming.summary" in sheriff-o-matic. That might not be a good idea..
,
Apr 6 2017
The change is rolled back
,
Apr 6 2017
,
Apr 6 2017
The following revision refers to this bug: https://chromium.googlesource.com/external/github.com/luci/luci-go.git/+/afac4f28a475757e790a3b03d5b0e0eb87d38c17 commit afac4f28a475757e790a3b03d5b0e0eb87d38c17 Author: hinoka <hinoka@google.com> Date: Thu Apr 06 21:58:38 2017 Milo: Fix logdog links BUG= 709229 Review-Url: https://codereview.chromium.org/2797373003 [modify] https://crrev.com/afac4f28a475757e790a3b03d5b0e0eb87d38c17/milo/appengine/buildbot/build.go
,
Apr 6 2017
This should be fixed now.
,
May 30 2017
,
Aug 1 2017
,
Jan 22 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by no...@chromium.org
, Apr 6 2017Components: -Infra>Platform>Milo Infra>Platform>Milo>Buildbot
Labels: -Pri-2 Pri-0