[Webkit-unassigned] [Bug 194816] test262-runner ends with SIGPIPE signal

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=194816

--- Comment #2 from Diego Pino <dpino at igalia.com> ---
Explanation of the patch.

I debugged the issue using 'Carp::Trace'. I captured SIGPIPE signals and printed out a trace. I got the following output:

```
Test262::Runner::main [3]
        scalar - new stash
        /home/slave/webkitgtk/gtk-linux-64-release/build/Tools/Scripts/test262/Runner.pm line 122
Test262::Runner::(eval) [2]
        scalar - no new stash
        /home/slave/webkitgtk/gtk-linux-64-release/build/Tools/Scripts/test262/Runner.pm line 416
Test262::Runner::__ANON__ [1]
        scalar - new stash
        /home/slave/webkitgtk/gtk-linux-64-release/build/Tools/Scripts/test262/Runner.pm line 416
```

This pattern occurred several times in the output.

IIRC, a SIGPIPE happens when attempting to write on a closed pipe. In the case of the suspecting line (416), I think what is happening if that child is trying to write on a closed socket (the parent was closed right before that loop). In any case, it seems to me this block of code is redundant, so I removed it.

After applying the patch, `test262-runner --release` runs just fine (exit status is 0).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190219/ef3ef507/attachment.html>