all
Every official matcher, one bundle per ecosystem.
bundlebundle
Install: ci-doctor matchers add official/all
bundles/all.yaml
id: alldescription: Every official matcher, one bundle per ecosystem.include: [python, js, go, rust, jvm, dotnet, ruby, php, c, any, container, iac]
Contains
38 matchers, bundles flattened:
- pytest pytest's `=== FAILURES ===` block, from the first failing test through to the short summary.
- python_traceback An uncaught Python exception. The exception type and message are on the traceback's last line; the frames above show where it was raised.
- python_lint A `file.py:12: error` diagnostic from mypy, ruff, flake8 or pylint.
- jest A jest test failure - the bullet header names the test, and the diff below it shows expected against received.
- tsc A TypeScript compile error (`error TS2345:`) with the source excerpt around it.
- eslint ESLint's `line:col error rule-name` entries and its `N problems` summary footer.
- pnpm pnpm's `ERR_PNPM_*` codes - the resolver or lockfile refusing, which is the cause itself.
- yarn Yarn Classic's `error <Capital>` lines and Berry's `YN0000:` diagnostic codes.
- bun A failed `bun test` (the crossed-out test and its assertion), or a `bun install` that found no matching version.
- node_runtime An uncaught Node error. The message above the stack is the cause; an ESM/CJS resolution error means a missing or mis-declared module.
- playwright A Playwright test failure - the `1) suite > test` header names the test; its trace and diff follow.
- cypress A `CypressError` or a retry timeout, with the command log leading up to it.
- npm `npm ERR!` lines. A wrapper: npm reports the failure of the script it ran, never the cause.
- js_script_exit A JS package manager announcing that a lifecycle script exited non-zero - pnpm's `ELIFECYCLE`, bun's `error: script "x" exited with code N`.
- go_test `go test`'s per-test `--- FAIL` marker, plus the assertion output printed under it.
- go_panic A Go `panic:` or runtime `fatal error:` with the goroutine dump beneath it.
- rust_test `cargo test`'s `failures:` block through to the `test result:` line.
- rust_panic A Rust panic, with the message and the frames that follow it.
- rust_compile rustc refusing to compile (`error[E0308]`). The first error is usually the cause; later ones often follow from it.
- maven_gradle Maven's `[ERROR]` lines - the compiler and test diagnostics Maven relays.
- gradle Gradle's `* What went wrong:` block, stopping before the `* Try:` boilerplate advice. A wrapper - it names the failed task, the compiler output above it is the cause.
- build_failure_banner The `BUILD FAILURE` / `FAILURE: Build failed` banner Maven and Gradle print once the build gave up.
- dotnet_test `dotnet test`: xunit/nunit `[FAIL]` markers and the `Failed!` summary line.
- dotnet_build MSBuild, Roslyn and NuGet error codes - `error CS0103`, `error NU1101`, `error MSB3073`.
- rspec RSpec's `Failures:` block through to the `N examples, N failures` tally.
- minitest Minitest's numbered `1) Failure:` entries and the assertion beneath each one.
- ruby_exception An unhandled Ruby exception - a backtrace frame naming the error class.
- bundler Bundler failing to resolve - a missing gem, or a version conflict it prints the tree for.
- phpunit PHPUnit's `There were N failures` block through to its `FAILURES`/`ERRORS`/`OK` footer.
- php_fatal A PHP fatal or parse error and the stack trace after it.
- composer Composer's resolver refusing the requirements, with the explanation it prints underneath.
- cc_cpp C/C++ builds - CMake configure errors and linker `undefined reference` / `collect2` failures.
- make `make: ***` - make reporting that a recipe it ran failed. The recipe's own output above it is the cause.
- bazel Bazel reporting that an action or target failed. A wrapper - the compiler or test output it relays is the cause.
- oom The job being killed - exit code 137, `Killed`, `Out of memory`. Nothing else in the log explains a SIGKILL.
- generic_error A line starting `ERROR` or `FATAL` from a tool with no pack of its own - the weakest signal; read it in context.
- docker_build BuildKit giving up - `failed to solve` / `executor failed running` - around the Dockerfile step that failed. A wrapper: the `RUN` step's own output is the cause.
- terraform Terraform's boxed `Error:` and the `on main.tf line 12` it points at.