Skip to content

[ISSUE #7534] Use high performance concurrent set to replace copyonwr… #245

[ISSUE #7534] Use high performance concurrent set to replace copyonwr…

[ISSUE #7534] Use high performance concurrent set to replace copyonwr… #245

Triggered via pull request December 4, 2023 05:51
Status Success
Total duration 39m 3s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

maven.yaml

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

Annotations

1 error and 3 warnings
maven-compile (windows-latest, JDK-8)
The consumer not running, please start it first.
maven-compile (ubuntu-latest, JDK-8)
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/
maven-compile (windows-latest, JDK-8)
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/
maven-compile (macos-latest, JDK-8)
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/