Skip to content

Ensure new track plays from start after replacement #373

Ensure new track plays from start after replacement

Ensure new track plays from start after replacement #373

Triggered via pull request October 19, 2023 11:30
Status Failure
Total duration 6m 16s
Artifacts

validate.yml

on: pull_request
Matrix: unit-tests
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 5 warnings
unit-tests (29, x86_64, google_apis, 600, 0)
❌ Failed to create checks using the provided token. (HttpError: Resource not accessible by integration)
unit-tests (29, x86_64, google_apis, 600, 0)
Final attempt failed. Child_process exited with error code 1
unit-tests (29, x86_64, google_apis, 600, 0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2. 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 (29, x86_64, google_apis, 600, 0)
⚠️ This usually indicates insufficient permissions. More details: https://github.com/mikepenz/action-junit-report/issues/23
unit-tests (29, x86_64, google_apis, 600, 0)
Attempt 1 failed. Reason: Child_process exited with error code 1
unit-tests (29, x86_64, google_apis, 600, 0)
Attempt 2 failed. Reason: Child_process exited with error code 1
build-sample
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/