[yocto] [PATCH] fetch2/__init_.py removed bb.error which caused exit code 1
Paulo Neves
ptsneves at gmail.com
Tue Jul 18 06:43:54 PDT 2017
http://lists.openembedded.org/pipermail/openembedded-core/2012-September/069448.html
Workaround to avoid exit 1 status.
The reason it happens is that there are 2 missions
the state cache uses the normal fetcher to get
its's stuff and it is acceptable for it to fail.
On the other hand it is not acceptable for fetch
to fail.
In it's code the state cache code catches the exception that the
fetcher launches and discards. The problem
is that before this exception is caught it prints
a bb.error and bb.error prints something and
continues on like no problem happened. but marks
the exit code as 1 which is a disaster.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Workaround-to-avoid-exit-1-status.patch
Type: text/x-patch
Size: 1498 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170718/50dd7a07/attachment.bin>
More information about the yocto
mailing list