1 |
On 01/28/2013 10:11 AM, Fabian Groffen wrote: |
2 |
> On 28-01-2013 01:54:02 +0100, Burcin Erocal wrote: |
3 |
>>> line 1367, in _main_loop self._event_loop.iteration() File |
4 |
>>> "/Users/burcinTraceback (most recent call last): File |
5 |
>>> "/Users/burcin/slave/plainbf_mini/t/local/bin/emerge", line 72, in |
6 |
>>> <module> sys.stderr.write(tb_str) IOError: [Errno 35] Resource |
7 |
>>> temporarily unavailable |
8 |
>> |
9 |
>> The traceback above is not complete. I guess it gets interrupted somehow, then the second IOError takes over. |
10 |
> |
11 |
>> File "/Users/burcin/slave/plainbf_mini/t/local/lib/portage/pym/_emerge/SpawnProcess.py", line 162, in _pipe_logger_exit |
12 |
>> self.wait() |
13 |
> |
14 |
> I can reproduce this. I don't have your second stack though, I only see |
15 |
> the one that results in |
16 |
> IOError: [Errno 35] Resource temporarily unavailable |
17 |
> |
18 |
>> It seems that the problem was introduced between these two merges. |
19 |
>> |
20 |
>> cefe9ddc5e1b8a1ba727afddd11638723875949c 2013-01-05 19:12 |
21 |
>> 754956bff8273df8ce2c3d9f6ff7fb22126ebd41 2013-01-10 22:01 |
22 |
> |
23 |
> Thanks! |
24 |
> |
25 |
> What I see is what looks like it actually chokes on writing more error |
26 |
> output like this: |
27 |
> * /Volumes/Scratch/bootstrap-20130128/usr/lib/portage/bin/save-ebuild-env.sh: |
28 |
> * line 88: compgen: command not found |
29 |
> <this repeats many times> |
30 |
> |
31 |
> ... |
32 |
> |
33 |
> File "/Volumes/Scratch/bootstrap-20130128/usr/lib/portage/pym/_emerge/Scheduler.py", line 1373, in _main_loop |
34 |
> self._event_loop.iteration() |
35 |
> File "/Volumes/Scratch/booTraceback (most recent call last): |
36 |
> File "/Volumes/Scratch/bootstrap-20130128/usr/bin/emerge", line 72, in <module> |
37 |
> sys.stderr.write(tb_str) |
38 |
> IOError: [Errno 35] Resource temporarily unavailable |
39 |
|
40 |
It looks like maybe one of the ebuilds is putting stdin into |
41 |
non-blocking mode, and it's propagating to emerge's stderr stream. If |
42 |
that's true, it might help if you use the emerge --quiet-build option, |
43 |
since that makes the ebuilds have /dev/null for stdin. |
44 |
-- |
45 |
Thanks, |
46 |
Zac |