Create new page to show stdout of multiple swarming tasks |
||||
Issue descriptionWe currently download all the stdout of our swarming tasks when collecting their results on the waterfall. This currently can't be removed because it would be hard for developers to easily look at all the test results. If multiple tests fail on multiple shards, it can be hard to determine which shard they would need to look at to see the exact errors in the test. I propose that we add a endpoint in the swarming server that'd have a path of something like https://chromium-swarm.appspot.com/task_stdout?id=deadbeef&id=deadbeef2&id=deadbeef3. This page would simply fetch the stdout in javascript and mux it all together in browser. It might not be that high performant (maybe with optional caching), but I think this would work well enough. Implementing this would allow us to not download stdout when collecting tasks, which I think would save a significant amount of time.
,
Oct 26
I have no preference about where this lives. Milo would be fine. Just would like a page where I can pass multiple swarming task ids, and see the combination of all the tasks stdouts. A log searching service would also theoretically solve this, although there might be other cases that log searching wouldn't let us do. I figure something like the swarming page would be pretty trivial to implement.
,
Oct 26
why would it be in milo? this data belongs to swarming and this use case doesn't fit well into existing milo responsibilities
,
Oct 30
Ping. Any thoughts about where this should live?
,
Oct 30
long term, our work on test results should fix this use case. The service would encapsulate shards and would present the failed tests directly. but if we are talking about a short term hack, milo is probably a better place for it (poor milo)
,
Nov 27
How much time would this actually save? I think we can make a better decision about whether to add tech debt (i.e. before we have a test results service) if we knew how much this is hurting right now.
,
Jan 3
In the Dart builders, we have made all of the shards send their test results back to the parent builder, and the builder displays a combined "Test Results" step with all the results (and the logs). I don't know if there is a better way for the infrastructure to handle it automatically, rather than just forwarding this info in your recipe's shard collection code in your recipes. See the "Test Results" step in this builder, for example: https://ci.chromium.org/p/dart/builders/luci.dart.ci.sandbox/front-end-win-release-x64/3215
,
Jan 9
Fair enough, I can see value in having this hosted on Swarming itself. |
||||
►
Sign in to add a comment |
||||
Comment 1 by maruel@google.com
, Oct 26