Skip to content

Retry mechanism for failed JWT related errors resolve #1161

Retry mechanism for failed JWT related errors resolve

Retry mechanism for failed JWT related errors resolve #1161

Triggered via pull request November 7, 2023 11:49
Status Failure
Total duration 10m 25s
Artifacts 2

build.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
Check
Process completed with exit code 1.
Report coverage
Process completed with exit code 255.
Check
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Unit tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Instrumentation tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Report coverage
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, actions/download-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Artifacts

Produced during runtime
Name Size
instrumentation-tests Expired
990 KB
unit-tests Expired
983 KB