Daily Test #1677
Annotations
4 errors, 10 warnings, and 6 notices
|
test (windows-2022, microburst.vm microsoft-office.vm mimikatz.vm nanodump.vm nasm.vm net-reactor...
Process completed with exit code 1.
|
|
test (windows-2022, 010editor.vm 7zip.vm adconnectdump.vm advanced-installer.vm aleapp.vm amcache...
Process completed with exit code 1.
|
|
test (windows-2025, floss.vm ftk-imager.vm fuzzdb.vm gadgettojscript.vm garbageman.vm getlapspass...
Process completed with exit code 1.
|
|
test (windows-2022, floss.vm ftk-imager.vm fuzzdb.vm gadgettojscript.vm garbageman.vm getlapspass...
Process completed with exit code 1.
|
|
setup
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/
|
|
test (windows-2022, sclauncher64.vm sdb_explorer.vm seatbelt.vm seclists.vm setdllcharacteristics...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/upload-artifact@5d5d22a31266ced268874388b861e4b58bb5c2f3, actions/upload-artifact@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/
|
|
test (windows-2025, microburst.vm microsoft-office.vm mimikatz.vm nanodump.vm nasm.vm net-reactor...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/upload-artifact@5d5d22a31266ced268874388b861e4b58bb5c2f3, actions/upload-artifact@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/
|
|
test (windows-2025, sclauncher64.vm sdb_explorer.vm seatbelt.vm seclists.vm setdllcharacteristics...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/upload-artifact@5d5d22a31266ced268874388b861e4b58bb5c2f3, actions/upload-artifact@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/
|
|
test (windows-2022, microburst.vm microsoft-office.vm mimikatz.vm nanodump.vm nasm.vm net-reactor...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/upload-artifact@5d5d22a31266ced268874388b861e4b58bb5c2f3, actions/upload-artifact@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/
|
|
test (windows-2025, 010editor.vm 7zip.vm adconnectdump.vm advanced-installer.vm aleapp.vm amcache...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/upload-artifact@5d5d22a31266ced268874388b861e4b58bb5c2f3, actions/upload-artifact@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/
|
|
test (windows-2022, 010editor.vm 7zip.vm adconnectdump.vm advanced-installer.vm aleapp.vm amcache...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/upload-artifact@5d5d22a31266ced268874388b861e4b58bb5c2f3, actions/upload-artifact@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/
|
|
test (windows-2025, floss.vm ftk-imager.vm fuzzdb.vm gadgettojscript.vm garbageman.vm getlapspass...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/upload-artifact@5d5d22a31266ced268874388b861e4b58bb5c2f3, actions/upload-artifact@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/
|
|
test (windows-2022, floss.vm ftk-imager.vm fuzzdb.vm gadgettojscript.vm garbageman.vm getlapspass...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/upload-artifact@5d5d22a31266ced268874388b861e4b58bb5c2f3, actions/upload-artifact@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/
|
|
publish
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11, actions/checkout@v4, actions/download-artifact@v4, schneegans/dynamic-badges-action@e9a478b16159b4d31420099ba146cdc50f134483. 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/
|
|
setup
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
test (windows-2025, microburst.vm microsoft-office.vm mimikatz.vm nanodump.vm nasm.vm net-reactor...
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
test (windows-2025, sclauncher64.vm sdb_explorer.vm seatbelt.vm seclists.vm setdllcharacteristics...
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
test (windows-2025, 010editor.vm 7zip.vm adconnectdump.vm advanced-installer.vm aleapp.vm amcache...
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
test (windows-2025, floss.vm ftk-imager.vm fuzzdb.vm gadgettojscript.vm garbageman.vm getlapspass...
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
publish
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
log-VM-windows-2022-0
|
2.54 KB |
sha256:e0036ecb47b259ea0b7988295112101add119f285e8215f36d2562b61c082555
|
|
|
log-VM-windows-2022-1
|
608 Bytes |
sha256:0a5f41f6166d2c67711f230ad8b382de94cf760ab08c57d39cd5420bfe8867a4
|
|
|
log-VM-windows-2022-2
|
562 Bytes |
sha256:6ac03616715aa34a383ef029a7f61d7bc6b17b91e8baa398786831642bdf6e8e
|
|
|
log-VM-windows-2022-3
|
481 Bytes |
sha256:746901e29ac3b3341be9daf5f87bc817a2eaf38894dd0986071c781c3c1a9f39
|
|
|
log-VM-windows-2025-4
|
4.42 KB |
sha256:447da95734bd1ca602cc0ff60b8e758782e5f41e09764cad3524a88baa507b72
|
|
|
log-VM-windows-2025-5
|
566 Bytes |
sha256:81ceb38144fcb631829c2edcd0640c8e523eb7ec54433ac34152aecd8cdb2c04
|
|
|
log-VM-windows-2025-6
|
517 Bytes |
sha256:bcf115954e314ae835bb6a649ed09ffdccef08f563c18507dcd2e8b026e348b8
|
|
|
log-VM-windows-2025-7
|
481 Bytes |
sha256:cc7f33da60ea547ebc34cbb88e6414f5a6d3b43dc083b7a10d32170205163058
|
|
|
logs-choco-windows-2022-0
|
316 KB |
sha256:22058772012192169b4641d3feb8bef49b17714a86643add0c9de224e4350bb1
|
|
|
logs-choco-windows-2022-1
|
84.8 KB |
sha256:7a5713451c77b059e4df8b0e776e6352d7e66a9d379cbec99391027a090b6a2b
|
|
|
logs-choco-windows-2022-2
|
742 KB |
sha256:bdc5cc30fc28e343db7a0194c0a62e4668119ad7f7df275251e8ad515c9e1936
|
|
|
logs-choco-windows-2022-3
|
672 KB |
sha256:2f429f8cc33322c40476eaa46bee48c1911a08f6f37a4b7a738fb5cefcf5ff58
|
|
|
logs-choco-windows-2025-4
|
313 KB |
sha256:7e064bc76c7291faa58b971f47cf0138e234b86ab9e009c51af652e382f2a2cb
|
|
|
logs-choco-windows-2025-5
|
23.7 KB |
sha256:8620a5d7491e4cc663273ef087d1f9672179e73964c7e816f8a98b43529edee8
|
|
|
logs-choco-windows-2025-6
|
714 KB |
sha256:517ba2aa24ba3ee4b90cba544fc6ca96fc73eec83c429a64324779af02cc4472
|
|
|
logs-choco-windows-2025-7
|
704 KB |
sha256:d0d3f75434b5174dbfa6b44bec5edf21be15321f871b88ba59c9002dca670269
|
|
|
success_failure_Win10_0
|
220 Bytes |
sha256:671f19d59ab4211f73606a87a01d035f4d43c4c8b30a238d30d1ffdba3dfb8a6
|
|
|
success_failure_Win10_1
|
267 Bytes |
sha256:4d8f173d64a21b2c578d3b2f4def043a81cdb759aed78cd1d6291deb655ae794
|
|
|
success_failure_Win10_2
|
258 Bytes |
sha256:a2df470fc637ef8a92a8e3a93d05d6e8ae3fa6e272fbee337852039963d43b2b
|
|
|
success_failure_Win10_3
|
203 Bytes |
sha256:5cfcbda5f6b9366aa66054b35c9114408678e5080f561d2ab5d899488fa3eaf6
|
|
|
success_failure_Win11_4
|
203 Bytes |
sha256:64e1e888d0cc16023fb1e3d9fbf8c2d46ee640ca551378e4b97c95244c331a0c
|
|
|
success_failure_Win11_5
|
225 Bytes |
sha256:210cfa9abaffad3eb735a1a45b4934410d6bd926e3f2dc498e2542a6078892fd
|
|
|
success_failure_Win11_6
|
206 Bytes |
sha256:0de44317461046b49b7c286e3d78b9cf93551dd648b095e747d4b64cbfba90b3
|
|
|
success_failure_Win11_7
|
203 Bytes |
sha256:079c95f4e2c690deb5657b4d8cdf9c5d66c22aa4bac7d9711aa2593216d2c500
|
|