-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
x/sys/windows: TestCommandLineRecomposition failures #58817
Comments
Found new dashboard test flakes for:
2023-02-28 18:48 windows-amd64-longtest sys@a6bfb89d go@70efe9f7 x/sys/windows.TestCommandLineRecomposition (log)
|
...intriguing. This is a randomized test added in CL 319229 (attn @zx2c4 @alexbrainman). Looks like it uncovered a bug. (On a side note, perhaps it should be converted to a fuzz test?) (CC @golang/windows) |
Agree. Also note that we need to fix both copies of Alex |
Alex |
In triage now, @alexbrainman do you plan to look into this? |
I briefly looked at the code. And the only way for go/src/syscall/syscall_windows.go Lines 41 to 45 in 53c91f9
I did not look at I cannot reproduce the failure by simply running the test. I am not sure what else I can try. So leaving this issue for you @mknyszek to work on. Sorry but I don't have much free time to spend here. Alex |
The test uses randomized input, and is entirely capable of randomly inserting a NUL byte into the string, which will cause the test to fail. Or so it seems to me. CC @zx2c4 who added the test in CL 319229. |
Good point @ianlancetaylor. I completely missed the fact that I think we should adjust What do you think? Alex |
|
Found new dashboard test flakes for:
2023-04-18 17:08 windows-amd64-race sys@2a33a30b go@ecf7e00d x/sys/windows.TestCommandLineRecomposition (log)
|
Change https://go.dev/cl/487695 mentions this issue: |
Found new dashboard test flakes for:
2023-09-15 18:45 windows-arm64-11 sys@c7ff727a go@a56e4969 x/sys/windows.TestCommandLineRecomposition (log)
|
Change https://go.dev/cl/530275 mentions this issue: |
Change https://go.dev/cl/531176 mentions this issue: |
It just occurred to me that the observed limit was almost certainly a side effect of the Go wrapper for CommandLineToArgv (golang/go#63236) rather than a behavior of the system call itself. Updates golang/go#63236. Updates golang/go#58817. Change-Id: Icc9db01f201f54a78044d1c48e0883e098cfb5e5 Cq-Include-Trybots: luci.golang.try:x_sys-gotip-windows-amd64-longtest Reviewed-on: https://go-review.googlesource.com/c/sys/+/531176 LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Auto-Submit: Bryan Mills <bcmills@google.com> Reviewed-by: Quim Muntal <quimmuntal@gmail.com> Reviewed-by: Than McIntosh <thanm@google.com>
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: