Recordspypipygmentsfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×2
============================= test session starts ============================= · platform win32 -- Python 3.13.14, pytest-9.1.1, pluggy-1.6.0 -- <path> …
Evidence quality: complete · pytest · unclassified-diagnostic · gap stage-unknown · First recorded: 2026-09-01 · Last seen: 2026-09-01
sha256:d52af8ea6f8b…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- os=windows · runtime=python@3.10 ×2 2026-09-01 → 2026-09-01
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- pygments 2.20.0: highlight python code to html with pygments This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWpygments.formatters.HtmlFormatterpygments.highlightpygments.lexers.get_lexer_by_name MIT-0 · 2026-08-27