Skip to content

Update build.yml

Update build.yml #5722

Triggered via pull request November 18, 2023 21:42
Status Success
Total duration 5m 58s
Artifacts 5

build.yml

on: pull_request
Matrix: Build Linux
Build Windows 2019
4m 30s
Build Windows 2019
Build Mac (for Intel)
2m 55s
Build Mac (for Intel)
Build Mac (universal build)
3m 56s
Build Mac (universal build)
Build Linux with -DFLATBUFFERS_NO_FILE_TESTS
1m 54s
Build Linux with -DFLATBUFFERS_NO_FILE_TESTS
Build Linux with out-of-source build location
1m 2s
Build Linux with out-of-source build location
Build Windows 2017
4m 8s
Build Windows 2017
Build Windows 2015
3m 41s
Build Windows 2015
Build Android (on Linux)
3m 16s
Build Android (on Linux)
Check Generated Code on Windows
3m 42s
Check Generated Code on Windows
Build Java
18s
Build Java
Build Kotlin MacOS
4m 16s
Build Kotlin MacOS
Build Kotlin Linux
3m 2s
Build Kotlin Linux
Build Rust Linux
1m 50s
Build Rust Linux
Build Rust Windows
1m 50s
Build Rust Windows
Build Python
1m 0s
Build Python
Build Go
1m 22s
Build Go
Build PHP
1m 2s
Build PHP
Build Swift
2m 4s
Build Swift
Build Swift Wasm
1m 30s
Build Swift Wasm
Build TS
1m 22s
Build TS
Build Dart
1m 22s
Build Dart
Build Nim
1m 7s
Build Nim
Matrix: Build Benchmarks (on Linux)
Matrix: Build .NET Windows
Matrix: Check Generated Code
Matrix: Build Linux C++
Matrix: Build Windows C++
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

3 warnings
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.
Build Swift Wasm
The following actions uses node12 which is deprecated and will be forced to run on node16: wasmerio/setup-wasmer@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Artifacts

Produced during runtime
Name Size
Linux flatbenchmark results g++-13 Expired
4.23 KB
Linux flatc binary clang++-15 Expired
7.01 MB
Linux flatc binary g++-13 Expired
6.38 MB
Mac flatc binary Expired
6.58 MB
Windows flatc binary Expired
3.32 MB