Andrew, way back when I implemented this feature in bug 1526445, you requested that I use `structuredLogger.deactivateBuffering()` and `structuredLogger.activateBuffering()` respectively when we skip a task. This happens to cause all other subsequent test results to be eaten and not logged to the console (and possibly in automation too). The test totals reported at the end still show the correct numbers, though, and when using `dump` everywhere instead of the logger also shows that the tasks are being run as expected. When I remove the buffering pausing code, everything works as expected, which makes me wonder: can I simplify things and remove the code?
Bug 1526445 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Andrew, way back when I implemented this feature in bug 1380470, you requested that I use `structuredLogger.deactivateBuffering()` and `structuredLogger.activateBuffering()` respectively when we skip a task. This happens to cause all other subsequent test results to be eaten and not logged to the console (and possibly in automation too). The test totals reported at the end still show the correct numbers, though, and when using `dump` everywhere instead of the logger also shows that the tasks are being run as expected. When I remove the buffering pausing code, everything works as expected, which makes me wonder: can I simplify things and remove the code?