| Summary: | [Mac] DRT stderr logging after the test completes gets attributed to the next test | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Simon Fraser (smfr) <simon.fraser> | ||||
| Component: | Tools / Tests | Assignee: | Simon Fraser (smfr) <simon.fraser> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | ap, dfarler, ossy, simon.fraser | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
Created attachment 239816 [details]
Patch
Comment on attachment 239816 [details]
Patch
No ChangeLog?
|
It's hard to use stderr logging when diagnosing DRT issues because stderr output that happens after dump() gets attributed to the next test. This happens because we fputs("#EOF\n", stderr); at the same time we terminate the text output.