Skip to content

Use the compiler to determine whether or not to enable f16 and f128 #563

Use the compiler to determine whether or not to enable f16 and f128

Use the compiler to determine whether or not to enable f16 and f128 #563

Triggered via pull request June 30, 2025 22:04
Status Failure
Total duration 39m 3s
Artifacts 1
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

main.yaml

on: pull_request
Calculate workflow variables
7s
Calculate workflow variables
Matrix: Benchmarks
Matrix: Build and test
Matrix: extensive
success
3s
success
Fit to window
Zoom out
Zoom in

Annotations

10 errors
Build and test (i586-unknown-linux-gnu, ubuntu-24.04)
Process completed with exit code 101.
Build and test (powerpc64le-unknown-linux-gnu, ubuntu-24.04)
Process completed with exit code 101.
Build and test (powerpc-unknown-linux-gnu, ubuntu-24.04)
Process completed with exit code 101.
Build and test (i686-unknown-linux-gnu, ubuntu-24.04)
Process completed with exit code 101.
Build and test (powerpc64-unknown-linux-gnu, ubuntu-24.04)
Process completed with exit code 101.
Build and test (i686-pc-windows-gnu, windows-2025, nightly-i686-gnu)
Process completed with exit code 101.
Build and test (x86_64-pc-windows-gnu, windows-2025, nightly-x86_64-gnu)
Process completed with exit code 101.
Build and test (i686-pc-windows-msvc, windows-2025, 1)
Process completed with exit code 101.
Build and test (aarch64-apple-darwin, macos-15)
Process completed with exit code 100.
success
Process completed with exit code 1.

Artifacts

Produced during runtime
Name Size Digest
baseline-icount-x86_64-202506302209-77e5d64d12a5 Expired
235 KB
sha256:b36e8d2906aa157e2bc32b269e6c99f4ec501d7cb1d233a59634ea451cc953cb