go: net: test is failing on Dragonfly builder

What version of Go are you using (go version)?

1.13

Does this issue reproduce with the latest release?

yes

What operating system and processor architecture are you using (go env)?

DragonflyBSD amd64

What did you do?

The net test is consistently failing after I upgraded the OS to a recent commit: https://build.golang.org/log/58be31cfd1a92ba9582fdf33e01f79e03184e59b

At first glance, this appears to be a Dragonfly bug http://bugs.dragonflybsd.org/issues/3205

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 1
  • Comments: 35 (24 by maintainers)

Commits related to this issue

Most upvoted comments

It’s presenting a new RTM_VERSION in the headers so it’s stable, right?

What effect does changing RTM_VERSION have on the kernel’s syscall ABI? (I’m not familiar with the Dragonfly kernel.)

Do Dragonfly kernels provide ABI compatibility with previous RTM_VERSIONs? If so, we should probably stay on the older RTM_VERSION.

+1
bcmills on Oct 11, 2019
  1. Can we have two separate builders, one for ‘master’ and one for ‘release’ ?

Absolutely! See http://golang.org/wiki/DashboardBuilders for instructions on how to add a new builder.

  1. How to deal with such cases in Go so that programs work in both ‘master’ and ‘release’ ?

That seems like more of a Dragonfly question — does the Dragonfly kernel not provide a stable syscall ABI?

(If it does not, perhaps we should change Dragonfly to use a C syscall library, as we did for macOS in #17490; CC @randall77.)

+1
bcmills on Oct 11, 2019
Read more comments on GitHub
← go: net: slice bounds out of range
go: net: TestInterfaceHardwareAddrWithWmic fails →