From: Henning Schild <henning.schild@siemens.com>
To: "[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: Mon, 28 Jan 2019 10:49:16 +0100 [thread overview]
Message-ID: <20190128104916.02c2ad28@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <a92ff0d9-e55a-ad92-b79c-7c0bc0a0bf21@siemens.com>
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 ...
> 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.
Henning
> Thanks,
> Claudius
>
next prev parent reply other threads:[~2019-01-28 9:49 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 [this message]
2019-01-28 11:27 ` Jan Kiszka
2019-02-06 14:59 ` Jan Kiszka
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=20190128104916.02c2ad28@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=claudius.heine.ext@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