From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/pkgcore/pkgdev:main commit in: tests/scripts/
Date: Sat, 19 Nov 2022 17:22:33 +0000 (UTC) [thread overview]
Message-ID: <1668878517.f9c6971a98ed76679e97e08ec25c4ab560921d21.arthurzam@gentoo> (raw)
commit: f9c6971a98ed76679e97e08ec25c4ab560921d21
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 19 17:21:57 2022 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Nov 19 17:21:57 2022 +0000
URL: https://gitweb.gentoo.org/proj/pkgcore/pkgdev.git/commit/?id=f9c6971a
tests/scripts/test_pkgdev_showkw.py: fix NOCOLOR test
Fix the test for systems which predefine NOCOLOR, like in case of ebuild
test environment (by epytest).
Follows: 9714e4785e1ffc56a08f042011b5a966c7520a1f
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
tests/scripts/test_pkgdev_showkw.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tests/scripts/test_pkgdev_showkw.py b/tests/scripts/test_pkgdev_showkw.py
index fe06be9..c611484 100644
--- a/tests/scripts/test_pkgdev_showkw.py
+++ b/tests/scripts/test_pkgdev_showkw.py
@@ -50,7 +50,8 @@ class TestPkgdevShowkwParseArgs:
'--config', str(config_file), *args])
return options
- assert parse().color is True
+ with os_environ('NOCOLOR'):
+ assert parse().color is True
with os_environ(NOCOLOR='1'):
# NOCOLOR overrides config file
assert parse().color is False
next reply other threads:[~2022-11-19 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 17:22 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-28 19:41 [gentoo-commits] proj/pkgcore/pkgdev:main commit in: tests/scripts/ Arthur Zamarin
2023-12-29 12:32 Arthur Zamarin
2024-01-26 20:22 Arthur Zamarin
2024-07-20 15:37 Arthur Zamarin
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=1668878517.f9c6971a98ed76679e97e08ec25c4ab560921d21.arthurzam@gentoo \
--to=arthurzam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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