From: "Zac Medico" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: pym/portage/tests/locks/
Date: Wed, 28 Mar 2012 00:26:31 +0000 (UTC) [thread overview]
Message-ID: <1332894377.f7a7a30ee44ced6628163bf33b52b30467d28246.zmedico@gentoo> (raw)
commit: f7a7a30ee44ced6628163bf33b52b30467d28246
Author: Zac Medico <zmedico <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 28 00:26:17 2012 +0000
Commit: Zac Medico <zmedico <AT> gentoo <DOT> org>
CommitDate: Wed Mar 28 00:26:17 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=f7a7a30e
LockNonblockTestCase: close_fds tweak
Make consistent with commit 144c23efbb4e9565debad03c13c5bcab833a8336.
---
pym/portage/tests/locks/test_lock_nonblock.py | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/pym/portage/tests/locks/test_lock_nonblock.py b/pym/portage/tests/locks/test_lock_nonblock.py
index 17f854d..2ff7b35 100644
--- a/pym/portage/tests/locks/test_lock_nonblock.py
+++ b/pym/portage/tests/locks/test_lock_nonblock.py
@@ -18,7 +18,10 @@ class LockNonblockTestCase(TestCase):
lock1 = portage.locks.lockfile(path)
pid = os.fork()
if pid == 0:
- portage.process._setup_pipes({0:0, 1:1, 2:2})
+ portage.locks._close_fds()
+ # Disable close_fds since we don't exec
+ # (see _setup_pipes docstring).
+ portage.process._setup_pipes({0:0, 1:1, 2:2}, close_fds=False)
rval = 2
try:
try:
next reply other threads:[~2012-03-28 0:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 0:26 Zac Medico [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-14 9:18 [gentoo-commits] proj/portage:master commit in: pym/portage/tests/locks/ Zac Medico
2011-06-09 0:33 Zac Medico
2011-05-18 19:46 Arfrever Frehtes Taifersar Arahesis
2011-05-17 21:14 Zac Medico
2011-05-17 21:03 Zac Medico
2011-05-17 20:56 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=1332894377.f7a7a30ee44ced6628163bf33b52b30467d28246.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