Skip to content

CI

CI #6578

Triggered via schedule January 4, 2025 04:48
Status Success
Total duration 5m 33s
Artifacts 6

build.yml

on: schedule
Matrix: Build Linux
Build Windows 2019
3m 59s
Build Windows 2019
Build Mac (for Intel)
2m 6s
Build Mac (for Intel)
Build Mac (universal build)
1m 45s
Build Mac (universal build)
Build Linux with -DFLATBUFFERS_NO_FILE_TESTS
2m 8s
Build Linux with -DFLATBUFFERS_NO_FILE_TESTS
Build Linux with out-of-source build location
1m 9s
Build Linux with out-of-source build location
Build Android (on Linux)
3m 47s
Build Android (on Linux)
Check Generated Code on Windows
3m 33s
Check Generated Code on Windows
Build Java
14s
Build Java
Build Kotlin MacOS
5m 20s
Build Kotlin MacOS
Build Kotlin Linux
2m 41s
Build Kotlin Linux
Build Rust Linux
1m 55s
Build Rust Linux
Build Rust Windows
1m 23s
Build Rust Windows
Build Python
53s
Build Python
Build Go
1m 15s
Build Go
Build PHP
59s
Build PHP
Build Swift Wasm
3m 13s
Build Swift Wasm
Build TS
1m 18s
Build TS
Build Dart
1m 21s
Build Dart
Build Nim
1m 13s
Build Nim
Matrix: Build Benchmarks (on Linux)
Matrix: Build Windows C++
Matrix: Build .NET Windows
Matrix: Check Generated Code
Matrix: Build Linux C++
Matrix: Build Swift
release-digests
0s
release-digests
provenance  /  detect-env
provenance / detect-env
provenance  /  privacy-check
provenance / privacy-check
provenance  /  generator
provenance / generator
provenance  /  create-release
provenance / create-release
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Build .NET Windows
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
Build .NET Windows
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
Build .NET Windows (-p:UnsafeByteBuffer=true)
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
Build .NET Windows (-p:UnsafeByteBuffer=true)
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.

Artifacts

Produced during runtime
Name Size
Linux flatbenchmark results g++-13
775 Bytes
Linux flatc binary clang++-18
2.63 MB
Linux flatc binary g++-13
2.43 MB
Mac flatc binary Intel
1.39 MB
Mac flatc binary Universal
2.68 MB
Windows flatc binary
1.36 MB