-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/test2json: misparses subtest names with : in them #23920
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
Comments
It turns out that golang/go#23920 hits us in veneur: Since these subtest names contain the : character, test2json never lists the test as having passed. Let's be friendly to good tools!
It turns out that golang/go#23920 hits us in veneur: Since these subtest names contain the : character, test2json never lists the test as having passed. Let's be friendly to good tools!
Change https://golang.org/cl/98445 mentions this issue: |
It turns out that golang/go#23920 hits us in veneur: Since these subtest names contain the : character, test2json never lists the test as having passed. Let's be friendly to good tools!
@bradfitz any chance to backport it to Go 1.10.x? |
@zolotov, it's not clear it meets the bar for our backport policy, but it's also small and trivial, with no great user workaround, so ... maybe? @andybons, @ianlancetaylor? |
I'm on the fence. It doesn't appear to be a regression (correct me if I'm wrong) but also doesn't have a user workaround and is fairly small as Brad said. I give a soft yes. Will leave to @ianlancetaylor to make final decision. |
Backporting is OK with me. |
@gopherbot please backport |
Backport issue(s) opened: #25027 (for 1.10), #25028 (for 1.9). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://golang.org/wiki/MinorReleases. |
Backport issue(s) opened: #25027 (for 1.10), #25029 (for 1.9). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://golang.org/wiki/MinorReleases. |
Closing this in favor of #25027 as the issue is fixed in master. (EDIT: It was already closed, as I only noticed while clicking "Reopen and comment" -.-) |
go1.10 has a bug in its test2json tool that causes test names with colons in them to be misparsed (golang/go#23920). This was causing the nightly stress issue poster to incorrectly post dozens of issues about tests that had not actually failed. Upgrade the builder to go1.10.3, which includes a fix for the test2json tool. Fix cockroachdb#27498. Release note: None
27597: build: upgrade to go1.10.3 r=tschottdorf a=benesch go1.10 has a bug in its test2json tool that causes test names with colons in them to be misparsed (golang/go#23920). This was causing the nightly stress issue poster to incorrectly post dozens of issues about tests that had not actually failed. Upgrade the builder to go1.10.3, which includes a fix for the test2json tool. Fix #27498. Release note: None Co-authored-by: Nikhil Benesch <[email protected]>
What version of Go are you using (
go version
)?go version go1.10 darwin/amd64
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?What did you do?
This test file makes
go test -json ./
produce very weird output onAction: "run"
:What did you expect to see?
JSON containing consistent references to the subtest names.
What did you see instead?
This produces mostly-correct looking output, but only mostly.
Here's the entire json dump in case you're interested
And here are the bits that are concerning:
Note the weird
"Action"
name, and the bad"Test"
entryIt looks like the action name gets extracted greedily, and everything in the test name up to the first
:
gets dragged in. Other stuff like"pass"
makes it through ok, but this seems like a bug.The text was updated successfully, but these errors were encountered: