Skip to content
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

cmd/go: TestScript failing on Windows with "The handle is invalid." #35350

Open
FiloSottile opened this issue Nov 4, 2019 · 1 comment
Milestone

Comments

@FiloSottile
Copy link
Member

@FiloSottile FiloSottile commented Nov 4, 2019

https://storage.googleapis.com/go-build-log/2a4850e8/windows-amd64-2016_a2bc003d.log from the https://golang.org/cl/205057 TryBot.

--- FAIL: TestScript (0.00s)
    --- FAIL: TestScript/mod_get_upgrade_pseudo (0.09s)
        script_test.go:192: 
            # For this test module there are three versions:
            #   * v0.1.1-0.20190429073117-b5426c86b553
            #   * v0.1.0
            #   * v0.0.0-20190430073000-30950c05d534
            # Only v0.1.0 is tagged.
            #
            # The v0.1.1 pseudo-version is semantically higher than the latest tag.
            # The v0.0.0 pseudo-version is chronologically newer.
            # Start at v0.1.1-0.20190429073117-b5426c86b553 (0.068s)
            > go get -d example.com/pseudoupgrade@b5426c8
            [stderr]
            go: downloading example.com v1.0.0
            go get example.com/pseudoupgrade@b5426c8: example.com/pseudoupgrade@b5426c8: invalid version: Get "http://127.0.0.1:49695/mod/example.com/pseudoupgrade/@v/b5426c8.info": dial tcp 127.0.0.1:49695: The handle is invalid.
            [exit status 1]
            FAIL: testdata\script\mod_get_upgrade_pseudo.txt:13: unexpected command failure

A single hit on greplogs: 2019-11-04T10:13:30-1b2ff10/windows-386-2008

/cc @bcmills

@FiloSottile FiloSottile added this to the Go1.14 milestone Nov 4, 2019
@bcmills

This comment has been minimized.

Copy link
Member

@bcmills bcmills commented Nov 5, 2019

This looks like the Windows equivalent of the failure in #35351 (comment), so let's hold off on digging in too far until the current netpoll instability has been worked out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.