Skip to content
CI

threading: use correct mutex name in reverse_lock fatal error messages #539

Sign in to view logs

threading: use correct mutex name in reverse_lock fatal error messages

threading: use correct mutex name in reverse_lock fatal error messages #539

Triggered via push July 7, 2025 14:35
@kevkevinpalkevkevinpal
pushed de4eef5
followupOnGtoCS
Status Success
Total duration 1h 42m 28s
Artifacts 1

ci.yml

on: push
Linux->Windows cross, no tests
58m 10s
Linux->Windows cross, no tests
test each commit
0s
test each commit
ASan + LSan + UBSan + integer, no depends, USDT
1h 6m
ASan + LSan + UBSan + integer, no depends, USDT
Matrix: macos-native-arm64
Matrix: windows-native-dll
Windows, test cross-built
44m 9s
Windows, test cross-built
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
macOS 14 native, arm64, fuzz
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
macOS 14 native, arm64, no depends, sqlite only, gui
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!

Artifacts

Produced during runtime
Name Size Digest
x86_64-w64-mingw32-executables-16119934643 Expired
891 MB
sha256:4e219545d04870b92bea47000104238a62b3158fec6ede76f8a314b1baf96e27