Skip to content

CI

CI #303

Triggered via schedule May 12, 2026 07:29
Status Failure
Total duration 1d 0h 0m 3s
Artifacts 6

build.yml

on: schedule
Matrix: Build Linux
Build Windows 2022
4m 28s
Build Windows 2022
Build Mac (for Intel)
2m 55s
Build Mac (for Intel)
Build Mac (universal build)
4m 24s
Build Mac (universal build)
Build Linux with -DFLATBUFFERS_NO_FILE_TESTS
2m 0s
Build Linux with -DFLATBUFFERS_NO_FILE_TESTS
Build Linux with out-of-source build location
1m 19s
Build Linux with out-of-source build location
Build Android (on Linux)
0s
Build Android (on Linux)
Check Generated Code on Windows
4m 39s
Check Generated Code on Windows
Build Java
24s
Build Java
Build Kotlin MacOS
2m 15s
Build Kotlin MacOS
Build Kotlin Linux
0s
Build Kotlin Linux
Build Rust Linux
1m 57s
Build Rust Linux
Build Rust Windows
1d 0h
Build Rust Windows
Build Python
57s
Build Python
Build Go
1m 31s
Build Go
Build PHP
55s
Build PHP
Test swift windows
2m 2s
Test swift windows
Test Swift Wasm
1m 29s
Test Swift Wasm
Build TS
1m 16s
Build TS
Build Dart
1m 13s
Build Dart
Build Nim
1m 3s
Build Nim
Bazel
1m 42s
Bazel
Matrix: Build Benchmarks (on Linux)
Matrix: Build Windows C++
Matrix: Build .NET Windows
Matrix: Check Generated Code
Matrix: Build Linux C++
Matrix: Test Swift Linux
release-digests
0s
release-digests
provenance  /  detect-env
provenance / detect-env
provenance  /  generator
provenance / generator
provenance  /  upload-assets
provenance / upload-assets
provenance  /  final
provenance / final
Fit to window
Zoom out
Zoom in

Annotations

5 errors, 11 warnings, and 1 notice
Build TS
Process completed with exit code 1.
Build .NET Windows (-p:UnsafeByteBuffer=true)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Build Rust Windows
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Build .NET Windows (-p:EnableSpanT=true,UnsafeByteBuffer=true)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Build .NET Windows
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Test Swift Wasm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: swift-actions/setup-swift@v2. 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 Swift Linux (6.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: swift-actions/setup-swift@v2. 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 Swift Linux (6.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: swift-actions/setup-swift@v2. 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 2022
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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 C++ (11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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/
Check Generated Code on Windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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 C++ (14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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 Swift Linux (5.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: swift-actions/setup-swift@v2. 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 C++ (17)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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 C++ (23)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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 C++ (20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@v2. 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 swift windows
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

Artifacts

Produced during runtime
Name Size Digest
Linux flatbenchmark results g++-13
751 Bytes
sha256:e70eca5c9659afb3af82cf4ef4d62e8a315a948e44e7898b6fb53a0aa918a6fa
Linux flatc binary clang++-18
2.68 MB
sha256:223b01ad46bfc51992fac26a2548a692269c9775eb2edde4584131ed3c044661
Linux flatc binary g++-13
2.46 MB
sha256:4085792cf0d077d0de479c278881708de746bfea854b9843b40d31de765a8488
Mac flatc binary Intel
1.4 MB
sha256:c62475570c451b67cb22fbaf829bd8bd52f69dbfcf3282b09839b41b0075c381
Mac flatc binary Universal
2.69 MB
sha256:844493389afc8c6da550d7dc5ae1bbfac5dd799935d370073d8be1f89915cb5f
Windows flatc binary
1.38 MB
sha256:1e1d2eab4f7a26c53dfc188e9b871fe187355a711ef5553c552673f8fe65e0d0