Skip to content
py-tests

FIX: handle potential null node in DQ failure lineage #28014

Sign in to view logs

FIX: handle potential null node in DQ failure lineage

FIX: handle potential null node in DQ failure lineage #28014

Triggered via pull request November 20, 2024 10:10
@TeddyCrTeddyCr
opened #18707
Status Failure
Total duration 1h 11m 59s
Artifacts –

py-tests.yml

on: pull_request_target
Matrix: py-run-tests
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
py-run-tests (3.11)
Process completed with exit code 2.
py-run-tests (3.9)
Process completed with exit code 2.
py-run-tests (3.8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/setup-python@v4, nick-fields/retry@v2.8.3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
py-run-tests (3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/setup-python@v4, nick-fields/retry@v2.8.3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
py-run-tests (3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/setup-python@v4, nick-fields/retry@v2.8.3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
py-run-tests (3.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/checkout@v3, actions/setup-java@v3, actions/setup-python@v4, nick-fields/retry@v2.8.3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/