[Swift] Bug fix for verifier where its being copied #6517
build.yml
on: pull_request
Matrix: Build Linux
Build Windows 2019
4m 25s
Build Mac (for Intel)
1m 42s
Build Mac (universal build)
3m 14s
Build Linux with -DFLATBUFFERS_NO_FILE_TESTS
2m 4s
Build Linux with out-of-source build location
1m 12s
Build Android (on Linux)
3m 28s
Check Generated Code on Windows
4m 18s
Build Java
15s
Build Kotlin MacOS
6s
Build Kotlin Linux
3m 16s
Build Rust Linux
1m 54s
Build Rust Windows
1m 55s
Build Python
1m 7s
Build Go
1m 27s
Build PHP
1m 7s
Build Swift Wasm
3m 26s
Build TS
1m 30s
Build Dart
1m 17s
Build Nim
1m 19s
Matrix: Build Benchmarks (on Linux)
Matrix: Build Windows C++
Matrix: Build .NET Windows
Matrix: Check Generated Code
Matrix: Build Linux C++
Matrix: Build Swift
provenance
/
detect-env
provenance
/
privacy-check
provenance
/
create-release
Annotations
3 errors and 2 warnings
Build Kotlin MacOS
Process completed with exit code 1.
|
Build .NET Windows (-p:UnsafeByteBuffer=true)
Process completed with exit code 1.
|
Build .NET Windows
The job was canceled because "_-p_UnsafeByteBuffer_true" failed.
|
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
|
767 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 |
|