From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6651481528729600000 X-Received: by 2002:a19:f202:: with SMTP id q2mr731666lfh.8.1549465147686; Wed, 06 Feb 2019 06:59:07 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a2e:814b:: with SMTP id t11-v6ls2999903ljg.6.gmail; Wed, 06 Feb 2019 06:59:07 -0800 (PST) X-Google-Smtp-Source: AHgI3IYRKnfxk8VLdx1zWuU78kB9kcBhUfXrj9fJU8QxAlFZ6+YtCt5YtMSVvHec6JFN7DJ+lpln X-Received: by 2002:a2e:7c02:: with SMTP id x2-v6mr752442ljc.1.1549465146990; Wed, 06 Feb 2019 06:59:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549465146; cv=none; d=google.com; s=arc-20160816; b=vrJpMyb+A1VtW7GnYhkIDpqA6Wla6hpFukcvOdthema1A5AbvM2BCDg6YYKL+Fu+rS /yjnX4in30Bls444Gvll9VfDd2PpXRCjP3oWkkznwi9PKnjYJvBJPxG6ZYDc3suvGO6y kIORQugCwEOim7QnLBi+oJw5DGCDcLRyWmuEAC5hKEFW6dU7MjN+QxaPtqCW5GMt8gih Ly0e6vKCKN4QPdakkfCNAhxGy9Ht6Q4TDtHdFdM/C8uUXC6FML6Q7mj4ngwqAO2B/Psi jWufDbQtY2oT7I4luy1jLozY1uD7td/bXmSjcEFtNzPEwM9sk0akyyt//ueF/ZSnz9IS ggpw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:references:cc:to:from:subject; bh=RW1EVjT02VtQjVuBr6nV3Pnz36mkX+HKTA+tLAWTBAs=; b=0IUkD1JEBwWCpJG/ToutwP9sAqkBT+Ec4i5xJxbVthwZUyIzSEfzWv5xpXrzV+3Z0s r2OVxOeGg4UvXxwFzUyg6NU73SSh83/oCSsLZTi9NtYtR/r0G2bSIEl4wmfoWAcxsDiZ nGnxqYB+grPyOe0Hmv4HocFlxI1opG8EJB2ThQFZQjy0jtJSRYz+MZaAcoH8xV/9aTXN 41qSYx+LhGolWqMogmRiRN798DMISv9GWhU0maU86XxECF0S0t0W9fBBaG2OjKO7ZcFE 6E6yU1XKQ60fziiJU2XIUYOWfr9rvmSOlZ0fLfH73DkD7ojauwd9HcQQZj6YcYEAnfFK JdFQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id y18si1103430lfe.3.2019.02.06.06.59.06 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Feb 2019 06:59:06 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id x16Ex6nU003059 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 6 Feb 2019 15:59:06 +0100 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x16Ex5xo016370; Wed, 6 Feb 2019 15:59:05 +0100 Subject: Re: [BUG?] 'ResourceWarning: unclosed file <_io.BufferedReader name=xx>' while parsing recipes From: Jan Kiszka To: "[ext] Henning Schild" , "[ext] Claudius Heine" Cc: isar-users References: <20190128104916.02c2ad28@md1za8fc.ad001.siemens.net> Message-ID: Date: Wed, 6 Feb 2019 15:59:05 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: 0D9WmVBKeXD7 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" : >> >>> Hi, >>> >>> I get those warnings in my log: >>> >>>       Parsing recipes...WARNING: >>> /builds/ebsy/debian/isar/meta-isar/recipes-core/images/isar-image-base.bb: >>> :15: ResourceWarning: unclosed file <_io.BufferedReader >>> name=32> >>> >>>       WARNING: >>> /builds/ebsy/debian/isar/meta-isar/recipes-core/images/isar-image-debug.bb: >>> :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