Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: bitbake exit codes?
Date: Mon, 14 Feb 2011 08:12:47 +0100	[thread overview]
Message-ID: <4D58D5EF.6000807@dresearch.de> (raw)

While setting up Jenkins/Hudson jobs for the testing-release-2011.03 branch based on the testscript.sh from the contrib subdir i hit the following problem.

bitbake (1.10.2) finally reports "NOTE: Task Summary: Attempted 1217 tasks of which 0 didn't need to be rerun and 0 failed.". So it seems that the build was successful. But bitbake did not return 0 but 1. So Jenkins marks the build as failed.

I guess the exit code 1 is coming from some QA Issues. How do we handle that if if my guess is right?

Do we mark such a build run as successful in our test matrix?

Has bitbake a defined set of exit codes that we can evaluate in the testscript.sh?

Steffen

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@DResearch.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058




             reply	other threads:[~2011-02-14  7:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14  7:12 Steffen Sledz [this message]
2011-02-14  8:11 ` bitbake exit codes? Frans Meulenbroeks
2011-02-14 10:39   ` bitbake exit codes? (testing-release-2011.03 build results) Steffen Sledz
2011-02-14 13:25     ` Frans Meulenbroeks
2011-02-14 13:28       ` Frans Meulenbroeks
2011-02-14 15:01     ` Tom Rini

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=4D58D5EF.6000807@dresearch.de \
    --to=sledz@dresearch.de \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox