From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Yu, Mingli" <mingli.yu@windriver.com>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v3] python3-cryptography: remove --benchmark-disable option
Date: Thu, 9 Jun 2022 09:06:04 +0200 [thread overview]
Message-ID: <20220609090604.067b8258@booty> (raw)
In-Reply-To: <20220608093120.1532299-1-mingli.yu@windriver.com>
Hi,
On Wed, 8 Jun 2022 17:31:20 +0800
"Yu, Mingli" <mingli.yu@windriver.com> wrote:
> From: Mingli Yu <mingli.yu@windriver.com>
>
> The new version introduced below change, so remove the option
> to avoid python3-pytest-benchmark 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
>
> Remove the case test_x509.py to avoid below failure:
> file /usr/lib64/python3-cryptography/ptest/tests/bench/test_x509.py, line 9
> def test_aki_public_bytes(benchmark):
> > fixture 'benchmark' not found
> > available fixtures: backend, cache, capfd, capfdbinary, caplog, capsys, capsysbinary, disable_rsa_checks, doctesty
> > use 'pytest --fixtures [testpath]' for help on them.
>
> Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
I currently see all patches at v1, and a patch has one v2 and two v3s.
This is confusing and chances are whatever I take for testing will be
wrong.
Could you please send the entire series as v4, updated at the
current state of the art and with all the changes discussed in previous
replies?
Thanks!
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-06-09 7:06 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 ` [OE-core] [PATCH v2 1/7] python3-cryptography: add python3-pytest-benchmark rdepends richard.purdie
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 ` Luca Ceresoli [this message]
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=20220609090604.067b8258@booty \
--to=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