CI #6494

Sign in to view logs

Triggered via schedule November 28, 2024 04:49

master

Status Failure

Total duration 6m 2s

Artifacts 6

build.yml

on: schedule

Matrix: Build Linux

Build Windows 2019

Build Mac (for Intel)

Build Mac (universal build)

Build Linux with -DFLATBUFFERS_NO_FILE_TESTS

Build Linux with out-of-source build location

Build Android (on Linux)

Check Generated Code on Windows

Build Kotlin MacOS

Build Kotlin Linux

Build Rust Linux

Build Rust Windows

Build Swift Wasm

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

provenance / detect-env

provenance / privacy-check

provenance / generator

provenance / create-release

Annotations

4 errors and 4 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

Process completed with exit code 1.

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.

Artifacts

Produced during runtime

Name	Size
Linux flatbenchmark results g++-13	734 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