From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
"[ext] Claudius Heine" <claudius.heine.ext@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [BUG?] 'ResourceWarning: unclosed file <_io.BufferedReader name=xx>' while parsing recipes
Date: Wed, 6 Feb 2019 15:59:05 +0100 [thread overview]
Message-ID: <a0d3f2e5-e02d-3f11-f611-22b7b5f525cd@siemens.com> (raw)
In-Reply-To: <b8bf1727-6852-0069-fd96-c4b86a903c7a@siemens.com>
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.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-02-06 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 9:45 Claudius Heine
2019-01-28 9:49 ` Henning Schild
2019-01-28 11:27 ` Jan Kiszka
2019-02-06 14:59 ` Jan Kiszka [this message]
2019-02-06 15:11 ` Claudius Heine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a0d3f2e5-e02d-3f11-f611-22b7b5f525cd@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=claudius.heine.ext@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox