Skip to content
continuous build

fix symbol naming (underscoring) #6080

Sign in to view logs

fix symbol naming (underscoring)

fix symbol naming (underscoring) #6080

Triggered via push September 21, 2025 17:01
@martin-frbgmartin-frbg
pushed fc042d9
gemm_batch
Status Success
Total duration 1h 41m 12s
Artifacts –

dynamic_arch.yml

on: push
neoverse_build
7m 51s
neoverse_build
Matrix: build
Matrix: cross_build
Matrix: msys2
Fit to window
Zoom out
Zoom in

Annotations

6 notices
msys2 (UCRT64, int32, None, mingw-w64-ucrt-x86_64, fc)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
msys2 (UCRT64, int32, Release)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
msys2 (MINGW32, int32, Release)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
msys2 (UCRT64, int64, Release)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
msys2 (CLANG64, int64, Release)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
msys2 (CLANG64, int32, Release)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677