Skip to content

CI

CI #507

Triggered via schedule March 30, 2026 05:33
Status Failure
Total duration 19m 56s
Artifacts 6

build.yml

on: schedule
Matrix: Build Linux
Build Windows 2022
17m 8s
Build Windows 2022
Build Mac (for Intel)
18m 5s
Build Mac (for Intel)
Build Mac (universal build)
4m 48s
Build Mac (universal build)
Build Linux with -DFLATBUFFERS_NO_FILE_TESTS
4m 47s
Build Linux with -DFLATBUFFERS_NO_FILE_TESTS
Build Linux with out-of-source build location
5m 37s
Build Linux with out-of-source build location
Build Android (on Linux)
0s
Build Android (on Linux)
Check Generated Code on Windows
17m 35s
Check Generated Code on Windows
Build Java
25s
Build Java
Build Kotlin MacOS
3m 16s
Build Kotlin MacOS
Build Kotlin Linux
3m 50s
Build Kotlin Linux
Build Rust Linux
1m 52s
Build Rust Linux
Build Rust Windows
2m 5s
Build Rust Windows
Build Python
3m 13s
Build Python
Build Go
4m 2s
Build Go
Build PHP
3m 19s
Build PHP
Test swift windows
0s
Test swift windows
Test Swift Wasm
1m 33s
Test Swift Wasm
Build TS
3m 19s
Build TS
Build Dart
3m 32s
Build Dart
Build Nim
3m 18s
Build Nim
Bazel
1m 57s
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
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

