Skip to content
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

debugview++test 'LineBufferTest2' locks up the GUI temporarily #12

Open
janwilmans opened this issue Dec 7, 2016 · 2 comments
Open

Comments

@janwilmans
Copy link

the test outputs 3x17.000 lines during the test, this completely locks up the UI while the test is running.
There is also another symptom visible:
a std::cout << msg << std::endl is not 'flushing' until the end of the test, so there is now way to tell the user to wait

@janwilmans
Copy link
Author

I think its a feature/bug that was always in boosttestui (large amounts of data in the logwindow seem to cause delays).
However, the behaviour of BOOST_TEST() seems to have changed:

0.014863 DebugView++Test.cpp(276): info: check line.time == 42.0 has passed
0.014870 DebugView++Test.cpp(277): info: check line.systemTime.dwLowDateTime == 43 has passed
0.014878 DebugView++Test.cpp(278): info: check line.systemTime.dwHighDateTime == 44 has passed

it is outputting a line now for every PASSED test... this seems to me, to be irrelevant information (I would mainly want to know about failures, not passed tests :), aside from the summery of course

@janwilmans
Copy link
Author

I was probably wrong, the problem is maybe that the test is started with --loglevel=all with outputs A LOT of stuff, and this does not seems to go well with the log-window (maybe every single message is handled on the UI thread?

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

No branches or pull requests

1 participant