make check on main hangs indefinitely. The resolver tests in internal/resolver/ perform iterative DNS resolution starting from root nameservers, which can take >60s or hang entirely.
Root Cause
All resolver tests use testContext() with a 60-second timeout and perform real network DNS queries. The go test command in the Makefile has no timeout flag, so a hanging test blocks forever.
Fix
Add -short and -timeout 30s flags to go test in make check
Skip real-DNS integration tests when -short is set
Context-canceled tests (no network needed) still run
Integration tests can be run explicitly: go test -v -race ./internal/resolver/...
## Problem
`make check` on main hangs indefinitely. The resolver tests in `internal/resolver/` perform iterative DNS resolution starting from root nameservers, which can take >60s or hang entirely.
## Root Cause
All resolver tests use `testContext()` with a 60-second timeout and perform real network DNS queries. The `go test` command in the Makefile has no timeout flag, so a hanging test blocks forever.
## Fix
- Add `-short` and `-timeout 30s` flags to `go test` in `make check`
- Skip real-DNS integration tests when `-short` is set
- Context-canceled tests (no network needed) still run
- Integration tests can be run explicitly: `go test -v -race ./internal/resolver/...`
See PR #21.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
make checkon main hangs indefinitely. The resolver tests ininternal/resolver/perform iterative DNS resolution starting from root nameservers, which can take >60s or hang entirely.Root Cause
All resolver tests use
testContext()with a 60-second timeout and perform real network DNS queries. Thego testcommand in the Makefile has no timeout flag, so a hanging test blocks forever.Fix
-shortand-timeout 30sflags togo testinmake check-shortis setgo test -v -race ./internal/resolver/...See PR #21.