-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Test printing refinement #18739
Comments
The table's also overly wide for default console widths so we should try to squeeze it down, maybe make the header wrapped to 2 rows with each title narrower, or drop the percent column? #17165 (comment) |
It should be possible to print row-by-row as each The widest columns are |
Yeah good abbreviations. Which worker the tests ran on when they execute in parallel is useful info to show, we may want to make room for it in the table. |
|
This remains incomplete. @kshyatt any intention of revisiting this? Cases like https://travis-ci.org/JuliaLang/julia/jobs/173755550 give no indication of what line number within the spawn test actually failed. |
@tkelman sorry I have been totally swamped with work. I will see if I can take a look today or tomorrow. |
Now results come in one by one and print their memory/timing data as they come in. We will no longer print rss results twice. Also, each test now prints which worker it ran on.
Now results come in one by one and print their memory/timing data as they come in. We will no longer print rss results twice. Also, each test now prints which worker it ran on.
Fix #18739, Make testset results printing better
Now results come in one by one and print their memory/timing data as they come in. We will no longer print rss results twice. Also, each test now prints which worker it ran on.
followup to #17165 / #18738, cc @kshyatt
right now the base tests are printing both old as-you-go info, in addition to a new table so it looks like
I propose we get rid of the old style and attempt to make the table just print new rows as they come in, if that's possible. The maxrss numbers are the same so it's duplicated information.
Additional printing-related followup from #17165 (comment), printing of
@test true
or@test 1==1
should be adjusted to not bother showingExpression: nothing
now that passing tests don't save the input expressions any more.The text was updated successfully, but these errors were encountered: