You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Coverage report is missing uncovered files when using --all with --include #588
When running the test suite of MySQL2 with c8 using --all combined with --include, some files that exist and match the include patterns become invisible in the coverage report when totally uncovered.
For context, here is the coverage configuration used:
However, lib/results_stream.js and lib/packets/binlog_query_statusvars.js don't appear in the report.
Expected behavior:
When bypassing c8's filtering (e.g., collecting V8 coverage data directly and calling Report programmatically) from my custom plugin that uses C8 behind the scenes, both files correctly appear with 0% coverage, confirming they exist and match the patterns.
I found another case that #589 fixes: with --all, c8 adds empty coverage for an executed file when its coverage entry uses an absolute path instead of a file:// URL. I reproduced this with c8 12.0.0 and verified that #589 handles both formats correctly. Could the absolute-path case be included in the regression tests?
Runnable reproduction
Save this as repro.cjs in an isolated directory with c8 available, then run node repro.cjs:
Activity
JBallin commentedon Oct 11, 2026
I found another case that #589 fixes: with
--all, c8 adds empty coverage for an executed file when its coverage entry uses an absolute path instead of afile://URL. I reproduced this with c8 12.0.0 and verified that #589 handles both formats correctly. Could the absolute-path case be included in the regression tests?Runnable reproduction
Save this as
repro.cjsin an isolated directory with c8 available, then runnode repro.cjs:Actual output with c8 12.0.0:
Expected: both accepted identities should be indexed, with zero empty reports for this executed file.