Auto-update symbols for Windows DF version 53.12 #2331
DFHack-Uristbuild.yml
on: push
Matrix: test / build-linux
test
/
...
/
Build win64
26m 37s
validate
26s
docs
/
Build linux64
1m 21s
test
/
...
/
Test (ubuntu, gcc-11, default plugins, default config)
1m 8s
test
/
...
/
Test (ubuntu, gcc-12, all plugins, default config)
1m 19s
test
/
...
/
Test (windows, msvc, default plugins, default config)
2m 34s
test
/
...
/
Test (windows, msvc, default plugins, empty config)
3m 18s
Annotations
4 errors and 17 warnings
|
test / Run Linux test suite / Test (ubuntu, gcc-11, default plugins, default config)
Final attempt failed. Child_process exited with error code 2
|
|
test / Run Linux test suite (gcc-12, all plugins) / Test (ubuntu, gcc-12, all plugins, default config)
Final attempt failed. Child_process exited with error code 2
|
|
test / Run Windows test suite / Test (windows, msvc, default plugins, default config)
Final attempt failed. Child_process exited with error code 1
|
|
test / Run Windows test suite (empty config) / Test (windows, msvc, default plugins, empty config)
Final attempt failed. Child_process exited with error code 1
|
|
validate
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/
|
|
docs / Build linux64
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/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 / Linux gcc-11 / Build linux64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/checkout@v4, 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 / Linux gcc-12 / Build linux64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/checkout@v4, 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 / Run Linux test suite / Test (ubuntu, gcc-11, default plugins, default config)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4, nick-fields/retry@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 / Run Linux test suite / Test (ubuntu, gcc-11, default plugins, default config)
Attempt 2 failed. Reason: Child_process exited with error code 2
|
|
test / Run Linux test suite / Test (ubuntu, gcc-11, default plugins, default config)
Attempt 1 failed. Reason: Child_process exited with error code 2
|
|
test / Run Linux test suite (gcc-12, all plugins) / Test (ubuntu, gcc-12, all plugins, default config)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4, nick-fields/retry@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 / Run Linux test suite (gcc-12, all plugins) / Test (ubuntu, gcc-12, all plugins, default config)
Attempt 2 failed. Reason: Child_process exited with error code 2
|
|
test / Run Linux test suite (gcc-12, all plugins) / Test (ubuntu, gcc-12, all plugins, default config)
Attempt 1 failed. Reason: Child_process exited with error code 2
|
|
test / Windows MSVC / Build win64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/checkout@v4, actions/upload-artifact@v4, ilammy/msvc-dev-cmd@v1. 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 / Run Windows test suite / Test (windows, msvc, default plugins, default config)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4, nick-fields/retry@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 / Run Windows test suite / Test (windows, msvc, default plugins, default config)
Attempt 2 failed. Reason: Child_process exited with error code 1
|
|
test / Run Windows test suite / Test (windows, msvc, default plugins, default config)
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
test / Run Windows test suite (empty config) / Test (windows, msvc, default plugins, empty config)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4, nick-fields/retry@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 / Run Windows test suite (empty config) / Test (windows, msvc, default plugins, empty config)
Attempt 2 failed. Reason: Child_process exited with error code 1
|
|
test / Run Windows test suite (empty config) / Test (windows, msvc, default plugins, empty config)
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
docs
|
2.44 MB |
sha256:5c3794eaf1b5356a58e2878fde4236d39df334ae10a42cd27a63d0ac26b54380
|
|
|
test-gcc-11
|
11 MB |
sha256:ac87ea5afb33c94b045971483d305ebce7dec74edbc068f38ba819002222ad2f
|
|
|
test-gcc-12
|
21.1 MB |
sha256:3dec7eaae17cb648b66f23298802894484f3e189bf69918e0e8dba40ac1ec7d3
|
|
|
test-msvc
|
8.03 MB |
sha256:7fd1ad4322bca23492e5931f937d753852104ec1859845bc332330ad1907ab34
|
|
|
test-output-gcc-11-default_plugins-default_config
|
1.75 KB |
sha256:e09feb1ecf34c60dbfeb6ae4ccdda89d895532c18baf4d36af7dfd4538703d2b
|
|
|
test-output-gcc-12-all_plugins-default_config
|
1.75 KB |
sha256:cc2d4d27a51412fe5c06148746e9262727e8ff6c227aa3dfca7102d68195d3a7
|
|
|
test-output-msvc-default_plugins-default_config
|
46.9 KB |
sha256:35ae9cc852c0245ba9f782f3645b71ce447a3bb0fa8e6fe7ee1cade5cd75e04e
|
|
|
test-output-msvc-default_plugins-empty_config
|
45.9 KB |
sha256:2308a964394af2f51062307a446a4b24061aff574bc0462e3ce249235dbb2424
|
|