CI

[Swift] Add allowReadingUnalignedBuffers to most ByteBuffer init methods #5751

Sign in to view logs

Re-run triggered November 20, 2023 13:11

#8134

abandy:8133

Status Success

Total duration 9m 12s

Artifacts 5

This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

build.yml

on: pull_request

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 Windows 2017

Build Windows 2015

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++

release-digests

provenance / detect-env

provenance / privacy-check

provenance / generator

provenance / create-release

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	3.4 MB
Windows flatc binary Expired	3.33 MB