Fix crash for TypeScript enum in substruct #6589
build.yml
on: pull_request
Matrix: Build Linux
Build Windows 2019
3m 54s
Build Mac (for Intel)
1m 29s
Build Mac (universal build)
1m 43s
Build Linux with -DFLATBUFFERS_NO_FILE_TESTS
1m 59s
Build Linux with out-of-source build location
1m 18s
Build Android (on Linux)
4m 5s
Check Generated Code on Windows
3m 37s
Build Java
27s
Build Kotlin MacOS
7m 23s
Build Kotlin Linux
3m 11s
Build Rust Linux
2m 2s
Build Rust Windows
1m 33s
Build Python
56s
Build Go
1m 18s
Build PHP
55s
Build Swift Wasm
3m 18s
Build TS
1m 16s
Build Dart
1m 12s
Build Nim
1m 14s
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
5 errors and 4 warnings
Build Swift (5.9)
The job was canceled because "_5_8" failed.
|
Build Swift (5.9)
The operation was canceled.
|
Build Swift (5.8)
Unexpected error, unable to continue. Please report at https://github.com/swift-actions/setup-swift/issues
The process '/usr/bin/gpg' failed with exit code 2
Stacktrace:
Error: The process '/usr/bin/gpg' failed with exit code 2
at ExecState._setResult (/home/runner/work/_actions/swift-actions/setup-swift/v2/dist/index.js:3191:25)
at ExecState.CheckComplete (/home/runner/work/_actions/swift-actions/setup-swift/v2/dist/index.js:3174:18)
at ChildProcess.<anonymous> (/home/runner/work/_actions/swift-actions/setup-swift/v2/dist/index.js:3068:27)
at ChildProcess.emit (node:events:519:28)
at maybeClose (node:internal/child_process:1105:16)
at ChildProcess._handle.onexit (node:internal/child_process:305:5)
|
Build Swift (5.10)
The job was canceled because "_5_8" failed.
|
Build Swift (5.10)
The operation was canceled.
|
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.
|