Skip to content

Update MID1_Generate_Warlock.simc (#11269) #32344

Update MID1_Generate_Warlock.simc (#11269)

Update MID1_Generate_Warlock.simc (#11269) #32344

Triggered via push April 8, 2026 03:43
Status Success
Total duration 21m 47s
Artifacts

main.yml

on: push
Matrix: build / ubuntu-clang-build
Matrix: build / ubuntu-gcc-build
Matrix: build / windows-VS
spec-test-selection
13s
spec-test-selection
environment-configuration-info
3s
environment-configuration-info
Matrix: ubuntu-test / ubuntu-test
Matrix: spec-test / spec-test
Matrix: spec-test-ptr / spec-test
update-generated-files  /  update-generated-files
1m 38s
update-generated-files / update-generated-files
Fit to window
Zoom out
Zoom in

Annotations

51 errors and 3 warnings
spec-test-ptr / spec-test-deathknight_unholy
Process completed with exit code 30.
spec-test-ptr / spec-test-deathknight_unholy
Process completed with exit code 30.
spec-test-ptr / spec-test-deathknight_unholy
Process completed with exit code 30.
spec-test-ptr / spec-test-deathknight_unholy
Process completed with exit code 30.
spec-test-ptr / spec-test-deathknight_unholy
Process completed with exit code 30.
spec-test-ptr / spec-test-deathknight_unholy
Process completed with exit code 30.
spec-test-ptr / spec-test-deathknight_unholy
Process completed with exit code 30.
spec-test-ptr / spec-test-deathknight_unholy
Process completed with exit code 30.
spec-test-ptr / spec-test-deathknight_unholy
Process completed with exit code 30.
spec-test-ptr / spec-test-deathknight_unholy
Process completed with exit code 30.
spec-test-ptr / spec-test-deathknight_unholy
Process completed with exit code 30.
spec-test-ptr / spec-test-deathknight_unholy
Process completed with exit code 30.
spec-test-ptr / spec-test-deathknight_unholy
Process completed with exit code 30.
spec-test-ptr / spec-test-deathknight_frost
Process completed with exit code 134.
spec-test-ptr / spec-test-deathknight_frost
Process completed with exit code 134.
spec-test-ptr / spec-test-deathknight_frost
Process completed with exit code 134.
spec-test-ptr / spec-test-deathknight_frost
Process completed with exit code 134.
spec-test-ptr / spec-test-deathknight_frost
Process completed with exit code 134.
spec-test-ptr / spec-test-deathknight_frost
Process completed with exit code 134.
spec-test-ptr / spec-test-deathknight_frost
Process completed with exit code 134.
spec-test-ptr / spec-test-deathknight_frost
Process completed with exit code 134.
spec-test-ptr / spec-test-deathknight_blood
Process completed with exit code 134.
spec-test-ptr / spec-test-deathknight_blood
Process completed with exit code 134.
spec-test-ptr / spec-test-deathknight_blood
Process completed with exit code 134.
spec-test-ptr / spec-test-deathknight_blood
Process completed with exit code 134.
spec-test-ptr / spec-test-deathknight_blood
Process completed with exit code 134.
spec-test-ptr / spec-test-deathknight_blood
Process completed with exit code 134.
spec-test-ptr / spec-test-deathknight_blood
Process completed with exit code 134.
spec-test-ptr / spec-test-deathknight_blood
Process completed with exit code 134.
spec-test-ptr / spec-test-evoker_augmentation
Process completed with exit code 30.
spec-test-ptr / spec-test-evoker_augmentation
Process completed with exit code 30.
spec-test-ptr / spec-test-evoker_augmentation
Process completed with exit code 30.
spec-test-ptr / spec-test-evoker_augmentation
Process completed with exit code 30.
spec-test-ptr / spec-test-evoker_augmentation
Process completed with exit code 30.
spec-test-ptr / spec-test-evoker_augmentation
Process completed with exit code 30.
spec-test-ptr / spec-test-evoker_augmentation
Process completed with exit code 30.
spec-test-ptr / spec-test-evoker_augmentation
Process completed with exit code 30.
spec-test-ptr / spec-test-evoker_augmentation
Process completed with exit code 30.
spec-test-ptr / spec-test-evoker_augmentation
Process completed with exit code 30.
spec-test-ptr / spec-test-evoker_augmentation
Process completed with exit code 30.
spec-test-ptr / spec-test-evoker_augmentation
Process completed with exit code 30.
spec-test-ptr / spec-test-hunter_marksmanship
Process completed with exit code 134.
spec-test-ptr / spec-test-hunter_marksmanship
Process completed with exit code 134.
spec-test-ptr / spec-test-hunter_marksmanship
Process completed with exit code 134.
spec-test-ptr / spec-test-hunter_marksmanship
Process completed with exit code 134.
spec-test-ptr / spec-test-hunter_marksmanship
Process completed with exit code 134.
spec-test-ptr / spec-test-hunter_marksmanship
Process completed with exit code 134.
spec-test-ptr / spec-test-hunter_marksmanship
Process completed with exit code 134.
spec-test-ptr / spec-test-hunter_marksmanship
Process completed with exit code 134.
spec-test-ptr / spec-test-hunter_marksmanship
Process completed with exit code 134.
spec-test-ptr / spec-test-hunter_marksmanship
Process completed with exit code 134.
build / windows-VS-amd64_arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
build / windows-VS-x64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
update-generated-files / update-generated-files
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, EndBug/add-and-commit@v9, geekyeggo/delete-artifact@v5. 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/