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 1/8] test/py/requirements.txt: update coverage
Date: Sat, 5 Apr 2025 20:46:19 +0200 [thread overview]
Message-ID: <20250405184626.22377-2-hs@denx.de> (raw)
In-Reply-To: <20250405184626.22377-1-hs@denx.de>
From: Heiko Schocher <hs@nabladev.com>
-coverage==6.2
+coverage==7.6.2
Signed-off-by: Heiko Schocher <hs@nabladev.com>
Signed-off-by: Heiko Schocher <hs@denx.de>
---
test/py/requirements.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/test/py/requirements.txt b/test/py/requirements.txt
index 75760f96e5..9b15e97f51 100644
--- a/test/py/requirements.txt
+++ b/test/py/requirements.txt
@@ -1,7 +1,7 @@
atomicwrites==1.4.1
attrs==19.3.0
concurrencytest==0.1.2
-coverage==6.2
+coverage==7.6.2
extras==1.0.0
filelock==3.0.12
fixtures==3.0.0
--
2.20.1
next prev parent reply other threads:[~2025-04-05 18:46 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 ` Heiko Schocher [this message]
2025-04-05 18:46 ` [PATCH v1 2/8] tools/buildman/requirements.txt: update coverage 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 ` [PATCH v1 4/8] test/py/requirements.txt: remove unittest2 and testtools Heiko Schocher
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-2-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