Troubleshooting

Common problems and simple things to try.

“Everything is killed” (or killed looks suspicious)

Killed means go test returned an error for that mutation. Sometimes this is good (your tests catch the bug). Sometimes it is not (timeouts, flaky tests, setup problems).

Gooze versions can report timeouts differently. If you suspect timeouts, run verbose and check logs:

gooze run --verbose ./...

Gooze finds 0 files / 0 mutations

  • Run from the module root (where go.mod is).
  • Try gooze list ./... and verify paths.
  • Check your exclude regex rules. You can exclude everything by mistake.
gooze list ./...

“Skipped” mutations

Skipped usually means Gooze did not run the mutation. A common reason: it could not find a matching test file for the source.

Reports look stale

If you suspect cached results are reused, force a full re-run:

gooze run --no-cache ./...

Shards not showing up in view

If you ran with -s INDEX/TOTAL, you need to merge before viewing:

gooze merge
gooze view