all.bat: tests fails in windows 10 at tip

[rajender]

all.bat in windows 10 fails with following errors.
I am using go 1.9.2 to build go tip.

Link to all.bat full output: http://text-share.com/view/cc0f79eb

[mvdan]

The size of this issue is massive - please try to put most of the copy-pasted text into a file and link to it. Otherwise it's unmanageable.

[rajender]

OK. Updated original report with link to full output.

Three package tests are failing.

1. net/http

--- FAIL: TestTransportBodyReadError (0.08s)
client_test.go:1826: Get http://127.0.0.1:52730/ping: write tcp 127.0.0.1:52733->127.0.0.1:52730: wsasend: An established connection was aborted by the software in your host machine.
FAIL
FAIL net/http 21.481s

2. runtime

Line 137: --- FAIL: TestGdbBacktrace (4.20s)
Line 149: --- FAIL: TestGdbConst (7.99s)
Line 153: --- FAIL: TestGdbAutotmpTypes (8.77s)
Line 623: FAIL runtime 180.470s

3. cmd/go

panic: test timed out after 3m0s

goroutine 970 [running]:
testing.(*M).startAlarm.func1()
C:/Users/rajender/go-contrib/go/src/testing/testing.go:1183 +0xef
created by time.goFunc
C:/Users/rajender/go-contrib/go/src/time/sleep.go:172 +0x4b

goroutine 1 [chan receive]:
testing.tRunner.func1(0xc042250000)
C:/Users/rajender/go-contrib/go/src/testing/testing.go:745 +0x118
testing.tRunner(0xc042250000, 0xc042083b78)
C:/Users/rajender/go-contrib/go/src/testing/testing.go:771 +0xd1
testing.runTests(0xc0421f2060, 0xbb1120, 0xf0, 0xf0, 0x33)
C:/Users/rajender/go-contrib/go/src/testing/testing.go:1034 +0x29d
testing.(*M).Run(0xc0421ac000, 0x0)
C:/Users/rajender/go-contrib/go/src/testing/testing.go:954 +0x163
cmd/go_test.TestMain(0xc0421ac000)
C:/Users/rajender/go-contrib/go/src/cmd/go/go_test.go:162 +0x1a5
main.main()
_testmain.go:520 +0x158
.....
FAIL cmd/go 193.565s

[mvdan]

Please provide your go env output. Also, does all.bat work fine if you're building 1.9.2?

Also note that you don't need to run the tests to build tip - you could use make.bat instead, skipping the tests.

[rajender]

C:\Users\rajender\go-contrib\go\src>go env
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\rajender\go
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\rajender\AppData\Local\Temp\go-build488734623=/tmp/go-build -gno-record-gcc-switches
set CXX=g++
set CGO_ENABLED=1
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config

[rajender]

building go1.9.2 also have same errors and some more.

Full output: http://text-share.com/view/c8ae4745

[alexbrainman]

@rajender quite a few tests fail.

I am not surprised that runtime.TestGdb* tests are not working. I have never tested them myself - I could not make gdb / pyhon runtime working. I suspect these are also skipped on all out builders.

runtime and cmd/go run out of time. I wonder if your computer is slow. You can test my theory by running these tests individually. You should also have -v flag so you can see progress as each test will print "PASS" as they go. For example, run

go test -v -short cmd/go

and see if it is still going just before 3 minutes elapses. Some for runtime package.

If your computer is slow, try and stop antivirus program temporarily - it helps for me a little.

Not sure about net/http.TestTransportBodyReadError failure.

Alex

[ianlancetaylor]

What is the status with 1.10.1? Thanks.

[bcmills]

I am not surprised that runtime.TestGdb* tests are not working. […] I suspect these are also skipped on all out builders.

They aren't skipped during racebuild (#24354). They're failing under gomote for me at tip.

--- FAIL: TestGdbBacktrace (2.43s)
        runtime-gdb_test.go:59: gdb version 7.10
        runtime-gdb_test.go:346: could not find '#0.*main\.eee' in backtrace
        runtime-gdb_test.go:347: gdb output:
                Excess command line arguments ignored. (off ...)
                Directory argument required.
                Use 'set auto-load safe-path /' for disabling the auto-load safe-path security.
                C:\workdir\go\src\runtime: No such file or directory.
                C:\workdir\go\src\runtime/startup-with-shell: No such file or directory.
                Argument required (expression to compute).
                No default breakpoint address now.
                No executable specified, use `target exec'.
                No stack.
                The program is not being run.
--- FAIL: TestGdbPanic (7.21s)
        runtime-gdb_test.go:59: gdb version 7.10
        runtime-gdb_test.go:542: could not find '#.* .* in main\.crash' in backtrace
        runtime-gdb_test.go:543: gdb output:
                Excess command line arguments ignored. (off ...)
                Directory argument required.
                Use 'set auto-load safe-path /' for disabling the auto-load safe-path security.
                C:\workdir\go\src\runtime: No such file or directory.
                C:\workdir\go\src\runtime/startup-with-shell: No such file or directory.
                Argument required (expression to compute).
                No executable specified, use `target exec'.
                No stack.
