-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: misc/cgo/testtls failing on openbsd-386-62, openbsd-amd64-62 #42408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It fails at the third run of |
Others are warnings. Probably fine. |
I'll take a look, but I manually tested here on 6.2 when the trybot was being difficult and as far as I know it worked. In short, the OpenBSD 6.2 builders should be retired - the only supported versions of OpenBSD are 6.7 and 6.8 - 6.2 was EOL when 6.4 was released in October 2018 (even the 6.4 builders are also more than a year EOL). |
Between here and #42237 there seems to be consensus that we just don't care about OpenBSD 6.2 any more. Perhaps https://github.com/golang/go/wiki/OpenBSD#building-from-source needs an update? |
There are probably parts of that wiki page that need updating, however the relevant part is: https://github.com/golang/go/wiki/OpenBSD#longterm-support (I think building from source was more so tracking whether it was possible, rather than if it was EOL :)) |
Change https://golang.org/cl/268097 mentions this issue: |
Just clarifying that the consensus here is that dropping OpenBSD 6.2 will fix this issue? It wasn't clear to me that we figured out that this is definitely specific to 6.2. |
Dropping 6.2 is covered by #42426, so if that's what we need to do, we can close this issue. |
Ping. Do we know that this is definitely a OpenBSD 6.2 issue? |
Hence, closing. |
There are numerous of these failures on http://build.golang.org (386 only until #42237 is fixed).
https://build.golang.org/log/131aa06b3b531ffe83df8b656838bebe8427a850
These started after http://golang.org/cl/267318, which re-enabled these tests.
These also show up on openbsd-amd64-62 with the fix for #42237.
cc @4a6f656c @cherrymui
The text was updated successfully, but these errors were encountered: