All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH 0/3] Fix bitbake-selftest failures
Date: Tue, 25 Sep 2018 11:07:05 -0400	[thread overview]
Message-ID: <20180925150708.2983-1-mark.hatle@windriver.com> (raw)

The original purpose of this work is to fix the Yocto Project bug 12928.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12928

During that work it was noticed that parse.py was running chdir without
restoring the original path.  Also the layerindexlib cooker test was
using __file__ without fully sanitizing it, so due to the prior issue
it could fail to load the test-case data.

The patch set is availabe on bitbake-contrib on the mgh/12928 branch.

Mark Hatle (3):
  lib/bb/tests/parse.py: Test case was changing chdir
  lib/layerindexlib/tests/cooker.py: Fix topdir to use an absolute
    (real) path
  lib/layerindexlib/tests/restapi.py: Fix test cases when
    BB_SKIP_NETTETS=yes

 lib/bb/tests/parse.py              |   4 +
 lib/layerindexlib/tests/cooker.py  |   2 +-
 lib/layerindexlib/tests/restapi.py | 164 ++++++++++++++++++++-----------------
 3 files changed, 92 insertions(+), 78 deletions(-)

-- 
1.8.3.1



             reply	other threads:[~2018-09-25 15:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25 15:07 Mark Hatle [this message]
2018-09-25 15:07 ` [PATCH 1/3] lib/bb/tests/parse.py: Test case was changing chdir Mark Hatle
2018-09-25 15:07 ` [PATCH 2/3] lib/layerindexlib/tests/cooker.py: Fix topdir to use an absolute (real) path Mark Hatle
2018-09-25 15:18   ` Mark Hatle
2018-09-25 15:07 ` [PATCH 3/3] lib/layerindexlib/tests/restapi.py: Fix test cases when BB_SKIP_NETTETS=yes Mark Hatle

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=20180925150708.2983-1-mark.hatle@windriver.com \
    --to=mark.hatle@windriver.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 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.