Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: bitbake-devel@lists.openembedded.org, Zhangle.Yang@windriver.com
Subject: Re: [PATCH 1/1] bitbake: runqueue: catch hashvalidate error in RunQueueExecuteScenequeue
Date: Wed, 27 Aug 2014 15:35:13 +0100	[thread overview]
Message-ID: <1409150113.29296.2.camel@ted> (raw)
In-Reply-To: <53FDE832.8060207@windriver.com>

On Wed, 2014-08-27 at 22:16 +0800, Hongxu Jia wrote:
> On 08/27/2014 10:05 PM, Richard Purdie wrote:
> > On Wed, 2014-08-27 at 21:57 +0800, Hongxu Jia wrote:
> >> We need to catch the failure of self.rq.hashvalidate which invoked
> >> in RunQueueExecuteScenequeue, and exit in a normal build.
> >>
> >> So we raise and except bb.BBHandledException for this specific error.
> >>
> >> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> >> ---
> >>   bitbake/lib/bb/runqueue.py | 16 +++++++++++++---
> >>   1 file changed, 13 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/bitbake/lib/bb/runqueue.py b/bitbake/lib/bb/runqueue.py
> >> index e13dc57..59e4188 100644
> >> --- a/bitbake/lib/bb/runqueue.py
> >> +++ b/bitbake/lib/bb/runqueue.py
> >> @@ -1046,7 +1046,14 @@ class RunQueue:
> >>                   self.state = runQueueComplete
> >>               else:
> >>                   self.start_worker()
> >> -                self.rqexe = RunQueueExecuteScenequeue(self)
> >> +                try:
> >> +                    self.rqexe = RunQueueExecuteScenequeue(self)
> >> +                except bb.BBHandledException:
> >> +                    # While hashvalidate failed, we need exit the normal build.
> >> +                    self.state = runQueueComplete
> >> +                except:
> >> +                    logger.error("RunQueueExecuteScenequeue init failed")
> >> +                    raise
> > Do you still need to do this with the change below? runqueue didn't
> > complete, it failed so the state doesn't seem right...
> 
> I want to exit the build peacefully, without too much break messages
> if we don't assign the above complete status, we have messages like this:
> ...
> ERROR: Hash validation failed in RunQueueExecuteScenequeue
> ERROR: An uncaught exception occured in runqueue, please see the failure 
> below:
> ERROR: Running idle function
> Traceback (most recent call last):
>                   try:
>      >                retval = function(self, data, False)
>                       if retval is False:
>                   try:
>      >                retval = rq.execute_runqueue()
>                   except runqueue.TaskFailure as exc:
>    File "/home/jiahongxu/yocto/poky/bitbake/lib/bb/runqueue.py", line 
> 1103, in RunQueue.execute_runqueue():
>               try:
>      >            return self._execute_runqueue()
>               except bb.runqueue.TaskFailure:
>    File "/home/jiahongxu/yocto/poky/bitbake/lib/bb/runqueue.py", line 
> 1049, in RunQueue._execute_runqueue():
>                       self.start_worker()
>      >                self.rqexe = RunQueueExecuteScenequeue(self)
>                       '''
>    File "/home/jiahongxu/yocto/poky/bitbake/lib/bb/runqueue.py", line 
> 1838, in RunQueueExecuteScenequeue.__init__(rq=<bb.runqueue.RunQueue 
> instance at 0x7f509f4bd950>):
>                       logger.error("Hash validation failed in 
> RunQueueExecuteScenequeue %s" % str(e))
>      >                raise bb.BBHandledException()
> 
> BBHandledException
> ...
> 
> Do you have ang ideas about how to exit the build peacefully?

I think bitbake has some deeper issues here we should fix. Firstly, I
think execute_runqueue should really do something like:

        try:
            return self._execute_runqueue()
        except bb.runqueue.TaskFailure:
            raise
        except BaseException as e:
            if not isinstance(e, (SystemExit, BBHandledException)):
                logger.error("An uncaught exception occured in runqueue, please see the failure below:")
            try:
                self.teardown_workers()
            except:
                pass
            self.state = runQueueComplete
            raise

then in buildFileIdle and buildTargetsIdle we should change SystemExit to (SystemExit, BBHandledException) too.

Cheers,

Richard




      reply	other threads:[~2014-08-27 14:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 13:57 [PATCH V4 0/1] bitbake: runqueue: catch hashvalidate error in RunQueueExecuteScenequeue Hongxu Jia
2014-08-27 13:57 ` [PATCH 1/1] " Hongxu Jia
2014-08-27 14:05   ` Richard Purdie
2014-08-27 14:16     ` Hongxu Jia
2014-08-27 14:35       ` Richard Purdie [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=1409150113.29296.2.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Zhangle.Yang@windriver.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=hongxu.jia@windriver.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox