You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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?
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
The text was updated successfully, but these errors were encountered: