Skip to content
issue-robot

After reporting an error in the batch on the same day, the batch on the second day needs to be stuck. Currently, there is no relevant configuration and the batch starts normally on the second day. After reporting an error in the batch on the same day, the batch on the second day needs to be stuck. Currently, there is no relevant configuration and the batch is started normally on the second day. #1707

Sign in to view logs

After reporting an error in the batch on the same day, the batch on the second day needs to be stuck. Currently, there is no relevant configuration and the batch starts normally on the second day. After reporting an error in the batch on the same day, the batch on the second day needs to be stuck. Currently, there is no relevant configuration and the batch is started normally on the second day.

After reporting an error in the batch on the same day, the batch on the second day needs to be stuck. Currently, there is no relevant configuration and the batch starts normally on the second day. After reporting an error in the batch on the same day, the batch on the second day needs to be stuck. Currently, there is no relevant configuration and the batch is started normally on the second day. #1707

Triggered via issue August 1, 2023 06:55
@zhangjun-zhzhangjun-zh
opened #14681 37ecd26
Status Failure
Total duration 26s
Artifacts –

issue-robot.yml

on: issues
issueRobot
18s
issueRobot
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
issueRobot
Docker build failed with exit code 1
issueRobot
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, ./.github/actions/translate-on-issue. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/