From: "Matthew" <matthew.zeng@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] ✗ patchtest: failure for ltp: make copyFrom scp command non-fatal (rev4)
Date: Wed, 5 Aug 2020 16:16:04 -0400 [thread overview]
Message-ID: <87mu38x30b.fsf@windriver.com> (raw)
In-Reply-To: <6092f4f3c64934ba1b10d657ca3103ab98cb5a1e.camel@linuxfoundation.org>
Richard Purdie <richard.purdie@linuxfoundation.org> writes:
> On Wed, 2020-08-05 at 15:23 -0400, Matthew wrote:
>> My poky master is the latest commit (5e1bc3ef5a * net-tools: fix
>> upstream version check) and my patch applies perfectly. Why is
>> Patchwork complaining?
>
> FWIW I just tried to apply the patch and it doesn't apply for me :(.
>
> (Stripping trailing CRs from patch; use --binary to disable.)
> patching file meta/lib/oeqa/core/target/ssh.py
> (Stripping trailing CRs from patch; use --binary to disable.)
> patching file meta/lib/oeqa/runtime/cases/ltp.py
> Hunk #1 FAILED at 78.
> 1 out of 1 hunk FAILED -- saving rejects to file meta/lib/oeqa/runtime/cases/ltp.py.rej
>
> The difference is trailing whitespace which is present on the line:
>
> remote_src = "/opt/ltp/results/%s" % ltp_group
>
> but has been stripped in your patch.
Arghh, I configured automatic remove trailing whitespace on save, that must be the issue.
Patch with the whitespace sent.
>
> Cheers,
>
> Richard
--
Mingde (Matthew) Zeng
prev parent reply other threads:[~2020-08-05 20:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 18:51 [PATCHv4] ltp: make copyFrom scp command non-fatal Matthew
2020-08-05 19:02 ` ✗ patchtest: failure for ltp: make copyFrom scp command non-fatal (rev4) Patchwork
2020-08-05 19:23 ` Matthew
2020-08-05 19:52 ` [OE-core] " Richard Purdie
2020-08-05 20:16 ` Matthew [this message]
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=87mu38x30b.fsf@windriver.com \
--to=matthew.zeng@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--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