Skip to content

Mention system property in docs that enable blocked thread detection #8509

Mention system property in docs that enable blocked thread detection

Mention system property in docs that enable blocked thread detection #8509

Triggered via pull request April 13, 2026 08:51
Status Success
Total duration 28m 38s
Artifacts

ci.yml

on: pull_request
Matrix: Test
Matrix: Submit Dependencies
Matrix: Publish Artifacts
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 8 warnings
Test (windows-latest, 2.13.18, graalvm@21, ciJVM)
Exception calling "SetPageFileSize" with "3" argument(s): "The operation completed successfully" At D:\a\_actions\al-cheb\configure-pagefile-action\d298bdee6b133626425040e3788f1055a8b4cf7a\scripts\SetPageFileSize.ps1 :193 char:1 + [Util.PageFile]::SetPageFileSize($minimumSize, $maximumSize, $diskRoo ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [], MethodInvocationException + FullyQualifiedErrorId : Win32Exception
Test (windows-latest, 2.13.18, temurin@21, ciJVM)
Exception calling "SetPageFileSize" with "3" argument(s): "The operation completed successfully" At D:\a\_actions\al-cheb\configure-pagefile-action\d298bdee6b133626425040e3788f1055a8b4cf7a\scripts\SetPageFileSize.ps1 :193 char:1 + [Util.PageFile]::SetPageFileSize($minimumSize, $maximumSize, $diskRoo ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [], MethodInvocationException + FullyQualifiedErrorId : Win32Exception
Test (windows-latest, 2.13.18, temurin@8, ciJVM)
Exception calling "SetPageFileSize" with "3" argument(s): "The operation completed successfully" At D:\a\_actions\al-cheb\configure-pagefile-action\d298bdee6b133626425040e3788f1055a8b4cf7a\scripts\SetPageFileSize.ps1 :193 char:1 + [Util.PageFile]::SetPageFileSize($minimumSize, $maximumSize, $diskRoo ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [], MethodInvocationException + FullyQualifiedErrorId : Win32Exception
Test (windows-latest, 2.13.18, temurin@17, ciJVM)
Exception calling "SetPageFileSize" with "3" argument(s): "The operation completed successfully" At D:\a\_actions\al-cheb\configure-pagefile-action\d298bdee6b133626425040e3788f1055a8b4cf7a\scripts\SetPageFileSize.ps1 :193 char:1 + [Util.PageFile]::SetPageFileSize($minimumSize, $maximumSize, $diskRoo ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [], MethodInvocationException + FullyQualifiedErrorId : Win32Exception
Test (windows-latest, 2.13.18, temurin@11, ciJVM)
Exception calling "SetPageFileSize" with "3" argument(s): "The operation completed successfully" At D:\a\_actions\al-cheb\configure-pagefile-action\d298bdee6b133626425040e3788f1055a8b4cf7a\scripts\SetPageFileSize.ps1 :193 char:1 + [Util.PageFile]::SetPageFileSize($minimumSize, $maximumSize, $diskRoo ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [], MethodInvocationException + FullyQualifiedErrorId : Win32Exception
Test (windows-latest, 2.13.18, graalvm@21, ciJVM)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: al-cheb/configure-pagefile-action@d298bdee6b133626425040e3788f1055a8b4cf7a. 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/
Test (windows-latest, 2.13.18, temurin@21, ciJVM)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: al-cheb/configure-pagefile-action@d298bdee6b133626425040e3788f1055a8b4cf7a. 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/
Test (ubuntu-latest, 3.3.7, temurin@8, ciJS)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v3. 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/
Test (ubuntu-latest, 2.12.21, temurin@8, ciJS)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v3. 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/
Test (windows-latest, 2.13.18, temurin@8, ciJVM)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: al-cheb/configure-pagefile-action@d298bdee6b133626425040e3788f1055a8b4cf7a. 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/
Test (ubuntu-latest, 2.13.18, temurin@8, ciJS)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v3. 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/
Test (windows-latest, 2.13.18, temurin@17, ciJVM)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: al-cheb/configure-pagefile-action@d298bdee6b133626425040e3788f1055a8b4cf7a. 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/
Test (windows-latest, 2.13.18, temurin@11, ciJVM)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: al-cheb/configure-pagefile-action@d298bdee6b133626425040e3788f1055a8b4cf7a. 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/