From: richard.purdie@linuxfoundation.org
To: "Yu, Mingli" <mingli.yu@windriver.com>,
openembedded-core@lists.openembedded.org,
luca.ceresoli@bootlin.com
Subject: Re: [OE-core] [PATCH v2 1/7] python3-cryptography: add python3-pytest-benchmark rdepends
Date: Tue, 17 May 2022 09:40:51 +0100 [thread overview]
Message-ID: <d037486615787f0c2f53edf1d2e09688ee8a2e62.camel@linuxfoundation.org> (raw)
In-Reply-To: <20220517081633.2992360-1-mingli.yu@windriver.com>
On Tue, 2022-05-17 at 16:16 +0800, Yu, Mingli wrote:
> From: Mingli Yu <mingli.yu@windriver.com>
>
> The new version introduced below change, so add python3-pytest-benchmark
> to rdepends to fix the gap.
> 496703c8 Refs #7079 -- added basic scaffholding for benchmarks (#7087)
>
> Fixes:
> # ./run-ptest
> Free memory: 31.283 GB
> ERROR: usage: pytest [options] [file_or_dir] [file_or_dir] [...]
> pytest: error: unrecognized arguments: --benchmark-disable
> inifile: /usr/lib/python3-cryptography/ptest/pyproject.toml
> rootdir: /usr/lib/python3-cryptography/ptest
It sounds like we're disabling the benchmarks anyway? :/
Can we not avoid the dependencies some other way?
The patch series as it stands won't build cleanly as there is no
maintainers entry for the new recipes.
Cheers,
Richard
next prev parent reply other threads:[~2022-05-17 8:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 2:13 [PATCH] python3-cryptography: add python3-pytest-benchmark rdepends mingli.yu
2022-05-16 8:45 ` [OE-core] " Luca Ceresoli
2022-05-17 8:16 ` [PATCH v2 1/7] " mingli.yu
2022-05-17 8:16 ` [PATCH 2/7] python3-pytest-benchmark: move from meta-python mingli.yu
2022-05-17 8:16 ` [PATCH 3/7] python3-aspectlib: " mingli.yu
2022-05-17 8:16 ` [PATCH 4/7] python3-py-cpuinfo: " mingli.yu
2022-05-17 8:16 ` [PATCH 5/7] python3-fields: " mingli.yu
2022-05-17 8:16 ` [PATCH 6/7] python3-process-tests: " mingli.yu
2022-05-17 8:16 ` [PATCH 7/7] python3-tornad: " mingli.yu
2022-05-17 15:33 ` [OE-core] " Khem Raj
2022-05-17 8:40 ` richard.purdie [this message]
2022-05-17 10:22 ` [PATCH v3] python3-cryptography: remove --benchmark-disable option mingli.yu
2022-06-08 9:31 ` mingli.yu
2022-06-09 7:06 ` [OE-core] " Luca Ceresoli
2022-06-13 7:30 ` [PATCH v4] python3-cryptography: remove test_x509.py mingli.yu
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=d037486615787f0c2f53edf1d2e09688ee8a2e62.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=luca.ceresoli@bootlin.com \
--cc=mingli.yu@windriver.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