Go 1.18 Beta 1 is released

[Cherry Mui]

Hello gophers,

We have just released go1.18beta1, a beta version of Go 1.18.
It is cut from the master branch at the revision tagged go1.18beta1.

Please try your production load tests and unit tests with the new version.
Your help testing these pre-release versions is invaluable.

Report any problems using the issue tracker:
https://golang.org/issue/new

If you have Go installed already, the easiest way to try go1.18beta1
is by using the go command:
$ go install golang.org/dl/go1.18beta1@latest
$ go1.18beta1 download

You can download binary and source distributions from the usual place:
https://golang.org/dl/#go1.18beta1

To find out what has changed in Go 1.18, read the draft release notes:
https://tip.golang.org/doc/go1.18

Cheers,
Cherry and Alex for the Go Team

[Jan Mercl]

On Tue, Dec 14, 2021 at 8:51 PM Cherry Mui <che...@golang.org> wrote:

> We have just released go1.18beta1, a beta version of Go 1.18.
> It is cut from the master branch at the revision tagged go1.18beta1.
>
> Please try your production load tests and unit tests with the new version.
> Your help testing these pre-release versions is invaluable.
>
> Report any problems using the issue tracker:
> https://golang.org/issue/new

The link requires a Github account, which I don't have so instead
reporting here:

When trying to build from source on netbsd/amd64 in qemu, both
'all.bash' and 'make.bash' crashes, logs attached. FYI, with Go1.17.5
and the same qemu VM, 'all.bash' fails, but does not crash IIRC and
'make.bash' completes without issues.

-j

[Austin Clements]

Jan, assuming you're running on an AMD CPU, this is go.dev/issue/34988 (if you're not running on an AMD CPU, that would be very interesting to know!) The TL;DR is that this appears to be a kernel bug, and we have a C reproducer, but we do not yet have a fix or a workaround.

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAA40n-UsTmUHXa-ao%3DykO9ejG-J8OD8scdmKiQtoxC2npC4HOg%40mail.gmail.com.

[Jan Mercl]

On Wed, Dec 15, 2021 at 7:41 PM Austin Clements <aus...@google.com> wrote:

> Jan, assuming you're running on an AMD CPU, this is go.dev/issue/34988 (if you're not running on an AMD CPU, that would be very interesting to know!) The TL;DR is that this appears to be a kernel bug, and we have a C reproducer, but we do not yet have a fix or a workaround.

Yep, the qemu host in question was running on an AMD Ryzen 9 3900X.

[Jan Mercl]

On Tue, Dec 14, 2021 at 8:51 PM Cherry Mui <che...@golang.org> wrote:

Let me report another failure that works, ie. tests build and pass,
with Go1.17.5 but not with Go1.18beta1

