Summary: | run-jsc-stress-tests doesn't eagerly report test failures when using the shell runner | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Mark Hahnenberg <mhahnenberg> | ||||
Component: | JavaScriptCore | Assignee: | Mark Hahnenberg <mhahnenberg> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | commit-queue, fpizlo | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Mark Hahnenberg
2014-03-07 08:57:44 PST
Created attachment 226137 [details]
Patch
Comment on attachment 226137 [details]
Patch
r=me
Comment on attachment 226137 [details] Patch Clearing flags on attachment: 226137 Committed r165274: <http://trac.webkit.org/changeset/165274> All reviewed patches have been landed. Closing bug. This made all error reporting super ugly because of the way that "1>&2" was added. Apparently when you add it without a space after the prefixCommand(), it somehow tells shell to duplicate the output. Don't ask why. Anyway, the moral of the story is: if you make changes to error handling in run-jsc-stress-tests you should test the error handling by locally breaking a test. I'll fix it. |