--- FAIL: TestGdbConst (6.69s)
        runtime-gdb_test.go:59: gdb version 7.10
        runtime-gdb_test.go:475: output "Excess command line arguments ignored. (off ...)\nDirectory argument required.\nUse 'set auto-load safe-path /' for disabling the auto-load safe-path security.\nC:\\workdir\\go\\src\\runtime: No such file or directory.\nC:\\workdir\\go\\src\\runtime/startup-with-shell: No such file or directory.\nArgument required (expression to compute).\nNo default breakpoint address now.\nNo executable specified, use `target exec'.\nThe history is empty.\nThe history is empty.\nThe history is empty.\nThe history is empty.\nThe history is empty.\n"
        runtime-gdb_test.go:478: output mismatch
--- FAIL: TestGdbAutotmpTypes (6.00s)
        runtime-gdb_test.go:59: gdb version 7.10
        runtime-gdb_test.go:416: could not find struct []main.astruct; in 'info typrs astruct' output
        runtime-gdb_test.go:417: gdb output:
                Excess command line arguments ignored. (off ...)
                Directory argument required.
                Use 'set auto-load safe-path /' for disabling the auto-load safe-path security.
                C:\workdir\go\src\runtime: No such file or directory.
                C:\workdir\go\src\runtime/startup-with-shell: No such file or directory.
                Argument required (expression to compute).
                No default breakpoint address now.
                No executable specified, use `target exec'.
                The program is not being run.
                "info" must be followed by the name of an info command.
                List of info subcommands:

                info address -- Describe where symbol SYM is stored
                info all-registers -- List of all registers and their contents
                info args -- Argument variables of current stack frame
                info auto-load -- Print current status of auto-loaded files
                info auto-load-scripts -- Print the list of automatically loaded Python scripts
                info auxv -- Display the inferior's auxiliary vector
                info bookmarks -- Status of user-settable bookmarks
                info breakpoints -- Status of specified breakpoints (all user-settable breakpoints if no argument)
                info classes -- All Objective-C classes
                info common -- Print out the values contained in a Fortran COMMON block
                info copying -- Conditions for redistributing copies of GDB
                info dcache -- Print information on the dcache performance
                info display -- Expressions to display when program stops
                info exceptions -- List all Ada exception names
                info extensions -- All filename extensions associated with a source language
                info files -- Names of targets and files being debugged
                info float -- Print the status of the floating point unit
                info frame -- All about selected stack frame
                info frame-filter -- List all registered Python frame-filters
                info functions -- All function names
                info guile -- Prefix command for Guile info displays
                info handle -- What debugger does when program gets various signals
                info inferiors -- IDs of specified inferiors (all inferiors if no argument)
                info line -- Core addresses of the code for a source line
                info locals -- Local variables of current stack frame
                info macro -- Show the definition of MACRO
                info macros -- Show the definitions of all macros at LINESPEC
                info mem -- Memory region attributes
                info os -- Show OS data ARG
                info pretty-printer -- GDB command to list all registered pretty-printers
                info probes -- Show available static probes
                info proc -- Show /proc process information about any running process
                info program -- Execution status of the program
                info record -- Info record options
                info registers -- List of integer registers and their contents
                info scope -- List the variables local to a scope
                info selectors -- All Objective-C selectors
                info set -- Show all GDB settings
                info sharedlibrary -- Status of loaded shared object libraries
                info signals -- What debugger does when program gets various signals
                info skip -- Display the status of skips
                info source -- Information about the current source file
                info sources -- Source files in the program
                info stack -- Backtrace of the stack
                info static-tracepoint-markers -- List target static tracepoints markers
                info symbol -- Describe what symbol is at location ADDR
                info target -- Names of targets and files being debugged
                info tasks -- Provide information about all known Ada tasks
                info terminal -- Print inferior's saved terminal status
                info threads -- Display currently known threads
                info tracepoints -- Status of specified tracepoints (all tracepoints if no argument)
                info tvariables -- Status of trace state variables and their values
                info type-printers -- GDB command to list all registered type-printers
                info types -- All type names
                info unwinder -- GDB command to list unwinders
                info variables -- All global and static variable names
                info vector -- Print the status of the vector unit
                info vtbl -- Show the virtual function table for a C++ object
                info w32 -- Print information specific to Win32 debugging
                info warranty -- Various kinds of warranty you do not have
                info watchpoints -- Status of specified watchpoints (all watchpoints if no argument)
                info xmethod -- GDB command to list registered xmethod matchers

                Type "help info" followed by info subcommand name for full documentation.
                Type "apropos word" to search for commands related to "word".
                Command name abbreviations are allowed if unambiguous.
FAIL
FAIL    runtime 76.955s

[gopherbot]

Change https://golang.org/cl/112895 mentions this issue: cmd/racebuild: install Git and GCC on the Windows builder

[gopherbot]

Change https://golang.org/cl/112896 mentions this issue: runtime/race: update most syso files to compiler-rt fe2c72

[gopherbot]

Change https://golang.org/cl/112915 mentions this issue: runtime: skip GDB tests on Windows

[ianlancetaylor]

Is there anything more to do here for 1.11? Thanks.

[ianlancetaylor]

No response to question as to whether there is anything else to do, so closing.