From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6651481528729600000 X-Received: by 2002:adf:ee51:: with SMTP id w17mr1357461wro.17.1548674851455; Mon, 28 Jan 2019 03:27:31 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:35c6:: with SMTP id c189ls1905417wma.13.canary-gmail; Mon, 28 Jan 2019 03:27:30 -0800 (PST) X-Google-Smtp-Source: ALg8bN7+8AkuETyfqIadx4TLNnJ8BhOjMmQroLXGmO3HVrX2TUlhKQRNP8eBzetTYL/JBFJozc8B X-Received: by 2002:a1c:f20c:: with SMTP id s12mr972203wmc.25.1548674850717; Mon, 28 Jan 2019 03:27:30 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548674850; cv=none; d=google.com; s=arc-20160816; b=k7WPg+3/l5D1/cqfHlwSk+BThBDT6ztP+HlbSxjcNCvUFgqyazkbv28fbRVlqhxbx2 tYNX4NKBNqg8lNWKIlwYir0l1VCYHnS2bqkIArX3Xk9jFXUJvOY39F7MyKua2NIxejT+ uGqEa2WhTSkTHdoMValEkJqz/tahw5qonCJSPzMM0jwuk19H8yD3Fts4EDNoorxk1CeI 0nhUDTK5Sdqf6qf5ByW00DgyaR6FVWjNW6LyKhUAlp7seNgDBfOS0K81WLm/0XtDhlpf 0Jx+Xaj/xHRHeBPc5SfIVuLjXogszD9Yb38jMCwaRbMR//7L3yLavgNIXXocCaHQfYEu PuDw== 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:from:references:cc:to:subject; bh=+C3vjC/AlqCyEq523q0qU2rM8UgrG9jj9vSc/CsInI8=; b=JqatKwuVat+5vZK9uOP9v1e6N14rpTtdXVEFKEX5+OJqrNX/rIcNVHxsZrKsX09ZWj sjPBi/tpm/hikcL69MAWb71edNPpFWr+/Q1Un5iEAwMChFiijUim5pG6YXpX92sgLWuy 93CtsvmRHSnPShe32LsZksG9EM7i62ACTO7qFOq4WhRx//8M690FKBUl0Ti5CbOGLLD3 R1HjlSk1FYU0skMmg+jQaX/37BpGE1hxYJSxMjEpCDJ59Z1kqdbPlt0kb6ScZEsjjqdN nCYyf5lPsQp+ItswdyPjZwlJf68YdV3ZiGAOaWiU6/GkVhCiET3h3X4JSPovFo1qdzQ1 zv6g== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id z207si2730524wmc.2.2019.01.28.03.27.30 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 28 Jan 2019 03:27:30 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id x0SBRUBj012380 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Mon, 28 Jan 2019 12:27:30 +0100 Received: from [167.87.35.18] ([167.87.35.18]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x0SBRT0l013978; Mon, 28 Jan 2019 12:27:29 +0100 Subject: Re: [BUG?] 'ResourceWarning: unclosed file <_io.BufferedReader name=xx>' while parsing recipes To: "[ext] Henning Schild" , "[ext] Claudius Heine" Cc: isar-users References: <20190128104916.02c2ad28@md1za8fc.ad001.siemens.net> From: Jan Kiszka Message-ID: Date: Mon, 28 Jan 2019 12:27:28 +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: <20190128104916.02c2ad28@md1za8fc.ad001.siemens.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: K3geO1y+lAJM 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. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux