Skip to content
ci

Use relative submodule paths to facilitate forking. #477

Sign in to view logs

Use relative submodule paths to facilitate forking.

Use relative submodule paths to facilitate forking. #477

Re-run triggered June 4, 2025 14:40
@igagisigagis
#25
zapolnov:nz_submodules
Status Failure
Total duration 1h 8m 8s
Artifacts –

ci.yml

on: pull_request
macosx
9s
macosx
msvs
6m 49s
msvs
Matrix: conan-linux
Matrix: conan-macosx
Matrix: deb_linux
Matrix: msys2
Matrix: sanitizer
Matrix: vcpkg
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 2 warnings
sanitizer - arm64v8/debian:bookworm
Process completed with exit code 128.
sanitizer - arm32v7/debian:bookworm
Process completed with exit code 128.
linux - ubuntu:noble
Process completed with exit code 128.
vcpkg - linux |
Process completed with exit code 128.
msys2 - mingw32
Process completed with exit code 128.
msys2 - mingw64
Process completed with exit code 128.
linux - debian:bookworm
Process completed with exit code 128.
linux - arm32v7/debian:bookworm
Process completed with exit code 128.
conan - macos-latest
Process completed with exit code 128.
sanitizer - debian:bookworm
Process completed with exit code 128.
linux - arm64v8/debian:bookworm
Process completed with exit code 128.
msvs
❌ Failed to create checks using the provided token. (HttpError: Resource not accessible by integration)
macosx
Process completed with exit code 128.
conan - linux |
Process completed with exit code 128.
vcpkg - linux |
No files were found with the provided path: vcpkg-installation/buildtrees/tst/ build/vcpkg/**/*.log. No artifacts will be uploaded.
msvs
⚠️ This usually indicates insufficient permissions. More details: https://github.com/mikepenz/action-junit-report/issues/23