public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-cov/files/
Date: Tue, 22 Nov 2022 12:45:44 +0000 (UTC)	[thread overview]
Message-ID: <1669121116.03b152e7d9550a36277933893778a6295df4cfd0.arthurzam@gentoo> (raw)

commit:     03b152e7d9550a36277933893778a6295df4cfd0
Author:     Michael Mair-Keimberger <mmk <AT> levelnine <DOT> at>
AuthorDate: Mon Nov 21 18:15:33 2022 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Tue Nov 22 12:45:16 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=03b152e7

dev-python/pytest-cov: remove unused patch(es)

Signed-off-by: Michael Mair-Keimberger <mmk <AT> levelnine.at>
Closes: https://github.com/gentoo/gentoo/pull/28372
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 .../files/pytest-cov-3.0.0-coverage-6.2.patch      | 30 ----------------------
 1 file changed, 30 deletions(-)

diff --git a/dev-python/pytest-cov/files/pytest-cov-3.0.0-coverage-6.2.patch b/dev-python/pytest-cov/files/pytest-cov-3.0.0-coverage-6.2.patch
deleted file mode 100644
index b44326d8b60d..000000000000
--- a/dev-python/pytest-cov/files/pytest-cov-3.0.0-coverage-6.2.patch
+++ /dev/null
@@ -1,30 +0,0 @@
-From 6d06678a76d9275beb48917d7653ea6a610c7717 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Micha=C5=82=20G=C3=B3rny?= <mgorny@gentoo.org>
-Date: Sun, 23 Jan 2022 15:03:35 +0100
-Subject: [PATCH] Update test_invalid_coverage_source for coverage-6.2
-
-Update test_invalid_coverage_source to make the "No data was collected"
-less strict, as the output has changed in coverage-6.2.  This solution
-was suggested by Tom Callaway (@spotrh) on the linked bug.
-
-Fixes #509
----
- tests/test_pytest_cov.py | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/tests/test_pytest_cov.py b/tests/test_pytest_cov.py
-index f93d352..6d97949 100644
---- a/tests/test_pytest_cov.py
-+++ b/tests/test_pytest_cov.py
-@@ -981,7 +981,7 @@ def test_invalid_coverage_source(testdir):
-         '*10 passed*'
-     ])
-     result.stderr.fnmatch_lines([
--        'Coverage.py warning: No data was collected.*'
-+        '*No data was collected.*'
-     ])
-     result.stdout.fnmatch_lines([
-         '*Failed to generate report: No data to report.',
--- 
-2.34.1
-


                 reply	other threads:[~2022-11-22 12:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1669121116.03b152e7d9550a36277933893778a6295df4cfd0.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