Skip to content
build-windows-QT5

move zapm.cpp to dedicated folder as it's not our code #18

Sign in to view logs

move zapm.cpp to dedicated folder as it's not our code

move zapm.cpp to dedicated folder as it's not our code #18

Triggered via pull request August 17, 2025 14:54
@atsjuatsju
reopened #227
atsju:JST/moveZernike
Status Success
Total duration 9m 44s
Artifacts 1

build-windows-QT5.yml

on: pull_request
cache-mingw-from-QT
9s
cache-mingw-from-QT
build-openCV-with-QT
10s
build-openCV-with-QT
build-QWT
7s
build-QWT
build-lapack-armadillo
4s
build-lapack-armadillo
build-DFTFringe
9m 16s
build-DFTFringe
Fit to window
Zoom out
Zoom in

Annotations

5 notices
cache-mingw-from-QT
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
build-lapack-armadillo
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
build-QWT
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
build-openCV-with-QT
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
build-DFTFringe
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

Artifacts

Produced during runtime
Name Size Digest
DFTFringe-windows-build-artifact-QT5 Expired
114 MB
sha256:88b38bbdba1b94e15eb5779ff9cbb8693f87f0f92f3725206bc6f2b5c46161b7