From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 01/20] oe-selftest: add a test for recipes without maintainers
Date: Thu, 1 Feb 2018 20:01:51 +0200 [thread overview]
Message-ID: <20180201180210.21652-1-alexander.kanavin@linux.intel.com> (raw)
'bitbake -c checkpkg world' is moved to class initializer to avoid
it being run twice in a row.
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
meta/lib/oeqa/selftest/cases/distrodata.py | 32 +++++++++++++++++++++++++-----
1 file changed, 27 insertions(+), 5 deletions(-)
diff --git a/meta/lib/oeqa/selftest/cases/distrodata.py b/meta/lib/oeqa/selftest/cases/distrodata.py
index 12540adc7d8..dd0760cce93 100644
--- a/meta/lib/oeqa/selftest/cases/distrodata.py
+++ b/meta/lib/oeqa/selftest/cases/distrodata.py
@@ -9,6 +9,12 @@ class Distrodata(OESelftestTestCase):
@classmethod
def setUpClass(cls):
super(Distrodata, cls).setUpClass()
+ feature = 'INHERIT += "distrodata"\n'
+ feature += 'LICENSE_FLAGS_WHITELIST += " commercial"\n'
+
+ cls.write_config(cls, feature)
+ bitbake('-c checkpkg world')
+
@OETestID(1902)
def test_checkpkg(self):
@@ -18,11 +24,6 @@ class Distrodata(OESelftestTestCase):
Product: oe-core
Author: Alexander Kanavin <alexander.kanavin@intel.com>
"""
- feature = 'INHERIT += "distrodata"\n'
- feature += 'LICENSE_FLAGS_WHITELIST += " commercial"\n'
-
- self.write_config(feature)
- bitbake('-c checkpkg world')
checkpkg_result = open(os.path.join(get_bb_var("LOG_DIR"), "checkpkg.csv")).readlines()[1:]
regressed_failures = [pkg_data[0] for pkg_data in [pkg_line.split('\t') for pkg_line in checkpkg_result] if pkg_data[11] == 'UNKNOWN_BROKEN']
regressed_successes = [pkg_data[0] for pkg_data in [pkg_line.split('\t') for pkg_line in checkpkg_result] if pkg_data[11] == 'KNOWN_BROKEN']
@@ -40,3 +41,24 @@ The following packages have been checked successfully for upstream versions,
but their recipes claim otherwise by setting UPSTREAM_VERSION_UNKNOWN. Please remove that line from the recipes.
""" + "\n".join(regressed_successes)
self.assertTrue(len(regressed_failures) == 0 and len(regressed_successes) == 0, msg)
+
+ def test_maintainers(self):
+ """
+ Summary: Test that recipes have a maintainer
+ Expected: All recipes (except a few special static/testing ones) should have a maintainer listed in maintainers.inc file.
+ Product: oe-core
+ Author: Alexander Kanavin <alexander.kanavin@intel.com>
+ """
+ def is_exception(pkg):
+ exceptions = ["packagegroup-", "initramfs-", "systemd-machine-units", "container-image-testpkg", "postinst", "devtool-test-", "selftest-ed", "target-sdk-provides-dummy"]
+ for i in exceptions:
+ if i in pkg:
+ return True
+ return False
+
+ checkpkg_result = open(os.path.join(get_bb_var("LOG_DIR"), "checkpkg.csv")).readlines()[1:]
+ no_maintainer_list = [pkg_data[0] for pkg_data in [pkg_line.split('\t') for pkg_line in checkpkg_result] if pkg_data[14] == '' and not is_exception(pkg_data[0])]
+ msg = """
+The following packages do not have a maintainer assigned to them. Please add an entry to meta/conf/distro/include/maintainers.inc file.
+""" + "\n".join(no_maintainer_list)
+ self.assertTrue(len(no_maintainer_list) == 0, msg)
--
2.15.1
next reply other threads:[~2018-02-01 18:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 18:01 Alexander Kanavin [this message]
2018-02-01 18:01 ` [PATCH 02/20] rpm: update to 4.14.1 Alexander Kanavin
2018-02-01 18:01 ` [PATCH 03/20] rpm: add a patch to help with Docker performance issues Alexander Kanavin
2018-02-01 18:01 ` [PATCH 04/20] openssl: update to 1.0.2n Alexander Kanavin
2018-02-01 18:01 ` [PATCH 05/20] webkitgtk: update to 2.18.6 Alexander Kanavin
2018-02-01 18:01 ` [PATCH 06/20] epiphany: update to 3.26.5.1 Alexander Kanavin
2018-02-01 18:01 ` [PATCH 07/20] p11-kit: take source code from official git Alexander Kanavin
2018-02-01 18:01 ` [PATCH 08/20] libnl: 3.2.29 -> 3.4.0 Alexander Kanavin
2018-02-01 18:01 ` [PATCH 09/20] vala: update to 0.38.6 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 10/20] mpg123: update to 1.25.8 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 11/20] boost: update to 1.66.0 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 12/20] liburcu: update to 0.10.1 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 13/20] btrfs-tools: update to 4.14.1 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 14/20] libwebp: update to 0.6.1 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 15/20] iso-codes: update to 3.77 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 16/20] dtc: upgrade to 1.4.6 Alexander Kanavin
2018-02-04 8:31 ` Burton, Ross
2018-02-04 17:11 ` Khem Raj
2018-02-05 10:42 ` Alexander Kanavin
2018-02-05 14:52 ` Alexander Kanavin
2018-02-05 18:18 ` Khem Raj
2018-02-01 18:02 ` [PATCH 17/20] ffmpeg: update to 3.4.1 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 18/20] iputils: update to 20161105 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 19/20] babeltrace: update to 1.5.4 Alexander Kanavin
2018-02-01 18:02 ` [PATCH 20/20] libmpc: fix upstream version check Alexander Kanavin
2018-02-01 18:33 ` ✗ patchtest: failure for "oe-selftest: add a test for re..." and 19 more Patchwork
2018-02-01 19:21 ` Alexander Kanavin
2018-02-01 20:41 ` [PATCH 01/20] oe-selftest: add a test for recipes without maintainers Paul Eggleton
2018-02-02 10:47 ` 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=20180201180210.21652-1-alexander.kanavin@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@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