digdag icon indicating copy to clipboard operation
digdag copied to clipboard

Wrong order in task log with group retry

Open yoyama opened this issue 6 years ago • 0 comments

Order of task log by 'digdag log ' cli is wrong.

_retry: 2
+task1:
  sh>: "sleep 2 && echo aaa"
+task2:
  sh>: "sleep 2 && echo bbb"
+task3:
  sh>: "sleep 2 && echo ccc && exit 1"

When run above WF and show task log, the cli result is as follows.

019-09-12 18:34:18.215 +0900 [INFO] (0041@[0:group_retry_fix_IT1]+test_log_order+task1) io.digdag.core.agent.OperatorManager: sh>: sleep 2 && echo aaa
aaa
2019-09-12 18:34:28.521 +0900 [INFO] (0041@[0:group_retry_fix_IT1]+test_log_order+task1) io.digdag.core.agent.OperatorManager: sh>: sleep 2 && echo aaa
aaa
2019-09-12 18:34:37.555 +0900 [INFO] (0041@[0:group_retry_fix_IT1]+test_log_order+task1) io.digdag.core.agent.OperatorManager: sh>: sleep 2 && echo aaa
aaa
2019-09-12 18:34:21.650 +0900 [INFO] (0041@[0:group_retry_fix_IT1]+test_log_order+task2) io.digdag.core.agent.OperatorManager: sh>: sleep 2 && echo bbb
bbb
2019-09-12 18:34:31.905 +0900 [INFO] (0041@[0:group_retry_fix_IT1]+test_log_order+task2) io.digdag.core.agent.OperatorManager: sh>: sleep 2 && echo bbb
bbb
2019-09-12 18:34:40.774 +0900 [INFO] (0041@[0:group_retry_fix_IT1]+test_log_order+task2) io.digdag.core.agent.OperatorManager: sh>: sleep 2 && echo bbb
bbb
2019-09-12 18:34:25.069 +0900 [INFO] (0041@[0:group_retry_fix_IT1]+test_log_order+task3) io.digdag.core.agent.OperatorManager: sh>: sleep 2 && echo ccc && exit 1
ccc
...

The order is not time series. This is because, cli firstly group the log with task name.

yoyama avatar Sep 12 '19 09:09 yoyama