Something is wrong with the test framework such that it stops reading and processing data from the process after the process has pushed a large amount of data in.
This is most obvious in the test escapeCursorDown_pastMargin_withScrollBack where there are hacks to get that test to pass most of the time, but notably not without debug mode on.
Probably some buffer is getting full and then things are getting gummed up. Sometimes writing again later fixes things.
It turns out that it wasn't that the test harness stopped processing data, but that the scroll_down function was broken. I've fixed that in the previous commit.
Something is wrong with the test framework such that it stops reading and processing data from the process after the process has pushed a large amount of data in. This is most obvious in the test escapeCursorDown_pastMargin_withScrollBack where there are hacks to get that test to pass most of the time, but notably not without debug mode on. Probably some buffer is getting full and then things are getting gummed up. Sometimes writing again later fixes things.
Date: 2014-03-23 03:41:26
User: travisb
Another test which seems to suffer often from this bug is test_escapeCursorUp_pastMargin_noScrollBack
Date: 2014-03-27 04:40:49
User: travisb
It turns out that it wasn't that the test harness stopped processing data, but that the scroll_down function was broken. I've fixed that in the previous commit.