[Scons-users] Surprising behavior with pipes
Gary Granger
granger at ucar.edu
Wed Sep 20 12:51:46 EDT 2017
When I have had to use pipelines in actions, I have had to set pipefail
explicitly, eg:
"set -o pipefail; %s 2>&1 | ${ASAN_FILTER}" % (command)
On 09/20/2017 08:39 AM, Andrew C. Morrow wrote:
>
> I noticed to my surprise recently that an Action that uses a pipeline
> doesn't fail if one of the subcommands fails:
>
> https://github.com/mongodb/mongo/blob/master/site_scons/site_tools/abilink.py#L66
>
> I had a buggy version of abidw installed, and when it crashed with an
> assertion, the SCons build did not terminate with an error. Instead
> the partial output up to the crash was consumed by md5 and used as the
> result.
>
> Is there a way to ask SCons to enforce pipefail?
>
More information about the Scons-users
mailing list