RESOLVED WONTFIX 83226
build-webkit | filter-build-webkit returns success even when build-webkit fails
https://bugs.webkit.org/show_bug.cgi?id=83226
Summary build-webkit | filter-build-webkit returns success even when build-webkit fails
Eric Seidel (no email)
Reported 2012-04-04 15:12:16 PDT
build-webkit | filter-build-webkit returns success even when build-webkit fails Fixing this would make my life easier. :) I would like to be able to use: build-webkit | filter-build-webkit && run-webkit-tests
Attachments
Eric Seidel (no email)
Comment 1 2012-04-04 15:12:29 PDT
Hmm... Looks like bug 70080 attempted this before.
Eric Seidel (no email)
Comment 2 2012-04-04 15:12:47 PDT
Another solution would be to just integrate filter-build-webkit into build-webkit :)
Dean Jackson
Comment 3 2012-04-04 15:13:45 PDT
(In reply to comment #2) > Another solution would be to just integrate filter-build-webkit into build-webkit :) Yeah. Pass --filter-build or something.
Eric Seidel (no email)
Comment 4 2012-04-04 15:17:35 PDT
mdelany doesn't seem to have a bugzilla account or I would have CC'd him. :) http://trac.webkit.org/log/trunk/Tools/Scripts/filter-build-webkit
Blaze Burg
Comment 5 2016-01-06 10:26:39 PST
There is nothing that we can change in filter-build-webkit (a perl script) to get the exit status from an earlier command in the pipeline. There are two ways to get this behavior without changing any scripts: 1. In bash, use cmd1 |& cmd2 (shortcut for cmd1 2>&1 | cmd2). Then the BUILD FAILED detection will work. 2. In bash, run 'set -o pipefail'. This uses the leftmost non-zero return code from a pipeline rather than the rightmost program. In the future, build-webkit should incorporate filter-build-webkit. If filter-build-webkit were running build commands, then it could capture and propagate the exit codes from its child processes.
Note You need to log in before you can comment on or make changes to this bug.