Skip to content

Add .whitesource configuration file #60

Add .whitesource configuration file

Add .whitesource configuration file #60

Triggered via push March 31, 2026 10:41
Status Failure
Total duration 45m 56s
Artifacts

linux.yml

on: push
x86_64-musl-test
36m 40s
x86_64-musl-test
x86_64-gnu-test-preview_mt
5m 44s
x86_64-gnu-test-preview_mt
check_format
1m 49s
check_format
deploy_api_docs
0s
deploy_api_docs
Matrix: x86_64-gnu-test
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 5 warnings
x86_64-gnu-test-preview_mt
Process completed with exit code 1.
x86_64-gnu-test (1.6.2, USE_PCRE1=true)
The strategy configuration was canceled because "x86_64-gnu-test._1_9_2" failed
x86_64-gnu-test (1.7.3)
The strategy configuration was canceled because "x86_64-gnu-test._1_9_2" failed
x86_64-gnu-test (1.8.2)
The strategy configuration was canceled because "x86_64-gnu-test._1_9_2" failed
x86_64-gnu-test (1.4.1, USE_PCRE1=true)
The strategy configuration was canceled because "x86_64-gnu-test._1_9_2" failed
x86_64-gnu-test (1.0.0, FLAGS=-Dwithout_ffi USE_PCRE1=true)
The strategy configuration was canceled because "x86_64-gnu-test._1_9_2" failed
x86_64-gnu-test (1.10.1)
The strategy configuration was canceled because "x86_64-gnu-test._1_9_2" failed
x86_64-gnu-test (1.9.2)
Process completed with exit code 1.
x86_64-gnu-test (1.3.2, USE_PCRE1=true)
The strategy configuration was canceled because "x86_64-gnu-test._1_9_2" failed
x86_64-gnu-test (1.1.1, FLAGS=-Dwithout_ffi USE_PCRE1=true)
The strategy configuration was canceled because "x86_64-gnu-test._1_9_2" failed
x86_64-gnu-test (1.2.2, USE_PCRE1=true)
The strategy configuration was canceled because "x86_64-gnu-test._1_9_2" failed
x86_64-gnu-test (1.11.2)
The strategy configuration was canceled because "x86_64-gnu-test._1_9_2" failed
x86_64-gnu-test (1.5.1, USE_PCRE1=true)
The strategy configuration was canceled because "x86_64-gnu-test._1_9_2" failed
x86_64-gnu-test (1.5.1, USE_PCRE1=true)
The operation was canceled.
x86_64-gnu-test-preview_mt
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
x86_64-gnu-test (1.9.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
x86_64-gnu-test (1.5.1, USE_PCRE1=true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
check_format
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
x86_64-musl-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/