71 errors and 31 warnings
Build TS
Process completed with exit code 1.
Build Windows C++ (11)
Use of uninitialized value in join or string
Build Windows C++ (11)
Use of uninitialized value in join or string
Build Windows C++ (11)
Use of uninitialized value in join or string
Build Windows C++ (11)
Use of uninitialized value in join or string
Build Windows C++ (11)
=> Use of uninitialized value in concatenation (.) or string
Build Windows C++ (11)
DEBUG: LIBDIR = Use of uninitialized value in print
Build Windows C++ (11)
DEBUG: libdir = => Use of uninitialized value in concatenation (.) or string
Build Windows C++ (11)
Use of uninitialized value in concatenation (.) or string
Build Windows C++ (11)
DEBUG: LIBDIR = , libdir = => Use of uninitialized value in concatenation (.) or string
Build Windows C++ (11)
Use of uninitialized value in concatenation (.) or string
Build Windows C++ (17)
Use of uninitialized value in join or string
Build Windows C++ (17)
Use of uninitialized value in join or string
Build Windows C++ (17)
Use of uninitialized value in join or string
Build Windows C++ (17)
Use of uninitialized value in join or string
Build Windows C++ (17)
=> Use of uninitialized value in concatenation (.) or string
Build Windows C++ (17)
DEBUG: LIBDIR = Use of uninitialized value in print
Build Windows C++ (17)
DEBUG: libdir = => Use of uninitialized value in concatenation (.) or string
Build Windows C++ (17)
Use of uninitialized value in concatenation (.) or string
Build Windows C++ (17)
DEBUG: LIBDIR = , libdir = => Use of uninitialized value in concatenation (.) or string
Build Windows C++ (17)
Use of uninitialized value in concatenation (.) or string
Build Windows C++ (14)
Use of uninitialized value in join or string
Build Windows C++ (14)
Use of uninitialized value in join or string
Build Windows C++ (14)
Use of uninitialized value in join or string
Build Windows C++ (14)
Use of uninitialized value in join or string
Build Windows C++ (14)
=> Use of uninitialized value in concatenation (.) or string
Build Windows C++ (14)
DEBUG: LIBDIR = Use of uninitialized value in print
Build Windows C++ (14)
DEBUG: libdir = => Use of uninitialized value in concatenation (.) or string
Build Windows C++ (14)
Use of uninitialized value in concatenation (.) or string
Build Windows C++ (14)
DEBUG: LIBDIR = , libdir = => Use of uninitialized value in concatenation (.) or string
Build Windows C++ (14)
Use of uninitialized value in concatenation (.) or string
Build Windows 2022
Use of uninitialized value in join or string
Build Windows 2022
Use of uninitialized value in join or string
Build Windows 2022
Use of uninitialized value in join or string
Build Windows 2022
Use of uninitialized value in join or string
Build Windows 2022
=> Use of uninitialized value in concatenation (.) or string
Build Windows 2022
DEBUG: LIBDIR = Use of uninitialized value in print
Build Windows 2022
DEBUG: libdir = => Use of uninitialized value in concatenation (.) or string
Build Windows 2022
Use of uninitialized value in concatenation (.) or string
Build Windows 2022
DEBUG: LIBDIR = , libdir = => Use of uninitialized value in concatenation (.) or string
Build Windows 2022
Use of uninitialized value in concatenation (.) or string
Check Generated Code on Windows
Use of uninitialized value in join or string
Check Generated Code on Windows
Use of uninitialized value in join or string
Check Generated Code on Windows
Use of uninitialized value in join or string
Check Generated Code on Windows
Use of uninitialized value in join or string
Check Generated Code on Windows
=> Use of uninitialized value in concatenation (.) or string
Check Generated Code on Windows
DEBUG: LIBDIR = Use of uninitialized value in print
Check Generated Code on Windows
DEBUG: libdir = => Use of uninitialized value in concatenation (.) or string
Check Generated Code on Windows
Use of uninitialized value in concatenation (.) or string
Check Generated Code on Windows
DEBUG: LIBDIR = , libdir = => Use of uninitialized value in concatenation (.) or string
Check Generated Code on Windows
Use of uninitialized value in concatenation (.) or string
Build Windows C++ (23)
Use of uninitialized value in join or string
Build Windows C++ (23)
Use of uninitialized value in join or string
Build Windows C++ (23)
Use of uninitialized value in join or string
Build Windows C++ (23)
Use of uninitialized value in join or string
Build Windows C++ (23)
=> Use of uninitialized value in concatenation (.) or string
Build Windows C++ (23)
DEBUG: LIBDIR = Use of uninitialized value in print
Build Windows C++ (23)
DEBUG: libdir = => Use of uninitialized value in concatenation (.) or string
Build Windows C++ (23)
Use of uninitialized value in concatenation (.) or string
Build Windows C++ (23)
DEBUG: LIBDIR = , libdir = => Use of uninitialized value in concatenation (.) or string
Build Windows C++ (23)
Use of uninitialized value in concatenation (.) or string
Build Windows C++ (20)
Use of uninitialized value in join or string
Build Windows C++ (20)
Use of uninitialized value in join or string
Build Windows C++ (20)
Use of uninitialized value in join or string
Build Windows C++ (20)
Use of uninitialized value in join or string
Build Windows C++ (20)
=> Use of uninitialized value in concatenation (.) or string
Build Windows C++ (20)
DEBUG: LIBDIR = Use of uninitialized value in print
Build Windows C++ (20)
DEBUG: libdir = => Use of uninitialized value in concatenation (.) or string
Build Windows C++ (20)
Use of uninitialized value in concatenation (.) or string
Build Windows C++ (20)
DEBUG: LIBDIR = , libdir = => Use of uninitialized value in concatenation (.) or string
Build Windows C++ (20)
Use of uninitialized value in concatenation (.) or string
Build .NET Windows (-p:EnableSpanT=true,UnsafeByteBuffer=true)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Build .NET Windows (-p:EnableSpanT=true,UnsafeByteBuffer=true)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Build .NET Windows (-p:EnableSpanT=true,UnsafeByteBuffer=true)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Build .NET Windows (-p:EnableSpanT=true,UnsafeByteBuffer=true)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Build .NET Windows (-p:UnsafeByteBuffer=true)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Build .NET Windows (-p:UnsafeByteBuffer=true)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Build .NET Windows (-p:UnsafeByteBuffer=true)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Build .NET Windows (-p:UnsafeByteBuffer=true)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Build .NET Windows
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Build .NET Windows
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Build .NET Windows
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Build .NET Windows
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
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/
Build Dart
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dart-lang/setup-dart@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 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/
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/
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/
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: ilammy/setup-nasm@v1, microsoft/setup-msbuild@v2, shogo82148/actions-setup-perl@v1.33.0. 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)
Cache not found for keys: setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855, setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855-, setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-
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: ilammy/setup-nasm@v1, microsoft/setup-msbuild@v2, shogo82148/actions-setup-perl@v1.33.0. 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)
Cache not found for keys: setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855, setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855-, setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-
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: ilammy/setup-nasm@v1, microsoft/setup-msbuild@v2, shogo82148/actions-setup-perl@v1.33.0. 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)
Cache not found for keys: setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855, setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855-, setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-
Build Windows 2022
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/setup-nasm@v1, microsoft/setup-msbuild@v2, shogo82148/actions-setup-perl@v1.33.0. 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
Cache not found for keys: setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855, setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855-, setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-
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: ilammy/setup-nasm@v1, microsoft/setup-msbuild@v2, shogo82148/actions-setup-perl@v1.33.0. 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
Cache not found for keys: setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855, setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855-, setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-
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: ilammy/setup-nasm@v1, microsoft/setup-msbuild@v2, shogo82148/actions-setup-perl@v1.33.0. 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)
Cache not found for keys: setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855, setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855-, setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-
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: ilammy/setup-nasm@v1, microsoft/setup-msbuild@v2, shogo82148/actions-setup-perl@v1.33.0. 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)
Cache not found for keys: setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855, setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855-, setup-perl-module-cache-v1-5beafc096902fd599704e272c58c0963e1ef347d4a40ef8df0eabe1393e9ecd4-unknown-

Artifacts

Produced during runtime
Name Size Digest
Linux flatbenchmark results g++-13
769 Bytes
sha256:172ace16a33d33c8c4e4132809f05c5837fe0d39e4e6743d1ade06019dda6e95
Linux flatc binary clang++-18
5.01 MB
sha256:54827164056ade3e11cfd98c66a2f9862f06b8f8bc4065f9205e284cf40311c7
Linux flatc binary g++-13
4.84 MB
sha256:32d9a8d1180dfac3404739de35772545f26b4f7a0d37d09f4dd72e1800daf6f2
Mac flatc binary Intel
3.8 MB
sha256:a375548fb3ac3ee2e50a4d3a6e7478ce355cd84dd38137d9034ce83a40c79be3
Mac flatc binary Universal
7.74 MB
sha256:865a5d1655a9f07c60f1a230caa45a5724647476483d32d32a8c61e629789f00
Windows flatc binary
3.17 MB
sha256:c0cbcd5e6a8fac5fee43f13c62de557031e7cbc92fc22bb6a5df6a15ee03afc0