On Wed, Jul 29, 2020 at 8:27 PM Mingde (Matthew) Zeng <matthew.z...@windriver.com> wrote: > > > Khem Raj <raj.k...@gmail.com> 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. >
its not in master yet so please send a v2. > > Matthew > > > > > On Wed, Jul 29, 2020 at 6:43 AM Richard Purdie > > <richard.pur...@linuxfoundation.org> wrote: > >> > >> On Wed, 2020-07-29 at 09:41 -0400, Mingde (Matthew) Zeng wrote: > >> > Richard Purdie <richard.pur...@linuxfoundation.org> 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
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#141110): https://lists.openembedded.org/g/openembedded-core/message/141110 Mute This Topic: https://lists.openembedded.org/mt/75864108/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
