From: Eric Dvorsak <eric@dvorsak.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: python-2: update to 2.7.10.
Date: Tue, 18 Aug 2015 18:23:06 +0200 [thread overview]
Message-ID: <87y4h85zx1.fsf@dvorsak.fr> (raw)
In-Reply-To: <87h9nwpqaq.fsf@gnu.org>
Ludovic Courtès writes:
> eric@dvorsak.fr skribis:
>
>> Altough the tests are still failing, I ran them after the build failed
>> with :
>>
>> guix build -K
>> cd tmp/nix-build-*
>> env -i $(which bash)
>> source environment-variables
>>
>> And they all passed except for some skips and a module that failed
>> trying to write to a dir without permissions.
>>
>> Maybe there is a fix to do to enable the tests, the problem might be
>> coming from the OS module. They fail because of an OSError exception,
>> so I wonder if it could be because the module doesn't work withing the
>> chroot.
>
> Wild guess: Could it be because Python’s bindings for ‘popen’ or
> something like that refer to /bin/sh, which is unavailable in the
> chroot, leading to ENOENT? Could you ‘grep -r /bin/sh’ in the source?
>
> Thanks,
> Ludo’.
Ag Results for `/bin/sh':
plat-freebsd4/regen:1:#! /bin/sh
plat-aix3/regen:1:#! /bin/sh
plat-beos5/regen:1:#! /bin/sh
plat-os2emx/regen:1:#! /bin/sh
distutils/tests/test_install_scripts.py:57: write_script("shell.sh", ("#!/bin/sh\n"
distutils/tests/test_build_scripts.py:68: ("#!/bin/sh\n"
distutils/tests/test_spawn.py:35: self.write_file(exe, '#!/bin/sh\nexit 1')
distutils/tests/test_spawn.py:47: self.write_file(exe, '#!/bin/sh\nexit 0')
test/test__osx_support.py:47: f.write("#!/bin/sh\n/bin/echo OK\n")
test/test__osx_support.py:59: f.write("#!/bin/sh\n/bin/echo ExpectedOutput\n")
test/test__osx_support.py:150: f.write("#!/bin/sh\n/bin/echo " + c_output)
test/test__osx_support.py:206: f.write("#!/bin/sh\nexit 255")
test/test_os.py:365: if os.path.exists("/bin/sh"):
test/test_os.py:367: with os.popen("/bin/sh -c 'echo $HELLO'") as popen:
test/test_subprocess.py:862: os.write(f, "#!/bin/sh\n")
test/test_subprocess.py:906: os.write(f, "#!/bin/sh\n")
test/test_subprocess.py:925: sh = '/bin/sh'
test/test_subprocess.py:927: # Test will fail if /bin/sh is a symlink to csh.
plat-irix5/regen:1:#! /bin/sh
plat-generic/regen:1:#! /bin/sh
plat-linux2/regen:1:#! /bin/sh
plat-netbsd1/regen:1:#! /bin/sh
ctypes/macholib/fetch_macholib:1:#!/bin/sh
plat-atheos/regen:1:#! /bin/sh
plat-aix4/regen:1:#! /bin/sh
plat-irix6/regen:1:#! /bin/sh
plat-freebsd6/regen:1:#! /bin/sh
plat-next3/regen:1:#! /bin/sh
plat-freebsd5/regen:1:#! /bin/sh
> This one ?
> popen2.py:84: cmd = ['/bin/sh', '-c', cmd]
plat-freebsd7/regen:1:#! /bin/sh
plat-darwin/regen:1:#! /bin/sh
subprocess.py:161:/bin/sh implicitly. This means that all characters, including shell
subprocess.py:226:Replacing /bin/sh shell backquote
subprocess.py:559: >>> check_output(["/bin/sh", "-c",
subprocess.py:1209: args = ["/bin/sh", "-c"] + args
pipes.py:36:second likewise for the output. The command must be valid /bin/sh
pipes.py:262:# Reliably quote a string as a single argument for /bin/sh
plat-freebsd8/regen:1:#! /bin/sh
plat-sunos5/regen:1:#! /bin/sh
plat-unixware7/regen:1:#! /bin/sh
Here is the def :
def _run_child(self, cmd):
if isinstance(cmd, basestring):
cmd = ['/bin/sh', '-c', cmd]
os.closerange(3, MAXFD)
try:
os.execvp(cmd[0], cmd)
finally:
os._exit(1)
What should be done to fix this ?
Eric
next prev parent reply other threads:[~2015-08-18 16:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 18:05 Python 2.7.* Andreas Enge
2015-08-02 15:42 ` [PATCH] gnu: python-2: update to 2.7.10 eric
2015-08-02 19:56 ` Mark H Weaver
2015-08-02 22:56 ` eric
2015-08-03 2:13 ` Mark H Weaver
2015-08-03 8:59 ` Andreas Enge
2015-08-04 14:52 ` Mark H Weaver
2015-08-07 0:12 ` Mark H Weaver
2015-08-10 13:56 ` Andreas Enge
2015-08-10 23:45 ` Mark H Weaver
2015-08-11 7:35 ` Andreas Enge
2015-08-18 15:30 ` Ludovic Courtès
2015-08-18 16:23 ` Eric Dvorsak [this message]
2015-08-18 17:48 ` Eric Bavier
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y4h85zx1.fsf@dvorsak.fr \
--to=eric@dvorsak.fr \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).