sharpca commented on PR #13081: URL: https://github.com/apache/seatunnel/pull/13081#issuecomment-6634176749
Update on `unit-test (17, ubuntu-latest)`: it is not a test failure and it is not the job timeout. - `unit-test` declares `timeout-minutes: 120` in `backend.yml`, and the job ran 06:30:57Z → 07:25:11Z, i.e. 54m14s. - In the job record, step 4 `run all modules unit test` is still `in_progress` with a null conclusion, and `Upload test reports` plus the two post steps are `pending`. The job therefore ended while the Maven step was still executing, before anything could be uploaded. - That job produced no report artifact (the run's only artifact belongs to `all-connectors-it-5`), so no test failed. - The same job also failed on this branch's earlier commit `24c2d878` (run https://github.com/sharpca/seatunnel/actions/runs/41675888169), so it is not specific to `cac71da1`. So the job was terminated runner-side mid-step, which is also why every completed step looks green while the job is red. The remaining failure in this run is the `TiDBCDCIT` container-startup `CommunicationsException` in `all-connectors-it-5`, unchanged from my previous comment. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
