From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/python-email-validator/
Date: Mon, 2 May 2022 12:42:16 +0000 (UTC) [thread overview]
Message-ID: <1651495331.ae2a89badb27c2ab211c9151615ec3da05e9f9df.mgorny@gentoo> (raw)
commit: ae2a89badb27c2ab211c9151615ec3da05e9f9df
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Mon May 2 12:40:47 2022 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Mon May 2 12:42:11 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ae2a89ba
dev-python/python-email-validator: Restore more test skips
Apparently my test setup is not the most strict one.
Closes: https://bugs.gentoo.org/842150
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
dev-python/python-email-validator/python-email-validator-1.2.1.ebuild | 3 +++
1 file changed, 3 insertions(+)
diff --git a/dev-python/python-email-validator/python-email-validator-1.2.1.ebuild b/dev-python/python-email-validator/python-email-validator-1.2.1.ebuild
index dd6dc9a517db..af9f4ad587c8 100644
--- a/dev-python/python-email-validator/python-email-validator-1.2.1.ebuild
+++ b/dev-python/python-email-validator/python-email-validator-1.2.1.ebuild
@@ -38,4 +38,7 @@ EPYTEST_DESELECT=(
"tests/test_main.py::test_email_example_reserved_domain[me@example.com]"
"tests/test_main.py::test_email_example_reserved_domain[me@mail.example.com]"
tests/test_main.py::test_validate_email__with_caching_resolver
+ tests/test_main.py::test_main_single_good_input
+ tests/test_main.py::test_main_multi_input
+ tests/test_main.py::test_main_input_shim
)
next reply other threads:[~2022-05-02 12:42 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 12:42 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-23 15:54 [gentoo-commits] repo/gentoo:master commit in: dev-python/python-email-validator/ Michał Górny
2023-05-23 15:36 Arthur Zamarin
2023-04-20 3:12 Michał Górny
2023-04-17 5:41 Michał Górny
2023-04-16 3:42 Michał Górny
2023-02-23 6:19 Michał Górny
2023-02-22 20:30 Arthur Zamarin
2023-01-22 9:01 Michał Górny
2022-10-22 15:53 Michał Górny
2022-10-22 15:49 Arthur Zamarin
2022-10-09 16:15 James Le Cuirot
2022-10-07 7:03 Michał Górny
2022-09-22 7:45 Michał Górny
2022-09-19 18:35 Arthur Zamarin
2022-06-06 9:29 Jakov Smolić
2022-05-15 10:41 Michał Górny
2022-05-15 10:41 Michał Górny
2022-05-11 12:56 Jakov Smolić
2022-05-02 8:27 Michał Górny
2022-05-01 1:52 WANG Xuerui
2022-04-24 20:26 Michał Górny
2022-04-08 14:23 Arthur Zamarin
2022-04-08 14:23 Arthur Zamarin
2021-12-03 20:47 Arthur Zamarin
2021-11-24 23:59 Sam James
2021-11-19 2:43 Sam James
2021-11-18 10:50 Sam James
2021-11-18 10:39 Sam James
2021-11-18 9:09 Sam James
2021-11-13 19:50 Sam James
2021-10-10 20:43 Sam James
2021-10-10 2:20 Sam James
2021-10-10 0:09 Sam James
2021-09-18 17:06 Sam James
2021-07-25 18:04 Michał Górny
2021-07-25 8:41 Michał Górny
2021-07-25 1:04 Sam James
2021-06-12 21:02 Michał Górny
2021-06-04 14:40 Michał Górny
2021-01-15 7:35 Michał Górny
2021-01-14 23:59 Sam James
2020-12-16 11:51 Michał Górny
2020-11-06 8:12 Michał Górny
2020-07-25 11:17 Sam James
2020-06-24 7:07 Michał Górny
2020-06-24 7:07 Michał Górny
2020-06-24 7:07 Michał Górny
2020-05-21 13:19 Michał Górny
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=1651495331.ae2a89badb27c2ab211c9151615ec3da05e9f9df.mgorny@gentoo \
--to=mgorny@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