Arvados

Prefer to display as log with timestamp

Each time it re-queries, add it to the end.

Revise the messages in run_queue.go

22132-scheduling-status-log @ f4013d381074bfcc1856597dfdb891fa1d0569e9

developer-run-tests: #4457

22132-scheduling-status-log @ ca45a8fe46f4f8520438d01bb7ae5ff28a7e73bb

developer-run-tests: #4469

22132-scheduling-status-messages @ 8668fd5770e7512857821007fba8babf90117ffd

Wordsmithed the scheduling status messages to hopefully be more useful to the end user.

developer-run-tests: #4476

Peter Amstutz wrote in #note-9:

22132-scheduling-status-log @ ca45a8fe46f4f8520438d01bb7ae5ff28a7e73bb

(I'm not reviewing this branch but) it looks like the timestamp regexp is trying to make fractional seconds optional, but didn't make the last "." optional. Maybe should be something like this?

- ... :[0-9]{2}\.[0-9]{0,}Z
+ ... :[0-9]{2}(\.[0-9]{1,9})?Z

Peter Amstutz wrote in #note-10:

22132-scheduling-status-messages @ 8668fd5770e7512857821007fba8babf90117ffd

I think we should update the examples in source:doc/api/dispatch.html.textile.liquid so the capitalization/punctuation matches the new complete-sentence style.

• "Cluster is at capacity for all the eligible instance types" would be better without "the".
• "Waiting in container queue" would be better without "container".

Rest LGTM, thanks.

Wordsmithed the scheduling status messages to hopefully be more useful to the end user.

Messaging to the user is much more readable, while being both thorough and concise.

Peter Amstutz wrote in #note-9:

22132-scheduling-status-log @ ca45a8fe46f4f8520438d01bb7ae5ff28a7e73bb

pending tests, this lgtm