----
jnml@darwin-m1:~$ GO111MODULE=off go get github.com/edsrzf/mmap-go
jnml@darwin-m1:~$ cd edsrzf/mmap-go/
/Users/jnml/src/github.com/edsrzf/mmap-go
jnml@darwin-m1:~/src/github.com/edsrzf/mmap-go$ go test
go: downloading golang.org/x/sys v0.0.0-20181221143128-b4a75ba826a6
# golang.org/x/sys/unix
/Users/jnml/pkg/mod/golang.org/x/s...@v0.0.0-20181221143128-b4a75ba826a6/unix/zsyscall_darwin_arm64.go:28:3:
//go:linkname must refer to declared function or variable
/Users/jnml/pkg/mod/golang.org/x/s...@v0.0.0-20181221143128-b4a75ba826a6/unix/zsyscall_darwin_arm64.go:43:3:
//go:linkname must refer to declared function or variable
/Users/jnml/pkg/mod/golang.org/x/s...@v0.0.0-20181221143128-b4a75ba826a6/unix/zsyscall_darwin_arm64.go:59:3:
//go:linkname must refer to declared function or variable
/Users/jnml/pkg/mod/golang.org/x/s...@v0.0.0-20181221143128-b4a75ba826a6/unix/zsyscall_darwin_arm64.go:75:3:
//go:linkname must refer to declared function or variable
/Users/jnml/pkg/mod/golang.org/x/s...@v0.0.0-20181221143128-b4a75ba826a6/unix/zsyscall_darwin_arm64.go:90:3:
//go:linkname must refer to declared function or variable
/Users/jnml/pkg/mod/golang.org/x/s...@v0.0.0-20181221143128-b4a75ba826a6/unix/zsyscall_darwin_arm64.go:105:3:
//go:linkname must refer to declared function or variable
/Users/jnml/pkg/mod/golang.org/x/s...@v0.0.0-20181221143128-b4a75ba826a6/unix/zsyscall_darwin_arm64.go:121:3:
//go:linkname must refer to declared function or variable
/Users/jnml/pkg/mod/golang.org/x/s...@v0.0.0-20181221143128-b4a75ba826a6/unix/zsyscall_darwin_arm64.go:136:3:
//go:linkname must refer to declared function or variable
/Users/jnml/pkg/mod/golang.org/x/s...@v0.0.0-20181221143128-b4a75ba826a6/unix/zsyscall_darwin_arm64.go:151:3:
//go:linkname must refer to declared function or variable
/Users/jnml/pkg/mod/golang.org/x/s...@v0.0.0-20181221143128-b4a75ba826a6/unix/zsyscall_darwin_arm64.go:166:3:
//go:linkname must refer to declared function or variable
/Users/jnml/pkg/mod/golang.org/x/s...@v0.0.0-20181221143128-b4a75ba826a6/unix/zsyscall_darwin_arm64.go:166:3:
too many errors
FAIL github.com/edsrzf/mmap-go [build failed]
jnml@darwin-m1:~/src/github.com/edsrzf/mmap-go$ go version
go version go1.18beta1 darwin/arm64
jnml@darwin-m1:~/src/github.com/edsrzf/mmap-go$
----

PS: Going through the builders logs now, there might be more to report later.

[Jan Mercl]

On Tue, Dec 14, 2021 at 8:51 PM Cherry Mui <che...@golang.org> wrote:

There's a test regression with Go1.18beta1 on freebsd/amd64 and
modernc.org/file.

The log file (https://gitlab.com/cznic/builder/-/blob/cdca564a0543e9ad0441884e3c12f7c0a326bdab/logs/freebsd64)
does not say much and I have not yet managed to look into the details:

----
I1215 17:27:15.350530 1078 builder_test.go:583] Wed, 15 Dec 2021
17:27:15 CET: testing
modernc.org/file@14a2f19c5fb54a1264e8b2fa0e79b906349240af
I1215 17:27:15.350578 1078 builder_test.go:609] dir
/home/jnml/src/modernc.org/builder/.exclude/src/modernc.org/file, cmd
[go test -timeout 24h]
E1215 17:32:17.815439 1078 builder_test.go:501] dir
"/home/jnml/src/modernc.org/builder/.exclude/src/modernc.org/file",
argv0 "go", envExtra [], args ["test" "-timeout" "24h"], out
--- FAIL: TestCallocBigMap (3.04s)
all_test.go:1078: 161
FAIL
exit status 1
FAIL modernc.org/file 301.930s
E1215 17:32:17.815516 1078 builder_test.go:503] FAIL: exit status 1
wd "/usr/home/jnml/src/modernc.org/builder/.exclude/src/modernc.org/file", <nil>
E1215 17:32:17.816481 1078 builder_test.go:612] FAIL testing modernc.org/file
----

https://modern-c.appspot.com/-/builder/?importpath=modernc.org%2ffile
https://gitlab.com/cznic/builder/-/commit/cdca564a0543e9ad0441884e3c12f7c0a326bdab#cdf7e925f5746741c316f5fbcf39ad0dfca90775_88_87

[Ian Lance Taylor]

There are no compatibility promises for unsupported techniques like
go:linkname. If they update their copy of golang.org/x/sys, it will
work with Go1.18beta1. I believe that this was fixed by
https://golang.org/cl/274573 which was committed to x/sys 2020-12-02.

Ian

[Jan Mercl]

On Fri, Dec 17, 2021 at 6:28 AM Ian Lance Taylor <ia...@golang.org> wrote:

> There are no compatibility promises for unsupported techniques like
> go:linkname. If they update their copy of golang.org/x/sys, it will
> work with Go1.18beta1. I believe that this was fixed by
> https://golang.org/cl/274573 which was committed to x/sys 2020-12-02.

Thanks for the information, I'll try to reach Evan by mail.

-j