Skip to content

fix: path issues for qt #282

fix: path issues for qt

fix: path issues for qt #282

Triggered via push November 1, 2024 11:19
Status Failure
Total duration 3m 16s
Artifacts

ci.yml

on: push
Matrix: tests
💎 CLang-Format
11s
💎 CLang-Format
💎 CMake-Format
21s
💎 CMake-Format
Matrix: build
🐧 Build flatpak on ubuntu-latest
0s
🐧 Build flatpak on ubuntu-latest
🐧 Build snap on ubuntu-20.04
0s
🐧 Build snap on ubuntu-20.04
release-all-green
3s
release-all-green
🗂 Create release and upload artifacts
0s
🗂 Create release and upload artifacts
changeLog
0s
changeLog
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
tests (ubuntu-22.04, Ninja, g++-10, gcc-10, Debug, 6.7.2)
Process completed with exit code 1.
tests (ubuntu-latest, Ninja, g++-10, gcc-10, Debug, 6.7.2)
Process completed with exit code 1.
release-all-green
Process completed with exit code 1.
tests (ubuntu-22.04, Ninja, g++-10, gcc-10, Debug, 6.7.2)
The following actions use a deprecated Node.js version and will be forced to run on node20: pat-s/always-upload-cache@9a0d1c3e1a8260b05500f9b67a5be8f2a1299819. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
tests (ubuntu-latest, Ninja, g++-10, gcc-10, Debug, 6.7.2)
The following actions use a deprecated Node.js version and will be forced to run on node20: pat-s/always-upload-cache@9a0d1c3e1a8260b05500f9b67a5be8f2a1299819. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/