Re: [gentoo-alt] portage failure on fedora-18

[Zac Medico]

On 01/28/2013 10:11 AM, Fabian Groffen wrote:
> On 28-01-2013 01:54:02 +0100, Burcin Erocal wrote:
>>> line 1367, in _main_loop self._event_loop.iteration() File
>>> "/Users/burcinTraceback (most recent call last): File
>>> "/Users/burcin/slave/plainbf_mini/t/local/bin/emerge", line 72, in
>>> <module> sys.stderr.write(tb_str) IOError: [Errno 35] Resource
>>> temporarily unavailable
>>
>> The traceback above is not complete. I guess it gets interrupted somehow, then the second IOError takes over.
>
>>   File "/Users/burcin/slave/plainbf_mini/t/local/lib/portage/pym/_emerge/SpawnProcess.py", line 162, in _pipe_logger_exit
>>     self.wait()
>
> I can reproduce this.  I don't have your second stack though, I only see
> the one that results in
> IOError: [Errno 35] Resource temporarily unavailable
>
>> It seems that the problem was introduced between these two merges.
>>
>> cefe9ddc5e1b8a1ba727afddd11638723875949c 2013-01-05 19:12
>> 754956bff8273df8ce2c3d9f6ff7fb22126ebd41 2013-01-10 22:01
>
> Thanks!
>
> What I see is what looks like it actually chokes on writing more error
> output like this:
>  *      /Volumes/Scratch/bootstrap-20130128/usr/lib/portage/bin/save-ebuild-env.sh:
>  *      line 88: compgen: command not found
> <this repeats many times>
>
> ...
>
>   File "/Volumes/Scratch/bootstrap-20130128/usr/lib/portage/pym/_emerge/Scheduler.py", line 1373, in _main_loop
>     self._event_loop.iteration()
>   File "/Volumes/Scratch/booTraceback (most recent call last):
>   File "/Volumes/Scratch/bootstrap-20130128/usr/bin/emerge", line 72, in <module>
>     sys.stderr.write(tb_str)
> IOError: [Errno 35] Resource temporarily unavailable

It looks like maybe one of the ebuilds is putting stdin into
non-blocking mode, and it's propagating to emerge's stderr stream. If
that's true, it might help if you use the emerge --quiet-build option,
since that makes the ebuilds have /dev/null for stdin.
-- 
Thanks,
Zac