jyviko 5bb43bdb13 CI: the test jobs grade their junit against tests/KNOWN_FAILING_TESTS ...

Native Linux tests and the GPU path test shards no longer fail on any failed test: nextest's
"tests failed" exit (100) goes to `cargo xtask known-failing --junit`, which fails on a failure
the list does not name and on a listed test that passes. Any other nextest exit (a build error,
a bad filter) still fails the step at once. The tests skill says to list a failing test with its
cause, in place of ignoring it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-30 22:20:00 -04:00

..

ISSUE_TEMPLATE

Bug template: ask to reproduce on a current build first (#5150) (#5154)

2026-10-26 06:49:42 +00:00

workflows

CI: the test jobs grade their junit against tests/KNOWN_FAILING_TESTS

2026-10-30 22:20:00 -04:00

actionlint.yaml

CI: spread the slowest tests across the test shards (#3646)

2026-10-20 20:41:58 -04:00

FUNDING.yml

Update funding information in FUNDING.yml

2026-10-12 20:26:45 -04:00

pull_request_template.md

CI: duplicate-PR check and a 'Changes a default' line (Refs #6439) (#6442)

2026-10-25 02:28:57 +00:00

release-notes.md

Pages links point at docs.solidcraft.io: Flatpak repository, help and troubleshooting (#1922)

2026-10-17 07:26:28 -04:00