From: "Matthew" <matthew.zeng@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
"Patches and discussions about the oe-core layer"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCHv2] ltp: remove OOM tests from runtest/mm
Date: Wed, 29 Jul 2020 23:27:02 -0400 [thread overview]
Message-ID: <878sf1r8c9.fsf@windriver.com> (raw)
In-Reply-To: <CAMKF1sqZuL_0GE7uOuJqQTNm9TEazXDAsUZmzSebaAZq0VLzFQ@mail.gmail.com>
Khem Raj <raj.khem@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.
Matthew
>
> On Wed, Jul 29, 2020 at 6:43 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>>
>> On Wed, 2020-07-29 at 09:41 -0400, Mingde (Matthew) Zeng wrote:
>> > Richard Purdie <richard.purdie@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
next prev parent reply other threads:[~2020-07-30 3:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 13:09 [PATCHv2] ltp: remove OOM tests from runtest/mm Matthew
2020-07-29 13:24 ` [OE-core] " Richard Purdie
2020-07-29 13:41 ` Matthew
2020-07-29 13:43 ` Richard Purdie
2020-07-29 23:23 ` Khem Raj
2020-07-30 3:27 ` Matthew [this message]
2020-07-30 3:34 ` Khem Raj
2020-07-30 3:56 ` Matthew
2020-08-05 15:52 ` Matthew
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=878sf1r8c9.fsf@windriver.com \
--to=matthew.zeng@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
/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