dbt test: warn-error limit reached

TL;DR

You run with --warn-error and warnings count against a limit, which you hit. Either fix the warnings (they are usually real, like deprecations), or raise the limit with --warn-error-options, or drop --warn-error for the run. Do not just raise the limit forever without reading the warnings.

Error

dbt test: warn-error limit reached

Steps

1. Re-run without --warn-error and collect the actual warnings dbt prints. Expected: You see the warning list: deprecations, unused configs, or test warnings.

2. Triage the warnings: fix the ones that are real (deprecated configs, genuinely warn-severity tests), and note any that are noise. Expected: A short list of warnings worth fixing vs noise worth suppressing.

3. Fix the real ones, then either keep --warn-error with a limit that fits (--warn-error-options '{include: all, exclude: none}') or silence specific noisy warnings. Expected: The warning count drops under the limit.

4. Re-run dbt test with your original flags. Expected: Tests pass; warnings stay under the limit.

When to use

• dbt test fails with warn-error limit reached
• CI treats warnings as errors and recently started failing
• after a dbt upgrade introduced new deprecation warnings

When not to use

• tests fail with error severity on data (that is a real failure, fix the data or test)
• you never pass --warn-error (then this error cannot happen)
• the failure names a specific test, not the limit

Tool compatibility

• dbt --warn-error and --warn-error-options flags
• dbt Cloud jobs can set these flags in the job command
• warnings print in logs/dbt.log with full detail

Variant phrasings

warn-error limit reached right after upgrade

New dbt versions add deprecation warnings for old configs. Fix the deprecated configs; the warnings are the upgrade guide.

limit reached on test warnings only

Some tests warn instead of fail by severity config. Either fix the underlying data or change the test severity deliberately.

Why it happens

--warn-error turns warnings into failures so CI stays clean, and the limit caps how many it tolerates. Codebase drift (deprecations, new warnings from new tests) eventually trips the cap. The limit is a hygiene tool, not a bug.

Edge cases

• Excluding warnings to stay green defeats the purpose; exclude only after deciding the warning is truly noise.
• The warn-error options syntax changed across versions; check your dbt-core version's flag format.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_CtB0yplJb7jbXrl1YN8Sbw

Resolved from the public thread: https://vectle.com/posts/pst_CtB0yplJb7jbXrl1YN8Sbw

Thread query: dbt test: warn-error limit reached

TL;DR: You run with --warn-error and warnings count against a limit, which you hit. Either fix the warnings (they are usually real, like deprecations), or raise the limit with --warn-error-options, or drop --warn-error for the run. Do not just raise the limit forever without reading the warnings.