When WebKitTestRunner doesn't get a response to IPC, it dumps "#PROCESS UNRESPONSIVE" to stderr. When run-webkit-tests sees that, it for some reason reports the test as crashing.
It seems like there may have been ports that couldn't detect crashes (chromium perhaps?). However, detecting crashes is a core WebKit2 behavior, and if that doesn't work, we shouldn't be lying about that in run-webkit-tests.
There are practical cases where IPC takes a long time and triggers this - e.g. with ASan builds, despite them now having a higher IPC timeout. Generating accurate output will help reduce confusion.
Created attachment 244211 [details]
Comment on attachment 244211 [details]
View in context: https://bugs.webkit.org/attachment.cgi?id=244211&action=review
> + fputs("#CRASHED - %s\n", webProcessName(), stderr);
This needs to be changed to fprintf.
Looking into webkitpy failures - I forgot to run these tests. We really need to have them on EWS.
Fixed the failures in r178118.