This repository has been archived by the owner on Nov 20, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 46
Parse parallel tests #29
Comments
Any updates on this issue? |
Not yet. I'm doing a big rewrite now to allow streaming (see #41) and will try to add experimental support for parallel tests as well. |
Interesting thing:
^ works, but
does not. |
Sorry, slow going on this one. Will try to speed it up. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Originally BitBucket issue 12
calmh
results.txt
tebeka
This has been discussed before, and this means guessing. I might consider guess with something like --guess-parallel command line switch - patches are welcome :)
calmh
I'm sorry, can you elaborate on what the guessing entails? Do you mean for capturing random stdout output that is not sent through t.Log() and so on? Because all other output and the result status is correctly attached to the test name as far as I can tell, i.e.
In fact, it seems like the "RUN" lines could in principle be ignored and just the status, timestamp and output collected, which will look the same regardless if we're in parallel mode or not...
tebeka
Hmm - seems like I need to think a bit more on this. My concern was that random output will be randomly added to different tests and one PASS will not be match to the right RUN. Looking at the sources of testing packages, there's fmt.Printf("=== RUN %s\n", t.name) which might collide with other tests IMO. I'll re-open and have a look soon-ish.
The text was updated successfully, but these errors were encountered: