Skip to content

CI/CD

CI/CD #2526

Triggered via schedule April 24, 2026 01:58
Status Success
Total duration 8m 15s
Artifacts 1

main.yml

on: schedule
Check requirements
21s
Check requirements
Auto-merge dependabot PR
0s
Auto-merge dependabot PR
Matrix: e2e-test
Matrix: integration-test
Run CodeQL analysis
2m 24s
Run CodeQL analysis
Run unit tests
31s
Run unit tests
Check action with dry run
1m 47s
Check action with dry run
Create release
0s
Create release
Publish metadata to GitHub Pages
29s
Publish metadata to GitHub Pages
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 16 warnings
Run unit tests
Failed to update (Legacy) WinSDK Module Map: Error: Request Failed Status Code: '500'
Run unit tests
Request Failed Status Code: '500'
Run unit tests
Request Failed Status Code: '500'
Run unit tests
Request Failed Status Code: '500'
Run unit tests
Request Failed Status Code: '500'
Run unit tests
Request Failed Status Code: '500'
Run unit tests
Failed to update (Legacy) WinSDK Module Map: Error: Request Failed Status Code: '404'
Run unit tests
Request Failed Status Code: '404'
Run unit tests
Request Failed Status Code: '404'
Run unit tests
Request Failed Status Code: '404'
Run unit tests
Procceding with fallback installation approach
Run unit tests
Unable to get installed SDKs due to: "Error: ENOENT: no such file or directory, scandir 'C:/ProgramFiles(x86)/Windows Kits/10/Include'"
Run unit tests
Procceding with fallback installation approach
Run unit tests
Unable to get installed SDKs due to: "Error: ENOENT: no such file or directory, scandir 'C:/ProgramFiles(x86)/Windows Kits/10/Include'"
Run unit tests
Unable to get installed SDKs due to: "Error: ENOENT: no such file or directory, scandir 'C:/ProgramFiles(x86)/Windows Kits/10/Include'"
Run unit tests
Unable to get installed SDKs due to: "Error: ENOENT: no such file or directory, scandir 'C:/ProgramFiles(x86)/Windows Kits/10/Include'"
Run unit tests
Unable to get installed SDKs due to: "Error: ENOENT: no such file or directory, scandir 'C:/ProgramFiles(x86)/Windows Kits/10/Include'"
Run unit tests
Unable to get installed SDKs due to: "Error: ENOENT: no such file or directory, scandir 'C:/ProgramFiles(x86)/Windows Kits/10/Include'"
Run unit tests
Unable to get installed SDKs due to: "Error: ENOENT: no such file or directory, scandir 'C:/ProgramFiles(x86)/Windows Kits/10/Include'"
Run unit tests
Unable to get installed SDKs due to: "Error: ENOENT: no such file or directory, scandir 'C:/ProgramFiles(x86)/Windows Kits/10/Include'"
Integrate Swift https://github.com/swiftwasm/swift/releases/download/swift-wasm-5.10-SNAPSHOT-2024-03-30-a/swift-wasm-5.10-SNAPSHOT-2024-03-30-a-ubuntu22.04_x86_64.tar.gz on ubuntu-22.04 with development true, VS linker , latest modules
No signature at "https:/github.com/swiftwasm/swift/releases/download/swift-wasm-5.10-SNAPSHOT-2024-03-30-a/swift-wasm-5.10-SNAPSHOT-2024-03-30-a-ubuntu22.04_x86_64.tar.gz.sig"
Run CodeQL analysis
User-specified `matrix` input is not an object.
Integrate Swift latest on windows-latest with development false, VS linker true, latest modules true
Skipping modulemap copies: "Error: ENOENT: no such file or directory, access 'C:\hostedtoolcache\windows\swift-6.3.1-RELEASE-windows10\6.3.1\x86_64\Platforms\6.3.1\Windows.platform\Developer\SDKs\Windows.sdk\usr\share\winsdk.modulemap'"
End-to-end test latest Swift on windows-11-arm
No signature at "https:/download.swift.org/swift-6.3.1-release/windows10-arm64/swift-6.3.1-RELEASE/swift-6.3.1-RELEASE-windows10-arm64.exe.sig"
Publish metadata to GitHub Pages
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/

Artifacts

Produced during runtime
Name Size Digest
debug-artifacts Expired
29.3 MB
sha256:ddf0a38f90f7d66e05af19d5071344d08bfd974d61c6c480450c670528f60ead