From: "Zac Medico" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: lib/portage/tests/ebuild/
Date: Sun, 31 Dec 2023 00:01:44 +0000 (UTC) [thread overview]
Message-ID: <1703980801.60c196dc162a376ee8b4856a4dc6b07d8a85bb3c.zmedico@gentoo> (raw)
commit: 60c196dc162a376ee8b4856a4dc6b07d8a85bb3c
Author: Zac Medico <zmedico <AT> gentoo <DOT> org>
AuthorDate: Sat Dec 30 22:59:19 2023 +0000
Commit: Zac Medico <zmedico <AT> gentoo <DOT> org>
CommitDate: Sun Dec 31 00:00:01 2023 +0000
URL: https://gitweb.gentoo.org/proj/portage.git/commit/?id=60c196dc
EbuildFetchTestCase: Fix dict/shelve key order assumption
Just like 4de288937ad7.
Bug: https://bugs.gentoo.org/921107
Signed-off-by: Zac Medico <zmedico <AT> gentoo.org>
lib/portage/tests/ebuild/test_fetch.py | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lib/portage/tests/ebuild/test_fetch.py b/lib/portage/tests/ebuild/test_fetch.py
index 9b9260008c..bc8c052746 100644
--- a/lib/portage/tests/ebuild/test_fetch.py
+++ b/lib/portage/tests/ebuild/test_fetch.py
@@ -615,12 +615,12 @@ class EbuildFetchTestCase(TestCase):
emdisconf.content_db.remove(filename)
# foo should still have a content revision corresponding to bar's content.
self.assertEqual(
- [
+ {
k[len("filename:") :]
for k in emdisconf.content_db
if k.startswith("filename:")
- ],
- ["bar", "foo"],
+ },
+ {"bar", "foo"},
)
self.assertEqual(len(emdisconf.content_db["filename:foo"]), 1)
self.assertEqual(
next reply other threads:[~2023-12-31 0:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-31 0:01 Zac Medico [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-05 6:11 [gentoo-commits] proj/portage:master commit in: lib/portage/tests/ebuild/ Zac Medico
2023-10-30 5:09 Zac Medico
2021-05-24 6:20 Zac Medico
2021-02-21 8:33 Zac Medico
2020-08-03 23:28 Zac Medico
2020-07-19 21:55 Zac Medico
2020-03-22 1:12 Zac Medico
2019-10-19 23:15 Zac Medico
2019-10-19 5:29 Zac Medico
2019-10-19 1:38 Zac Medico
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=1703980801.60c196dc162a376ee8b4856a4dc6b07d8a85bb3c.zmedico@gentoo \
--to=zmedico@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