Skip to content

fix: parse record-typed candidate response values when reading the remote results.xml #254

fix: parse record-typed candidate response values when reading the remote results.xml

fix: parse record-typed candidate response values when reading the remote results.xml #254

Triggered via pull request November 8, 2024 11:29
Status Failure
Total duration 40s
Artifacts

continuous-integration.yaml

on: pull_request
Matrix: ci
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
ci (ubuntu-latest, 7.4)
Process completed with exit code 1.
ci (ubuntu-latest, 8.1)
Process completed with exit code 1.
ci (ubuntu-latest, 8.0)
Process completed with exit code 1.
ci (ubuntu-latest, 7.4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ci (ubuntu-latest, 8.1)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ci (ubuntu-latest, 8.0)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/