From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Paulo Neves <ptsneves@gmail.com>
Cc: Yocto list discussion <yocto@yoctoproject.org>
Subject: Re: [PATCH] fetch2/__init_.py removed bb.error which caused exit code 1
Date: Tue, 18 Jul 2017 11:13:53 -0500 [thread overview]
Message-ID: <1500394433.2753.11.camel@linux.intel.com> (raw)
In-Reply-To: <CAJO0J4hEcDr36TMJtBO+nb8cFMubct7yhUuu4HDjEQyQntvuQw@mail.gmail.com>
you need to send it to openembedde-core mailing list and use
git-send-email to submit your patch. More info on the link below
http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
Leo
On Tue, 2017-07-18 at 15:43 +0200, Paulo Neves wrote:
> 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.
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
prev parent reply other threads:[~2017-07-18 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 13:43 [PATCH] fetch2/__init_.py removed bb.error which caused exit code 1 Paulo Neves
2017-07-18 16:13 ` Leonardo Sandoval [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1500394433.2753.11.camel@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=ptsneves@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.