Skip to content

fix: better logging on why something fails/passes file check (#1250) #3546

fix: better logging on why something fails/passes file check (#1250)

fix: better logging on why something fails/passes file check (#1250) #3546

Triggered via push March 5, 2026 05:53
Status Success
Total duration 20m 58s
Artifacts 3

ci.yml

on: push
Matrix: checks
Matrix: docs
Matrix: min
Format
1m 58s
Format
Tests on 🐍 3.9 • cygwin
3m 3s
Tests on 🐍 3.9 • cygwin
Distribution build
23s
Distribution build
Manylinux on 🐍 3.13 • Free-threaded
9m 56s
Manylinux on 🐍 3.13 • Free-threaded
Tests on 🐍 3 • msys UCRT
13m 17s
Tests on 🐍 3 • msys UCRT
Tests on 🐍 3 • mingw64
13m 4s
Tests on 🐍 3 • mingw64
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
🐍 3.8 • CMake 3.21.x on macos-latest
[notice] A new release of pip is available: 21.1.1 -> 25.0.1 [notice] To update, run: python3.8 -m pip install --upgrade pip
Tests on 🐍 3.9 • cygwin
The process 'D:\cygwin\bin\git.exe' failed with exit code 128

Artifacts

Produced during runtime
Name Size Digest
Package Metadata Expired
6.13 KB
sha256:f84fa3f4b69679c22ae9aa4bfa20ff1152b6a1849e510ca2f7c22ac70c5f7d2d
Packages Expired
475 KB
sha256:e0ecc3ceb4e23da23a8734d2c56e86077abef8334312eb8a040f584d5adb2388
PyPI README Expired
5.47 KB
sha256:f3e0e7761075526b14778e7fd729f5fc48038949716392a90c238910244c8796