Re: Processing large amounts of files

[Ricardo Wurmus <rekado@elephly.net>]

Ricardo Wurmus <rekado@elephly.net> writes:

> Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> writes:
>
>>> When running with "-l all" I see this:
>>> 
>>>   info: .75 Computing workflow `cat'...
>>>   debug: 3.13 Computing script for process `meow'
>>>   guix: 3.13 Looking up package `bash-minimal'
>>>   guix: 3.13 Opening inferior Guix at
>>> `/gnu/store/pb1nkrn3sg6a1j6c4r5j2ahygkf4vkv9-profile'
>>>   guix: 4.27 Looking up package `guix'
>>>   debug: 4.45 Generating all scripts and their dependencies.
>>>   debug: 4.89 Generating all scripts and their dependencies.
>>>   run: 6.73 Executing: /bin/sh -c
>>> /gnu/store/5idhbvhrwj3p53kkz2vikdn1ypncwj84-gwl-meow.scm '((inputs
>>> "/tmp/meow/0" ...
>>>   process: 8.80 In execvp of /bin/sh: Argument list too long
>>>   error: 8.80 Wrong type argument in position 1: #f
>>> 
>>> This at least tells us that the last error here is due to sh refusing
>>> to run.
>> Good to know, and I thought it'd be just that, but… shouldn't this
>> failure to invoke sh be caught through something?
>
> Yes, it really should.  This may be a problem with how we capture stdout
> and stderr.  I'll look into it.

Fixed with commit f7d6b159e9423e69271503ef9ea92e191265d8ee.

The command processor erroneously returned the exit code and not the
composite status value containing both exit code and termination signal.

-- 
Ricardo