[OE-core] [RFC][PATCH] Resolve an issue when using pipes to process data

[Mark Hatle]

I'm sending this as an RFC.  I know the patch works, but I think it highlights
a potentially larger issue in the system.

If we're processing data using shell pipes, the return code of a failed
process may end up being lost -- avoiding the regular error capture when
bitbake runs a task.

In this particular case, while working to fix a bug in pseudo we made an
error condition fatal (triggered an abort()), but buildhistory kept on
processing ignoring any issues had occurred.

Breaking up the processing into steps, things that 'could fail', and later
processing steps that shouldn't fail will give us more of an opportunity to
identify failures in the future and deal with them in a quicker manner,
then having to investigate log files for messages.

I'm suspecting we should run a janitor exercise against oe-core looking for
similar situations where we might be piping the data and potentially losing
return codes in the process.

Comments?

Mark Hatle (1):
  buildhistory.bbclass: Break up the find to catch failures

 meta/classes/buildhistory.bbclass | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

-- 
2.5.0