Skip to content

Conversation

@sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Nov 10, 2025

Now the parallel test suite now longer needs its own reporting logic it can just share use the existing Runner/Result which now supports the color and single long output formats.

By default we now buffer test output and use the single line test runner. Adding -v will disabled this and give multi-line non-buffered output. Adding another -v will enable logging in the test framework (same as setting EMTEST_VERBOSE)

@sbc100 sbc100 requested review from juj and kripken and removed request for kripken November 10, 2025 17:47
@sbc100
Copy link
Collaborator Author

sbc100 commented Nov 10, 2025

Replaced #25752

@sbc100
Copy link
Collaborator Author

sbc100 commented Nov 10, 2025

shot

@sbc100 sbc100 force-pushed the SingleLineTestResult_part2 branch 2 times, most recently from 77cd236 to c447e52 Compare November 10, 2025 18:28
@sbc100 sbc100 force-pushed the SingleLineTestResult_part2 branch 2 times, most recently from a9f51e3 to 8b8c0bc Compare November 11, 2025 00:13
# Format the line so that it fix within the terminal width, unless it's less then min_len
def writeStatus(self, test, msg, color, line_pos):
# Becuse the message can include the skip reason (which can be very long somtimes), truncate it
# to a reasonable length to avoid exceeding ling length.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# to a reasonable length to avoid exceeding ling length.
# to a reasonable length to avoid exceeding line length.

@brendandahl
Copy link
Collaborator

Looks nice!
I don't think we need to fix this yet, but one thing I notice when running with -j1 is it will show the last test that has passed e.g. (test_core.core0.test_promise_await_jspi) ... ok instead of the currently running test.

@sbc100
Copy link
Collaborator Author

sbc100 commented Nov 11, 2025

Looks nice! I don't think we need to fix this yet, but one thing I notice when running with -j1 is it will show the last test that has passed e.g. (test_core.core0.test_promise_await_jspi) ... ok instead of the currently running test.

Yes thats is how the parallel test runner works for sure. We don't overwrite the old line until we have new test result.

For the -j1 runner I agree we could maybe show the current tests.. but then you would also never see the .. ok since that would be immediately replaced with the new test name following by ...

Now the parallel test suite now longer needs its own reporting logic
it can just share use the existing Runner/Result which now supports
the color and single long output formats.

By default we now buffer test output and use the single line test
runner.  Adding `-v` will disabled this and give multi-line non-buffered
output.  Adding another `-v` will enable logging in the test framework
(same as setting EMTEST_VERBOSE)
@sbc100 sbc100 force-pushed the SingleLineTestResult_part2 branch from 8b8c0bc to 8e8dabb Compare November 11, 2025 00:46
@sbc100 sbc100 merged commit a500942 into emscripten-core:main Nov 11, 2025
2 of 15 checks passed
@sbc100 sbc100 deleted the SingleLineTestResult_part2 branch November 11, 2025 00:46
@brendandahl
Copy link
Collaborator

I'd be fine not seeing the 'ok', it's more helpful to me to see if a test is taking a long time or hung.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants