Re: [go-nuts] Bug? go/src/all.bash on master branch fails in go/build test with Go1.18

2022-04-07 Thread tenkoh 
I have heard about build dashboard for the first time. Thanks! I will check 
it.

2022年4月7日木曜日 14:45:39 UTC+9 axel.wa...@googlemail.com:

> The master branch is used for the active development and not for general 
> consumption. It is not unusual for builds/tests to fail on it occasionally. 
> You can always check the build dashboard  to 
> see if that's currently the case.
> Generally, I would tend to assume that there is something wrong with your 
> setup, especially if it also happens on the release-branch.go1.18 branch. 
>
> On Thu, Apr 7, 2022 at 12:25 AM tenkoh  wrote:
>
>> I'm unsure whether this is a bug or not, so let me ask here.
>>
>> *### What version of Go are you using (`go version`)?*
>> go version go1.18 linux/arm64
>>
>> *### Does this issue reproduce with the latest release?*
>> Yes
>>
>> *### What operating system and processor architecture are you using (`go 
>> env`)?*
>> using docker image: golang:1.18
>>
>> GO111MODULE=""
>> GOARCH="arm64"
>> GOBIN=""
>> GOCACHE="/root/.cache/go-build"
>> GOENV="/root/.config/go/env"
>> GOEXE=""
>> GOEXPERIMENT=""
>> GOFLAGS=""
>> GOHOSTARCH="arm64"
>> GOHOSTOS="linux"
>> GOINSECURE=""
>> GOMODCACHE="/go/pkg/mod"
>> GONOPROXY=""
>> GONOSUMDB=""
>> GOOS="linux"
>> GOPATH="/go"
>> GOPRIVATE=""
>> GOPROXY="https://proxy.golang.org,direct";
>> GOROOT="/usr/local/go"
>> GOSUMDB="sum.golang.org"
>> GOTMPDIR=""
>> GOTOOLDIR="/usr/local/go/pkg/tool/linux_arm64"
>> GOVCS=""
>> GOVERSION="go1.18"
>> GCCGO="gccgo"
>> AR="ar"
>> CC="gcc"
>> CXX="g++"
>> CGO_ENABLED="1"
>> GOMOD="/go.mod"
>> GOWORK=""
>> CGO_CFLAGS="-g -O2"
>> CGO_CPPFLAGS=""
>> CGO_CXXFLAGS="-g -O2"
>> CGO_FFLAGS="-g -O2"
>> CGO_LDFLAGS="-g -O2"
>> PKG_CONFIG="pkg-config"
>> GOGCCFLAGS="-fPIC -pthread -fmessage-length=0 
>> -fdebug-prefix-map=/tmp/go-build2526966007=/tmp/go-build 
>> -gno-record-gcc-switches"
>> GOROOT/bin/go version: go version go1.18 linux/arm64
>> GOROOT/bin/go tool compile -V: compile version go1.18
>> uname -sr: Linux 5.10.47-linuxkit
>> /lib/aarch64-linux-gnu/libc.so.6: GNU C Library (Debian GLIBC 
>> 2.31-13+deb11u2) stable release version 2.31.
>>
>> *### What did you do?*
>> Get master branch, then run build & test using "all.bash"
>>
>> ```
>> $ cd /
>> $ mkdir build
>> $ cd build
>> $ git clone https://go.googlesource.com/go
>> $ cd go/src
>> $ ./all.bash 
>> ```
>>
>> *### What did you expect to see?*
>> Success in build and all tests.
>>
>>
>> *### What did you see instead?*
>> --- FAIL: TestImportPackageOutsideModule (0.00s)
>> build_test.go:647: error when importing package when no go.mod is 
>> present: got "no required module provides package example.com/p; to add 
>> it:\n\tgo get example.com/p"; want "go.mod file not found in current 
>> directory or any parent directory"
>> FAIL
>> FAILgo/build0.948s
>>
>>
>> The error occurs in go/src/go/build/build_test.go.
>> The same test passed with go 1.17.8.
>>
>> Best regards,
>>
>> -- 
>> 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/a5ae452c-c991-4a95-8ccb-c698672447bdn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/49a87842-35e8-45b8-bf89-4a2e1784816dn%40googlegroups.com.

Re: [go-nuts] Bug? go/src/all.bash on master branch fails in go/build test with Go1.18

2022-04-06 Thread 'Axel Wagner' via golang-nuts 
The master branch is used for the active development and not for general
consumption. It is not unusual for builds/tests to fail on it occasionally.
You can always check the build dashboard  to see
if that's currently the case.
Generally, I would tend to assume that there is something wrong with your
setup, especially if it also happens on the release-branch.go1.18 branch.

On Thu, Apr 7, 2022 at 12:25 AM tenkoh  wrote:

> I'm unsure whether this is a bug or not, so let me ask here.
>
> *### What version of Go are you using (`go version`)?*
> go version go1.18 linux/arm64
>
> *### Does this issue reproduce with the latest release?*
> Yes
>
> *### What operating system and processor architecture are you using (`go
> env`)?*
> using docker image: golang:1.18
>
> GO111MODULE=""
> GOARCH="arm64"
> GOBIN=""
> GOCACHE="/root/.cache/go-build"
> GOENV="/root/.config/go/env"
> GOEXE=""
> GOEXPERIMENT=""
> GOFLAGS=""
> GOHOSTARCH="arm64"
> GOHOSTOS="linux"
> GOINSECURE=""
> GOMODCACHE="/go/pkg/mod"
> GONOPROXY=""
> GONOSUMDB=""
> GOOS="linux"
> GOPATH="/go"
> GOPRIVATE=""
> GOPROXY="https://proxy.golang.org,direct";
> GOROOT="/usr/local/go"
> GOSUMDB="sum.golang.org"
> GOTMPDIR=""
> GOTOOLDIR="/usr/local/go/pkg/tool/linux_arm64"
> GOVCS=""
> GOVERSION="go1.18"
> GCCGO="gccgo"
> AR="ar"
> CC="gcc"
> CXX="g++"
> CGO_ENABLED="1"
> GOMOD="/go.mod"
> GOWORK=""
> CGO_CFLAGS="-g -O2"
> CGO_CPPFLAGS=""
> CGO_CXXFLAGS="-g -O2"
> CGO_FFLAGS="-g -O2"
> CGO_LDFLAGS="-g -O2"
> PKG_CONFIG="pkg-config"
> GOGCCFLAGS="-fPIC -pthread -fmessage-length=0
> -fdebug-prefix-map=/tmp/go-build2526966007=/tmp/go-build
> -gno-record-gcc-switches"
> GOROOT/bin/go version: go version go1.18 linux/arm64
> GOROOT/bin/go tool compile -V: compile version go1.18
> uname -sr: Linux 5.10.47-linuxkit
> /lib/aarch64-linux-gnu/libc.so.6: GNU C Library (Debian GLIBC
> 2.31-13+deb11u2) stable release version 2.31.
>
> *### What did you do?*
> Get master branch, then run build & test using "all.bash"
>
> ```
> $ cd /
> $ mkdir build
> $ cd build
> $ git clone https://go.googlesource.com/go
> $ cd go/src
> $ ./all.bash
> ```
>
> *### What did you expect to see?*
> Success in build and all tests.
>
>
> *### What did you see instead?*
> --- FAIL: TestImportPackageOutsideModule (0.00s)
> build_test.go:647: error when importing package when no go.mod is
> present: got "no required module provides package example.com/p; to add
> it:\n\tgo get example.com/p"; want "go.mod file not found in current
> directory or any parent directory"
> FAIL
> FAILgo/build0.948s
>
>
> The error occurs in go/src/go/build/build_test.go.
> The same test passed with go 1.17.8.
>
> Best regards,
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/a5ae452c-c991-4a95-8ccb-c698672447bdn%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CAEkBMfHTK%3DUnog3Nj0nttgDTOdRgHFAhuURnEBCn6kdX4tY4xg%40mail.gmail.com.

[go-nuts] Bug? go/src/all.bash on master branch fails in go/build test with Go1.18

2022-04-06 Thread tenkoh 
I'm unsure whether this is a bug or not, so let me ask here.

*### What version of Go are you using (`go version`)?*
go version go1.18 linux/arm64

*### Does this issue reproduce with the latest release?*
Yes

*### What operating system and processor architecture are you using (`go 
env`)?*
using docker image: golang:1.18

GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOENV="/root/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct";
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_arm64"
GOVCS=""
GOVERSION="go1.18"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -pthread -fmessage-length=0 
-fdebug-prefix-map=/tmp/go-build2526966007=/tmp/go-build 
-gno-record-gcc-switches"
GOROOT/bin/go version: go version go1.18 linux/arm64
GOROOT/bin/go tool compile -V: compile version go1.18
uname -sr: Linux 5.10.47-linuxkit
/lib/aarch64-linux-gnu/libc.so.6: GNU C Library (Debian GLIBC 
2.31-13+deb11u2) stable release version 2.31.

*### What did you do?*
Get master branch, then run build & test using "all.bash"

```
$ cd /
$ mkdir build
$ cd build
$ git clone https://go.googlesource.com/go
$ cd go/src
$ ./all.bash 
```

*### What did you expect to see?*
Success in build and all tests.


*### What did you see instead?*
--- FAIL: TestImportPackageOutsideModule (0.00s)
build_test.go:647: error when importing package when no go.mod is 
present: got "no required module provides package example.com/p; to add 
it:\n\tgo get example.com/p"; want "go.mod file not found in current 
directory or any parent directory"
FAIL
FAILgo/build0.948s


The error occurs in go/src/go/build/build_test.go.
The same test passed with go 1.17.8.

Best regards,

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/a5ae452c-c991-4a95-8ccb-c698672447bdn%40googlegroups.com.