Closed Bug 1558240 Opened 6 years ago Closed 5 years ago

The Taskcluster log output is not separated from the captured tidy output

Categories

(Taskcluster :: Workers, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: trink, Assigned: dustin)

Details

The [taskcluster 2019-06-10 16:36:58.754Z] === Task Finished === output should be on its own line

https://queue.taskcluster.net/v1/task/UAEN9erbQ-2CmQVYaStDkA/runs/0/artifacts/public/logs/live_backing.log

I think this has to do with an implicit assumption that everything writing to the logs ends its write with a newline -- which rust did not in this case. The simple fix is probably to insert a newline before the === Task FInished === output.

Assignee: nobody → dustin
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED

This bug was for docker-worker, not generic-worker - so reopening.

Note, I personally disagree that this is a bug even in docker-worker.

Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Yeah I also believe we should fix the thing generating the output as opposed to trying to make the worker 'correct' the output. Please re assign it to the appropriate product/component. This is not a high priority I am just try to make our log output more consistent and silence some complaints/noise from the parser.

:jdm, do you have any guidance on where to send this?

Flags: needinfo?(josh)

If I understand the context correctly, right now the rustup tool prints [ without a newline as the last piece of output. If that's the case, it should be reported to https://github.com/rust-lang/rustup.

Flags: needinfo?(josh)
Status: REOPENED → RESOLVED
Closed: 5 years ago5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.