All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tim Orling" <ticotimo@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Tim Orling <timothy.t.orling@intel.com>
Subject: [PATCH 0/1] python3: skip tests requiring tools-sdk
Date: Fri, 18 Jun 2021 17:00:10 -0700	[thread overview]
Message-ID: <cover.1624060313.git.timothy.t.orling@intel.com> (raw)

When running python3-ptest for any release since Python 3.8.8 with a minimal
target (e.g. python3-ptest), two test cases will fail:

https://github.com/python/cpython/blob/main/Lib/ctypes/test/test_find.py#L116
https://github.com/python/cpython/blob/main/Lib/ctypes/test/test_find.py#L120

For the autobuilder, these tests have always been running on an image
which set IMAGE_FEATURES to include 'tools-sdk', which includes the
required packagegroup-core-buildessential. Here we add a patch to test
for 'tools-sdk' and skip the tests if it is not present.

The following changes since commit b8723c114b3d9b58d2da1a86d728d176dcbeb4b1:

  nfs-utils: upgrade 2.5.3 -> 2.5.4 (2021-06-17 22:18:41 +0100)

are available in the Git repository at:

  git://push.openembedded.org/openembedded-core-contrib timo/python3-skip-test-find

Tim Orling (1):
  python3: skip tests requiring tools-sdk

 ...pes.test_find-skip-without-tools-sdk.patch | 33 +++++++++++++++++++
 meta/recipes-devtools/python/python3_3.9.5.bb |  1 +
 2 files changed, 34 insertions(+)
 create mode 100644 meta/recipes-devtools/python/python3/0001-test_ctypes.test_find-skip-without-tools-sdk.patch

-- 
2.30.2


             reply	other threads:[~2021-06-19  0:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-19  0:00 Tim Orling [this message]
2021-06-19  0:00 ` [PATCH 1/1] python3: skip tests requiring tools-sdk Tim Orling
2021-06-21 11:59   ` [OE-core] " Alexander Kanavin
2021-06-21 17:30     ` Tim Orling
2021-06-21 20:16       ` Alexander Kanavin
2021-06-21 20:24         ` Tim Orling
2021-06-21 20:50       ` Richard Purdie
2021-06-21 21:10         ` Alexander Kanavin

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.1624060313.git.timothy.t.orling@intel.com \
    --to=ticotimo@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=timothy.t.orling@intel.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 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.