From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail5.wrs.com (mail5.wrs.com [192.103.53.11]) by mx.groups.io with SMTP id smtpd.web12.1087.1596079691822240198 for ; Wed, 29 Jul 2020 20:28:11 -0700 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: windriver.com, ip: 192.103.53.11, mailfrom: matthew.zeng@windriver.com) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail5.wrs.com (8.15.2/8.15.2) with ESMTPS id 06U3R3j4023408 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 29 Jul 2020 20:27:23 -0700 Received: from mt-manjaro (128.224.73.244) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server (TLS) id 14.3.487.0; Wed, 29 Jul 2020 20:27:06 -0700 References: <20200729130916.38764-1-matthew.zeng@windriver.com> <87bljyqvzk.fsf@windriver.com> User-agent: mu4e 1.4.10; emacs 27.0.91 From: "Matthew" To: Khem Raj CC: Richard Purdie , "Patches and discussions about the oe-core layer" Subject: Re: [OE-core] [PATCHv2] ltp: remove OOM tests from runtest/mm In-Reply-To: Date: Wed, 29 Jul 2020 23:27:02 -0400 Message-ID: <878sf1r8c9.fsf@windriver.com> MIME-Version: 1.0 X-Originating-IP: [128.224.73.244] Content-Type: text/plain Khem Raj writes: > on master-next I am also seeing > > step1b: WARNING: ltp-20200515-r0 do_patch: QA Issue: Patch log > indicates that patches do not apply cleanly. [patch-fuzz] > > I wonder if its related to this as well. My bad. Just a couple days ago ltp master introduced a commit directly effected the line above my change, resulting the diff to look slightly different. I could send a patch on top of this commit, or is it possible to revert this merged commit altogether and I will send a new patch, to keep the git log clean. Whichever preferred by YP. Matthew > > On Wed, Jul 29, 2020 at 6:43 AM Richard Purdie > wrote: >> >> On Wed, 2020-07-29 at 09:41 -0400, Mingde (Matthew) Zeng wrote: >> > Richard Purdie writes: >> > >> > > On Wed, 2020-07-29 at 09:09 -0400, Matthew wrote: >> > > > Fixes [YOCTO #13802] >> > > >> > > Thanks, we can reference the bug but I don't think we can yet claim >> > > it >> > > fixes it. >> > >> > Sure, would something like the following work? >> > >> > Reference [YOCTO #13802] >> >> Simply "[YOCTO #13802]" is fine (I'll tweak the commit message as I >> merge). >> >> > > The missing log issue happened again: >> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/96/builds/908 >> > > so I think there are multiple issues at play here. >> > >> > Can you attach this build's log.do_testimage so I can have a further >> > look? >> >> Sorry, that build directory has been reused in this case :( Next time >> that happens I'll try and spot/grab it. >> >> > > Is there any way to have the logging logged to disk straight away >> > > rather than stuck internally in oeqa's logging buffers? That way we >> > > could see which tests had run before a hang? >> > > >> > > Also, could we make the scp failure non-fatal, maybe a warning so >> > > that >> > > when it fails we can look at the rest of the logs? >> > >> > I'll further investigate this idea. >> >> Thanks! >> >> Cheers, >> >> Richard >> >> -- Mingde (Matthew) Zeng