Recently we added reporting package-level failures (that is not associated to a specific test) to LUCI. In some cases, e.g. at timeout, LUCI reports both test failures and package-level failures. E.g. https://ci.chromium.org/ui/p/golang/builders/ci/gotip-netbsd-arm64/b8745232168515795905/overview, which has failures for both os/exec.TestCancelErrors/killed_after_error and os/exec. Currently watchflakes reports two issues for them, in this case #68436 and #66895. We should not report the package-level one.
Comment From: gabyhelp
Related Issues and Documentation
- os/exec: TestCancelErrors/killed_after_error failures #66895
- build: os/exec failures #68436
- build: golang.org/x/tools/go/packages failures #67899
- build: os failures #67451
- x/build/cmd/watchflakes: fails to attribute `*** Test killed with quit:` failures to the running test #61070
- cmd/internal/testdir: Test/fixedbugs/issue46234.go failures #67558
- Testing packages.: unrecognized failures #57995 (closed)
- build: golang.org/x/net/dns/dnsmessage failures #67830
- build: golang.org/x/net/context failures #67828
- runtime: TestCgoPprofPIE aborted on LUCI gotip-linux-ppc64le builder #65173 (closed)
(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)
Comment From: gopherbot
Change https://go.dev/cl/601436 mentions this issue: cmd/watchflakes: coalesce a package-level failure to a test failure in the same package