x/net/ipv6: TestPacketConnReadWriteMulticast{UDP,ICMP} failing with "i/o timeout" on OpenBSD 6.8 #42064
Comments
This test consistently fails on the openbsd-arm64-jsing: https://build.golang.org/log/be54c3c8bfe2313b55b63b76bc5af92d6c39a524 The test also failed on https://golang.org/cl/274772 on the It doesn't seem to fail on builder running OpenBSD 6.2 or 6.4. |
It'd be helpful to find out if the test runs or gets skipped on OpenBSD 6.4. (It's possible it's passing in 6.4 because IPv6 isn't supported there and it gets skipped.) |
Marking as release-blocker via #11811, especially since this doesn't seem builder- or arch-specific. But note that OpenBSD is not a first-class port, so it may be viable to unblock the release by skipping the test on the affected builders — especially given that this appears to be either a regression in the kernel or an incompatible ABI change. |
Change https://golang.org/cl/279512 mentions this issue: |
The known issue with OpenBSD 6.8 builders appears to be resolved via CL 278732 and CL 279134. Promote them to the primary OpenBSD post-submit builders and TryBots. Having test coverage from OpenBSD 6.8 and 6.4 builders gives us us more confidence that Go works on supported OpenBSD versions (which are 6.8 and 6.7 at this time, per past policy decision in https://golang.org/issue/15227#issuecomment-293319876). Reduce numTryTestHelpers from 5 to 4 based on some data from golang.org/issue/37439 showing that going from 3 to 5 helpers doesn't make a significant difference. We can adjust further if we learn that OpenBSD TryBots become the bottleneck. Fixes golang/go#35712. For golang/go#42542. For golang/go#42064. Updates golang/go#42426. Change-Id: Id2fa4be7c3161f89752c1428146846fe06ca63db Reviewed-on: https://go-review.googlesource.com/c/build/+/279512 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Trust: Dmitri Shuralyov <dmitshur@golang.org>
Change https://golang.org/cl/280052 mentions this issue: |
These tests are known to be failing on OpenBSD 6.8 and need investigation. The OpenBSD 6.8 builders are default TryBots now, so skip them to prevent people working on other packages from constantly getting a failure. Issue 42064 remains open to do the work of determining if the ipv6 package needs to be fixed, or if OpenBSD 6.8 has a problem and the test can be permanently skipped as unsupported. For golang/go#11811. Updates golang/go#42064. Updates golang/go#35712. Change-Id: I59883384e4dbce679cb1a4e8e2c3f0fa7983010b Reviewed-on: https://go-review.googlesource.com/c/net/+/280052 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Trust: Dmitri Shuralyov <dmitshur@golang.org>
@4a6f656c Do openbsd-{arm,arm64,mips64}-jsing builders all run OpenBSD 6.8? If not, the issue title may need to be adjusted further. |
@4a6f656c Just a friendly ping on this release-blocker in the new year. Do you have any updates? |
@4a6f656c Have there been any updates with this issue. We are approaching the release and this is a release-blocker. |
I quickly checked the arm64 and mips64 builders using
Assuming that the offline openbsd-arm-jsing builder also runs at least 6.7 (see #25498 (comment)) and that OpenBSD version might be affected the same, I've sent https://golang.org/cl/283752 to include |
Change https://golang.org/cl/283752 mentions this issue: |
TestPacketConnReadWriteMulticastUDP
is failing fairly consistently on theopenbsd-arm-jsing
builders. It should either be fixed or skipped.Note that this failure mode is different from the one on Darwin (#37319) and the one previously reported for OpenBSD (#33843).
2020-10-16T16:51:38-7b1cca2/openbsd-arm-jsing
2020-10-16T16:51:38-7b1cca2/openbsd-arm64-jsing
2020-10-10T22:47:23-4f7140c/openbsd-arm-jsing
2020-10-09T03:24:41-dbdefad/openbsd-arm-jsing
2020-10-08T22:28:04-59f7323/openbsd-arm-jsing
2020-10-06T15:34:59-a7d1128/openbsd-arm-jsing
2020-10-02T20:24:02-0a1ea39/openbsd-arm-jsing
2020-09-30T14:50:03-4acb6c0/openbsd-arm-jsing
2020-09-27T03:25:02-5d4f700/openbsd-arm-jsing
2020-09-25T08:00:53-05aa5d4/openbsd-arm-jsing
2020-09-23T18:22:12-328152d/openbsd-arm-jsing
2020-09-04T19:48:48-62affa3/openbsd-arm-jsing
2020-08-22T12:43:28-c890458/openbsd-arm-jsing
2020-08-13T13:45:08-3edf25e/openbsd-arm-jsing
2020-07-07T03:43:11-ab34263/openbsd-arm-jsing
2020-06-25T00:16:55-4c52546/openbsd-arm-jsing
2020-06-02T11:40:24-627f964/openbsd-arm-jsing
2020-05-28T22:51:25-3c3fba1/openbsd-arm-jsing
2020-05-20T18:23:14-0ba52f6/openbsd-arm-jsing
CC @4a6f656c @golang/osp-team
The text was updated successfully, but these errors were encountered: