Files
solidcraft/tests/KNOWN_FAILING_TESTS
T
jyvikoandClaude Opus 5.5 a26d3ee41c xtask: known-failing grades a nextest junit report against tests/KNOWN_FAILING_TESTS
`cargo xtask known-failing --junit PATH` reads nextest's junit (a file, or every .xml under a
directory, so all of a run's junit artifacts at once) and fails on a test that failed and the
list does not name, and on a listed test that passed (FIXED: take its line off, as the kernel
rig's gate does). A listed test that did not run is neither, since a pull request tests only the
packages it touches. The list has the rig's KNOWN_FAILING format (`<test> <cause>`, sorted, the
rig's own parser), with `<test>` nextest's `<binary id>::<test name>`; `cargo xtask lists`
checks it is sorted. The list starts empty.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-30 22:20:00 -04:00

11 lines
882 B
Plaintext

# The cargo tests that fail today, one a line: `<test> <why it fails today>`, with the issue that
# tracks it when there is one. Sorted. `<test>` is nextest's `<binary id>::<test name>`, as the
# junit report names it. CI's test jobs (`cargo xtask known-failing`) fail on a test that fails
# and is not listed here, and on a listed test that passes: a fix removes its line in the same
# pull request. The tests stay un-ignored, so every run shows whether they still fail.
# Refresh (after an SMLib pin bump): download the junit artifacts of develop's latest CI run, one
# directory each (`gh run download <run> -R tangency-labs/solidcraft -n <artifact> -D <dir>/<artifact>`
# for junit and junit-gpu-1..4), run `cargo xtask known-failing --junit <dir>`, then drop each
# FIXED line and add each REGRESSION line with its cause, from the test's failure message.
# Baseline: none yet.