Skip to content

Fix potentially using wrong env to get procs when threaded #351

Fix potentially using wrong env to get procs when threaded

Fix potentially using wrong env to get procs when threaded #351

Triggered via push August 31, 2023 13:25
Status Success
Total duration 11m 38s
Artifacts
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
build_linux
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/
build_mac
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/
build_windows
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/
publish
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/
publish
Unexpected input(s) 'input', valid inputs are ['entryPoint', 'args', 'include', 'exclude', 'find', 'replace', 'regex']