U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Heiko Schocher <hs@nabladev.com>, Heiko Schocher <hs@denx.de>,
	Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>
Subject: [PATCH v1 4/8] test/py/requirements.txt: remove unittest2 and testtools
Date: Sat,  5 Apr 2025 20:46:22 +0200	[thread overview]
Message-ID: <20250405184626.22377-5-hs@denx.de> (raw)
In-Reply-To: <20250405184626.22377-1-hs@denx.de>

From: Heiko Schocher <hs@nabladev.com>

unittest2 and testtools leads in:

Collecting argparse (from unittest2>=1.0.0->testtools==2.3.0->-r /builds/u-boot/custodians/u-boot-i2c/tbottesting/../test/py/requirements.txt (line 26))
  Downloading argparse-1.4.0-py2.py3-none-any.whl.metadata (2.8 kB)

which breaks pytest 6.2.5 with

  File "/home/uboot/.local/lib/python3.10/site-packages/_pytest/config/argparsing.py", line 381, in __init__
    argparse.ArgumentParser.__init__(
TypeError: ArgumentParser.__init__() got an unexpected keyword argument 'allow_abbrev'

Signed-off-by: Heiko Schocher <hs@nabladev.com>
Signed-off-by: Heiko Schocher <hs@denx.de>
---

 test/py/requirements.txt | 2 --
 1 file changed, 2 deletions(-)

diff --git a/test/py/requirements.txt b/test/py/requirements.txt
index 22315b4ed5..26412ac0b3 100644
--- a/test/py/requirements.txt
+++ b/test/py/requirements.txt
@@ -23,8 +23,6 @@ python-subunit==1.3.0
 requests==2.32.3
 setuptools==70.3.0
 six==1.16.0
-testtools==2.3.0
 traceback2==1.4.0
-unittest2==1.1.0
 wcwidth==0.1.7
 zipp==3.19.2
-- 
2.20.1


  parent reply	other threads:[~2025-04-05 18:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-05 18:46 [PATCH v1 0/8] This series introduces U-Boot tests with tbot on real hardware Heiko Schocher
2025-04-05 18:46 ` [PATCH v1 1/8] test/py/requirements.txt: update coverage Heiko Schocher
2025-04-05 18:46 ` [PATCH v1 2/8] tools/buildman/requirements.txt: " Heiko Schocher
2025-04-05 18:46 ` [PATCH v1 3/8] test/py/requirements.txt: increase filelock version Heiko Schocher
2025-04-05 18:46 ` Heiko Schocher [this message]
2025-04-05 18:46 ` [PATCH v1 5/8] test: increase timeouts Heiko Schocher
2025-04-05 18:46 ` [PATCH v1 6/8] [RFC] CI: add U-Boot testing on real HW with tbot Heiko Schocher
2025-04-05 18:46 ` [PATCH v1 7/8] .gitlab-ci.yml: add tbot-lab Heiko Schocher
2025-04-05 18:46 ` [PATCH v1 8/8] scripts: add helper for getting infos from your patchwork ToDo list Heiko Schocher

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=20250405184626.22377-5-hs@denx.de \
    --to=hs@denx.de \
    --cc=hs@nabladev.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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