-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
all: test failures after calling all.bat on Windows7 #24709
Comments
all.bat
on Windows7
Thank you for the report:
Looks like your cmd.exe calls chcp program. Do you know why? TestLookPath calls "cmd.exe /c test.exe" with no standard PATH, and I suspect cmd.exe could not find chcp program.
Looks the same as above.
No one on that I know of has gdb with Python support. Including our builders. So all these Gdb/python tests are skipped everywhere. You are welcome to fix these tests, but we should modify our builders so they have appropriate Gdb installed first. If you know how to install Gdb, I could show you where the code that configures builders lives. So you could adjust builders config. Also this https://go-review.googlesource.com/#/c/go/+/102419/ is probably related. Feel free to review the CL.
Looks like a dup of #17245 and #23171 Alex |
calling
while i've been using
i think i've seen this error before. i can try debugging this eventually. thanks |
Test, unlike you, modifies PATH.
That is what I would do.
Well, your gdb setup is different from mine.
We have bunch of computers https://build.golang.org that run all.bat for every change we submit. Windows builders have some software installed to execute all.bat. For example gcc. I am certain builders do not have gcc with python setup - otherwise they would have failed the tests. Just like you.
That would be nice. Thank you. Alex |
i was on PTO last week and quite busy this week, so i will try to find some time to debug some of the issues here next week. |
`%SystemRoot%/System32/chcp.com` is a tool on Windows that is used to change the active code page in the console. `go test os/exec` can fail with: "'chcp' is not recognized as an internal or external command" The test uses a custom PATH variable but does not include `%SystemRoot%/System32`. Always append that to PATH. Ref golang#24709
`%SystemRoot%/System32/chcp.com` is a tool on Windows that is used to change the active code page in the console. `go test path/filepath` can fail with: "'chcp' is not recognized as an internal or external command" The test uses a custom PATH variable but does not include `%SystemRoot%/System32`. Always append that to PATH. Ref golang#24709
`%SystemRoot%/System32/chcp.com` is a tool on Windows that is used to change the active code page in the console. `go test os/exec` can fail with: "'chcp' is not recognized as an internal or external command" The test uses a custom PATH variable but does not include `%SystemRoot%/System32`. Always append that to PATH. Updates golang#24709
`%SystemRoot%/System32/chcp.com` is a tool on Windows that is used to change the active code page in the console. `go test path/filepath` can fail with: "'chcp' is not recognized as an internal or external command" The test uses a custom PATH variable but does not include `%SystemRoot%/System32`. Always append that to PATH. Updates golang#24709
Change https://golang.org/cl/109361 mentions this issue: |
Change https://golang.org/cl/109362 mentions this issue: |
did a couple of fixes for the this one doesn't happen all the time:
and also i'm noticing an infinite loop if i run: instead of: |
full output of:
i see a lot of failed tests in there. |
'%SystemRoot%/System32/chcp.com' is a tool on Windows that is used to change the active code page in the console. 'go test path/filepath' can fail with: "'chcp' is not recognized as an internal or external command" The test uses a custom PATH variable but does not include '%SystemRoot%/System32'. Always append that to PATH. Updates golang#24709
'%SystemRoot%/System32/chcp.com' is a tool on Windows that is used to change the active code page in the console. 'go test os/exec' can fail with: "'chcp' is not recognized as an internal or external command" The test uses a custom PATH variable but does not include '%SystemRoot%/System32'. Always append that to PATH. Updates golang#24709
'%SystemRoot%/System32/chcp.com' is a tool on Windows that is used to change the active code page in the console. 'go test path/filepath' can fail with: "'chcp' is not recognized as an internal or external command" The test uses a custom PATH variable but does not include '%SystemRoot%/System32'. Always append that to PATH. Updates #24709 Change-Id: Ib4c83ffdcc5dd6eb7bb34c07386cf2ab61dcae57 GitHub-Last-Rev: fac9261 GitHub-Pull-Request: #25089 Reviewed-on: https://go-review.googlesource.com/109362 Run-TryBot: Brad Fitzpatrick <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Brad Fitzpatrick <[email protected]>
'%SystemRoot%/System32/chcp.com' is a tool on Windows that is used to change the active code page in the console. 'go test os/exec' can fail with: "'chcp' is not recognized as an internal or external command" The test uses a custom PATH variable but does not include '%SystemRoot%/System32'. Always append that to PATH. Updates #24709 Change-Id: I1ab83b326072e3f0086b391b836234bcfd8a1fb7 GitHub-Last-Rev: fb93052 GitHub-Pull-Request: #25088 Reviewed-on: https://go-review.googlesource.com/109361 Run-TryBot: Brad Fitzpatrick <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Brad Fitzpatrick <[email protected]>
Does it happen often enough for you to debug? Can you see what the problem is?
What do you mean by "infinite loop" ? I suspect no one runs this command. all.bat runs go test -short cmd/go so 'go test cmd/go' might take a while, but if takes 10-20 minutes, please create new issue and report which test is too long (by adding -v flag) and we will adjust tests.
What I said before. Create new issue for that, and someone will adjust tests to make it pass. Thank you. Alex |
On 27 April 2018 at 13:17, Alex Brainman ***@***.***> wrote:
this one doesn't happen all the time:
Does it happen often enough for you to debug? Can you see what the problem
is?
i didn't have the time to debug it.
maybe next week, but i'm traveling too.
it just happened again from `all.bat`:
```
--- FAIL: TestLinkXImportPathEscape (0.44s)
go_test.go:4396: running testgo [build -o ./linkx.exe -ldflags
-X=my.pkg
.Text=linkXworked my.pkg/main]
go_test.go:4405: remove ./linkx.exe: Access is denied.
FAIL
FAIL cmd/go 101.878s
```
and also i'm noticing an infinite loop if i run:
go test cmd/go
What do you mean by "infinite loop" ? I suspect no one runs this command.
all.bat runs
go test -short cmd/go
so 'go test cmd/go' might take a while, but if takes 10-20 minutes, please
create new issue and report which test is too long (by adding -v flag) and
we will adjust tests.
"infinite loop" - i though the tests are never ending at first, but i guess
they just take a lot of time.
*** Test killed: ran too long (10m0s).
What I said before. Create new issue for that, and someone will adjust
tests to make it pass.
will do.
thanks.
|
closing in favor of #25300 |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version devel +e8aa9a53 Thu Apr 5 16:22:39 2018 +0000 windows/amd64
latest master at the time.
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?OS:
Microsoft Windows [Version 6.1.7601]
(Windows 7)CPU: Intel i3-2120
What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
What did you expect to see?
no test errors
What did you see instead?
test related errors
full log:
https://pastebin.com/gqhbAWh2
additional information:
python -V
Python 2.7.3
gcc -v
gcc version 5.1.0 (tdm64-1)
no antivirus software running on the machine ATM.
comments:
chcp
works, which i can verify by this small program:calling
exec.Command("cmd", "/c", "chcp")
also works.i haven't looked at the
gdb
related failures.report requested by @alexbrainman
The text was updated successfully, but these errors were encountered: