Skip to content

Backport of Do not acquire a read lock twice on tidyStatusLock during tidy-status into release/1.17.x #9601

Backport of Do not acquire a read lock twice on tidyStatusLock during tidy-status into release/1.17.x

Backport of Do not acquire a read lock twice on tidyStatusLock during tidy-status into release/1.17.x #9601

Triggered via pull request October 2, 2024 13:28
Status Success
Total duration 11s
Artifacts

remove-labels.yml

on: pull_request_target
RemoveWaitingLabelFromClosedIssueOrPR
3s
RemoveWaitingLabelFromClosedIssueOrPR
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
RemoveWaitingLabelFromClosedIssueOrPR
Error: failed to remove labels: waiting-for-response
RemoveWaitingLabelFromClosedIssueOrPR
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-ecosystem/action-remove-labels@2ce5d41b4b6aa8503e285553f75ed56e0a40bae0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
RemoveWaitingLabelFromClosedIssueOrPR
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-ecosystem/action-remove-labels@2ce5d41b4b6aa8503e285553f75ed56e0a40bae0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
RemoveWaitingLabelFromClosedIssueOrPR
failed to remove label: waiting-for-response: HttpError: Label does not exist