Skip to content

Daily Test

Daily Test #1674

Triggered via schedule May 23, 2026 04:31
Status Failure
Total duration 1h 33m 27s
Artifacts 24

daily.yml

on: schedule
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

11 errors, 10 warnings, and 6 notices
publish
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
publish
could not read Username for 'https://github.com': terminal prompts disabled
publish
Cannot prompt because user interactivity has been disabled.
publish
could not read Username for 'https://github.com': terminal prompts disabled
publish
Cannot prompt because user interactivity has been disabled.
publish
could not read Username for 'https://github.com': terminal prompts disabled
publish
Cannot prompt because user interactivity has been disabled.
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-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-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, 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-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, 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@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/
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.53 KB
sha256:b2127c31217f625d1328572fbb7c64b631551a093edcccffdd0b11ee7027ba2a
log-VM-windows-2022-1
607 Bytes
sha256:90d68207e093ed1f2fdfa48440f86fbcc0344a9ef451e49f17f73094a5bbbfff
log-VM-windows-2022-2
560 Bytes
sha256:1523f47224d0ee3a0b6c974d91bca1b8437a42e96695c926191659d5a48fc793
log-VM-windows-2022-3
481 Bytes
sha256:ee4ec02413fd33b670201e4027054859fc9066ef688a7c3257b645eff963519c
log-VM-windows-2025-4
4.42 KB
sha256:902d7e50f8473a3233f0d3a6ac0f5bc3bae6cf812df9ca1dfee2bbe68024d489
log-VM-windows-2025-5
566 Bytes
sha256:eab4cbe8e4b8227139d64bdc7f8f214fe023fd125c88597009b988941ca8d374
log-VM-windows-2025-6
515 Bytes
sha256:083fa1cfc4ceb6c7628c0a19aa06afb84e97aa22ca874f1bc97e348c65b19c02
log-VM-windows-2025-7
481 Bytes
sha256:39e8ebab3f84ad1826c5441101869dadfa0e5017f3df710f2ee85d29bb659427
logs-choco-windows-2022-0
314 KB
sha256:2bab6231ff160ed13ca3ee83d93bb169d2104902dbfc40de534c400c68cd1c51
logs-choco-windows-2022-1
84.5 KB
sha256:8b235856a454d97ce438bad9735d09cefdd5b99ad8f9eff545d3b154082149b2
logs-choco-windows-2022-2
744 KB
sha256:88fb0115c4150147fb909e46216729210b1f0959f58d30741e4ce34c55d54bb3
logs-choco-windows-2022-3
669 KB
sha256:6e5430b61e625fc3b42efd512f3b6eddffe7c6cc3fd11bc0d0045739f4fd7371
logs-choco-windows-2025-4
309 KB
sha256:3500c0b90b2c610f78c3945c74fff2da0341d6bbfbbeee76e39024cc561010d1
logs-choco-windows-2025-5
22.6 KB
sha256:4a6bf617636f1d5b80c7328a92c0d191e6f5acfd82618006bd8c150560106126
logs-choco-windows-2025-6
715 KB
sha256:051cd31d81495e345cf15577dd249d7154f1db8bba1971a92b831c650fe2bead
logs-choco-windows-2025-7
704 KB
sha256:fe0c1a4c5b396d2ca6fc8037066e9c61f9f3e05ad1d71e0a973c19ff530529a0
success_failure_Win10_0
220 Bytes
sha256:d1939fc5ef41397784d1ae762a489af543d16d9d4079f790ed7f66480891d54c
success_failure_Win10_1
267 Bytes
sha256:f8ff024600d381a8d5304aa09eabaf9485243ee62fcc72e7ad5a316195cbe79e
success_failure_Win10_2
258 Bytes
sha256:fc9d143db98d5730e12656530c4d968f3f0faf19b5c5d403e64e10572d240857
success_failure_Win10_3
203 Bytes
sha256:519ef94b3a1d8bd9e9e7df06ce0d698d5b51529d9118c17121e5ea220d8eb7db
success_failure_Win11_4
203 Bytes
sha256:8af104960efea1c352b1bff5e6751dd07e480eaf0f6c307b488d98f975f0d45e
success_failure_Win11_5
225 Bytes
sha256:5d0687f6a69409ea68b2f9db5c024fe5bf497f410d84c269cbbee107204ae383
success_failure_Win11_6
206 Bytes
sha256:21228c27fff47c823bc51ba19a36d9bf8e10671cc6b7c84fdd2896ebbd0f0303
success_failure_Win11_7
203 Bytes
sha256:14f9e296cab59ed763267c51162d5301107b5dca69281e7caad708da718f3019