LUCI builds are still "RUNNING" after they finish |
|
Issue descriptionI've seen this a few times on and off https://chromium-swarm.appspot.com/task?id=3eccc0d659a47b10&refresh=10&show_raw=1&wide_logs=true is an example of this. As I'm writing this, it's state is "RUNNING", but the following annotations are at the bottom of the page: substep: < step: < name: "recipe result" status: SUCCESS started: < seconds: 1532032133 nanos: 668015800 > ended: < seconds: 1532032133 nanos: 674800300 > other_links: < label: "result" logdog_stream: < name: "steps/recipe_result/0/logs/result/0" > > > > stdout_stream: < name: "stdout" > started: < seconds: 1532027200 nanos: 472249700 > ended: < seconds: 1532032134 nanos: 45378300 > > annotation_url: "logdog://logs.chromium.org/chromium/buildbucket/cr-buildbucket.appspot.com/8940546805169322656/+/annotations" recipe: < name: "chromium_trybot" > Which seems to suggest that the task is complete. Is swarming doing something still? It doesn't have an isolated output as far as I know... I don't know if it's possible to see this in tasks that have completed
,
Jul 19
The task will be marked as RUNNING until the overhead is complete, which in some case can be non-trivial.
,
Jul 19
According to the swarming task page, there is no overhead after the task completes. Attachment from task in description. |
|
►
Sign in to add a comment |
|
Comment 1 by martiniss@chromium.org
, Jul 19