Skip to content

[Swift] Migrating benchmarks to a newer lib. #5770

[Swift] Migrating benchmarks to a newer lib.

[Swift] Migrating benchmarks to a newer lib. #5770

Triggered via pull request November 21, 2023 17:44
Status Success
Total duration 6m 46s
Artifacts 5

build.yml

on: pull_request
Matrix: Build Linux
Build Windows 2019
3m 35s
Build Windows 2019
Build Mac (for Intel)
2m 44s
Build Mac (for Intel)
Build Mac (universal build)
4m 57s
Build Mac (universal build)
Build Linux with -DFLATBUFFERS_NO_FILE_TESTS
57s
Build Linux with -DFLATBUFFERS_NO_FILE_TESTS
Build Linux with out-of-source build location
38s
Build Linux with out-of-source build location
Build Windows 2017
3m 15s
Build Windows 2017
Build Windows 2015
3m 48s
Build Windows 2015
Build Android (on Linux)
3m 51s
Build Android (on Linux)
Check Generated Code on Windows
4m 20s
Check Generated Code on Windows
Build Java
31s
Build Java
Build Kotlin MacOS
5m 59s
Build Kotlin MacOS
Build Kotlin Linux
2m 35s
Build Kotlin Linux
Build Rust Linux
1m 1s
Build Rust Linux
Build Rust Windows
1m 3s
Build Rust Windows
Build Python
18s
Build Python
Build Go
43s
Build Go
Build PHP
19s
Build PHP
Build Swift
1m 2s
Build Swift
Build Swift Wasm
1m 16s
Build Swift Wasm
Build TS
43s
Build TS
Build Dart
48s
Build Dart
Build Nim
33s
Build Nim
Matrix: Build Benchmarks (on Linux)
Matrix: Build Windows C++
Matrix: Build .NET Windows
Matrix: Check Generated Code
Matrix: Build Linux 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

5 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 .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 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.24 KB
Linux flatc binary clang++-15 Expired
7.01 MB
Linux flatc binary g++-13 Expired
6.37 MB
Mac flatc binary Expired
6.58 MB
Windows flatc binary Expired
3.33 MB