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 HashValidateFailure errors in RunQueueExecuteScenequeue
Date: Wed, 27 Aug 2014 13:51:38 +0100	[thread overview]
Message-ID: <1409143898.5772.46.camel@ted> (raw)
In-Reply-To: <6f9c2a0b17e91a37bc1083c799c3820f50bdf926.1409140298.git.hongxu.jia@windriver.com>

On Wed, 2014-08-27 at 19:54 +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 add exception HashValidateFailure for this specific error.
> 
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
>  bitbake/lib/bb/runqueue.py | 17 +++++++++++++++--
>  1 file changed, 15 insertions(+), 2 deletions(-)
> 
> diff --git a/bitbake/lib/bb/runqueue.py b/bitbake/lib/bb/runqueue.py
> index e13dc57..b48b02b 100644
> --- a/bitbake/lib/bb/runqueue.py
> +++ b/bitbake/lib/bb/runqueue.py
> @@ -1046,7 +1046,15 @@ class RunQueue:
>                  self.state = runQueueComplete
>              else:
>                  self.start_worker()
> -                self.rqexe = RunQueueExecuteScenequeue(self)
> +                try:
> +                    self.rqexe = RunQueueExecuteScenequeue(self)
> +                except bb.runqueue.HashValidateFailure:
> +                    # While HashValidateFailure, we need exit the normal build.
> +                    logger.error("Hash validatation failed in RunQueueExecuteScenequeue")
> +                    self.state = runQueueComplete
> +                except:
> +                    logger.error("RunQueueExecuteScenequeue init failed")
> +                    raise
>  
>          if self.state in [runQueueSceneRun, runQueueRunning, runQueueCleanUp]:
>              self.dm.check(self)
> @@ -1821,7 +1829,10 @@ class RunQueueExecuteScenequeue(RunQueueExecute):
>                  sq_task.append(task)
>              call = self.rq.hashvalidate + "(sq_fn, sq_task, sq_hash, sq_hashfn, d)"
>              locs = { "sq_fn" : sq_fn, "sq_task" : sq_taskname, "sq_hash" : sq_hash, "sq_hashfn" : sq_hashfn, "d" : self.cooker.data }
> -            valid = bb.utils.better_eval(call, locs)
> +            try:
> +                valid = bb.utils.better_eval(call, locs)
> +            except:
> +                raise bb.runqueue.HashValidateFailure()

How about:

except Exception as e:
	logger.error("Hash validation failed in RunQueueExecuteScenequeue %s" % str(e))
        raise BBHandledException

Raising the HandledException error should shut down the system
gracefully from there. Adding a custom exception here doesn't help much
other than warning about the exact point of failure as we can do that in
the logger.error message.

I think if you made this:

except Exception as e:
	logger.critial("Hash validation failed in RunQueueExecuteScenequeue %s" % str(e))

then we'd not even need to BBHandledException as logger.critical does
that internally but I could be wrong, I'm going from memory.

Cheers,

Richard


>              valid_new = stamppresent
>              for v in valid:
> @@ -2003,6 +2014,8 @@ class TaskFailure(Exception):
>      def __init__(self, x):
>          self.args = x
>  
> +# Exception raised for a hash validation error
> +class HashValidateFailure(Exception): pass
>  
>  class runQueueExitWait(bb.event.Event):
>      """




      reply	other threads:[~2014-08-27 12:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 11:54 [PATCH V3 0/1] bitbake: runqueue: catch HashValidateFailure errors in RunQueueExecuteScenequeue Hongxu Jia
2014-08-27 11:54 ` [PATCH 1/1] " Hongxu Jia
2014-08-27 12:51   ` 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=1409143898.5772.46.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