#!watchflakes
default <- pkg == "golang.org/x/sys/unix" && test == "TestIoctlGetEthtoolDrvinfo"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestIoctlGetEthtoolDrvinfo
    syscall_linux_test.go:61: end0: "st_gmac"
    syscall_linux_test.go:57: failed to get ethtool driver info for "end1": device or resource busy
--- FAIL: TestIoctlGetEthtoolDrvinfo (0.00s)

— watchflakes

Comment From: gopherbot

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "golang.org/x/sys/unix" && test == "TestIoctlGetEthtoolDrvinfo"
2024-05-09 17:46 x_sys-gotip-linux-riscv64 sys@f34bb9fc go@f43d9c40 x/sys/unix.TestIoctlGetEthtoolDrvinfo (log) === RUN TestIoctlGetEthtoolDrvinfo syscall_linux_test.go:61: end0: "st_gmac" syscall_linux_test.go:57: failed to get ethtool driver info for "end1": device or resource busy --- FAIL: TestIoctlGetEthtoolDrvinfo (0.00s)
2024-05-13 22:24 x_sys-go1.21-linux-riscv64 sys@6943ab67 release-branch.go1.21@6f521957 x/sys/unix.TestIoctlGetEthtoolDrvinfo (log) === RUN TestIoctlGetEthtoolDrvinfo syscall_linux_test.go:61: end0: "st_gmac" syscall_linux_test.go:57: failed to get ethtool driver info for "end1": device or resource busy --- FAIL: TestIoctlGetEthtoolDrvinfo (0.00s)

— watchflakes

Comment From: griesemer

ping @mdlayher

Comment From: mdlayher

It looks like https://github.com/golang/go/issues/67350 and subsequent CL added a check for EBUSY which I would have expected to be the solution here. Otherwise I'm unsure where to look next.

Comment From: ianlancetaylor

Looks like this log was run on May 13, but the fix was committed on May 17. I don't know why watchflakes is reporting a May 13 run in June, but this is presumably fixed.