Re: [BUG?] 'ResourceWarning: unclosed file <_io.BufferedReader name=xx>' while parsing recipes

[Claudius Heine <claudius.heine.ext@siemens.com>]

Hi Jan,

On 06/02/2019 15.59, Jan Kiszka wrote:
> On 28.01.19 12:27, [ext] Jan Kiszka wrote:
>> On 28.01.19 10:49, [ext] Henning Schild wrote:
>>> Am Mon, 28 Jan 2019 10:45:23 +0100
>>> schrieb "[ext] Claudius Heine" <claudius.heine.ext@siemens.com>:
>>>
>>>> Hi,
>>>>
>>>> I get those warnings in my log:
>>>>
>>>>       Parsing recipes...WARNING:
>>>> /builds/ebsy/debian/isar/meta-isar/recipes-core/images/isar-image-base.bb: 
>>>>
>>>> <string>:15: ResourceWarning: unclosed file <_io.BufferedReader
>>>> name=32>
>>>>
>>>>       WARNING:
>>>> /builds/ebsy/debian/isar/meta-isar/recipes-core/images/isar-image-debug.bb: 
>>>>
>>>> <string>:15: ResourceWarning: unclosed file <_io.BufferedReader
>>>> name=30>
>>>
>>> I think we have all seen those ...
>>
>> I'm getting even more warnings these days, right after finishing the 
>> build:
>>
>> Exception ignored when trying to write to the signal wakeup fd:
>> BlockingIOError: [Errno 11] Resource temporarily unavailable
>>
>>>
>>>> They don't seem to have any effect, but are annoying. Does anyone
>>>> know what those mean and how to fix them? I guess they start
>>>> appearing on a bitbake update. Should they be investigated?
>>>
>>> and made the same observations, asked ourselfs the same questions.
>>> I also think it came with the bitbake update and i think it should be
>>> investigated and resolved.
>>>
>>
>> Yes, agreed. Maybe the first try should be updating bitbake and check 
>> if the issue persists. Or check if its git history suggests that 
>> something was changed in this direction.
> 
> Just browsed some bitbake commits for other reasons:
> 
> http://git.openembedded.org/bitbake/commit/?id=afee3f594e1510051a0b18e430e92549caf72fa2 
> 
> 
> Looks like an update will do it.

I am not sure. They fix an unclosed socket, but our error is an unclosed 
file. There exception occures with '.../lib/bb/main.py:481' ours 
'...images/isar-image-debug.bb'.

I guess that it is a similar issue this patch fixes, but IMO that one 
doesn't look like it fixes our problem.

Anyway thanks for looking that up!
Claudius

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de