From: leonardo.sandoval.gonzalez@linux.intel.com
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/3] On knotty, Make sure bitbake.lock is unlocked before exiting
Date: Tue, 7 Jul 2015 09:45:58 +0000 [thread overview]
Message-ID: <cover.1436261758.git.leonardo.sandoval.gonzalez@linux.intel.com> (raw)
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
Solves issues recently found on the AutoBuilder, where between one build and another the
following log error is seen:
ERROR: Only one copy of bitbake should be run against a build directory
More info on https://bugzilla.yoctoproject.org/show_bug.cgi?id=7941
The following changes since commit b78b1a6bb82fb864f1f857bf7259908d0ed930b5:
tune-i586-nlp: Add new tune file to support Quark/X1000 CPU (2015-07-01 15:40:00 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib lsandov1/PR-Service-selftest-failures-7941
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=lsandov1/PR-Service-selftest-failures-7941
Leonardo Sandoval (3):
cooker.py: Lock/Unlock members function into BBCooker
command.py: Unlock function included into CommandsSync class
knotty.py: Make sure bitbake.lock is unlocked before exiting
bitbake/lib/bb/command.py | 6 ++++++
bitbake/lib/bb/cooker.py | 17 ++++++++++++++---
bitbake/lib/bb/ui/knotty.py | 20 ++++++++++++++++++++
3 files changed, 40 insertions(+), 3 deletions(-)
--
1.8.4.5
next reply other threads:[~2015-07-07 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 9:45 leonardo.sandoval.gonzalez [this message]
2015-07-07 9:45 ` [PATCH 1/3] cooker.py: Lock/Unlock members function into BBCooker leonardo.sandoval.gonzalez
2015-07-07 9:46 ` [PATCH 2/3] command.py: Unlock function included into CommandsSync class leonardo.sandoval.gonzalez
2015-07-07 9:46 ` [PATCH 3/3] knotty.py: Make sure bitbake.lock is unlocked before exiting leonardo.sandoval.gonzalez
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=cover.1436261758.git.leonardo.sandoval.gonzalez@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=bitbake-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