Re: [PATCH] process: Flush server stdout/stderr before reporting failure

[Jan Kiszka <jan.kiszka@siemens.com>]

On 2018-09-05 02:14, richard.purdie@linuxfoundation.org wrote:
> On Tue, 2018-09-04 at 15:09 +0200, Jan Kiszka wrote:
>> Looks similar on first glance, but it only partly helps with
>> exceptions.
>> We get from
>>
>> $ bitbake | cat
>> ERROR: Unable to start bitbake server
>>
>> to
>>
>> $ bitbake | cat
>> ERROR: Unable to start bitbake server
>> ERROR: Server log for this session (/work/build/bitbake-
>> cookerdaemon.log):
>> --- Starting bitbake server pid 149 at 2018-09-04 13:02:15.144583 ---
>>
>> while it should have
>>
>> $ bitbake
>> ERROR: Unable to start bitbake server
>> ERROR: Last 10 lines of server log for this session
>> (/work/build/bitbake-cookerdaemon.log):
>> Traceback (most recent call last):
>>     File "/work/isar/bitbake/lib/bb/daemonize.py", line 77, in
>> createDaemon
>>       function()
>>     File "/work/isar/bitbake/lib/bb/server/process.py", line 433, in
>> _startServer
>>       self.cooker = bb.cooker.BBCooker(self.configuration,
>> self.featureset)
>>     File "/work/isar/bitbake/lib/bb/cooker.py", line 178, in __init__
>>       self.configwatcher = pyinotify.WatchManager()
>>     File "/work/isar/bitbake/lib/pyinotify.py", line 1764, in __init__
>>       raise OSError(err % self._inotify_wrapper.str_errno())
>> OSError: Cannot initialize new instance of inotify, Errno=Too many
>> open
>> files (EMFILE)
> 
> The more I looked into this the more problems I found. I've put this in
> for some testing which should address the issues:
> 
> http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=dae574dd680f4f9db0b1447266742fa127963842
> 

Yep, it does here as well!

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux