Issue 4337: Layout tests on Windows don't collect stderr http://code.google.com/p/chromium/issues/detail?id=4337
New issue report by [EMAIL PROTECTED]: Although test_shell_thread.py tells the subprocess module to pipe stderr with stdout, on Windows it looks like it's being dropped on the floor instead. This is hiding possible problems. I tried a fix that pulled stderr out into its own pipe and read and printed it out after receiving #EOF on stdout, but this led to instability on the buildbots. The test harness would hang on most, but not all, runs. I haven't looked closely into what was going on or whether there was a specific subset of tests that cause problems. At first, the patch caused Python to abort with a MemoryError, which I fixed by not collecting empty stderr lines. Then one test did hang more consistently, so I added it to tests_fixable with a SKIP. Then I tried commenting out the lines that were collecting and printing stderr. But none of that helped, so I rolled back the original change completely. History: http://codereview.chromium.org/8778 http://codereview.chromium.org/10611 http://codereview.chromium.org/10614 http://codereview.chromium.org/10616 Issue attributes: Status: Assigned Owner: [EMAIL PROTECTED] CC: [EMAIL PROTECTED], [EMAIL PROTECTED] Labels: Type-Bug Pri-2 OS-All Area-DevTools Tests -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to chromium-bugs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
