automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report]  |FAILURE| pw(84077) [kmods, v2] windows: normalize line-endings
Date: 12 Nov 2020 12:20:41 -0800	[thread overview]
Message-ID: <569c58$g58dr6@orsmga005-auth.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]


Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/84077

_apply issues_

Submitter: Luca Boccassi <luca.boccassi@gmail.com>
Date: 2020-11-12 20:15:09
Reply_mail: 20201112201509.1002479-1-luca.boccassi@gmail.com

DPDK git baseline:
	Repo:dpdk, CommitID: 3495a68f2a5491b417ff080d57cbf7e39abc1f44


* Repo: dpdk
Once it has been determined that an example cannot be built, there is
    little point in continuing to process the meson.build file for that
    example, so we can use subdir_done() to return to the calling file.
    This can potentially prevent problems where later statement in the file
    may cause an error on systems where the app cannot be built, e.g. on
    Windows or FreeBSD.
    
--
Applying: windows: normalize line-endings
error: sha1 information is lacking or useless (README).
error: could not build fake ancestor
Patch failed at 0001 windows: normalize line-endings
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team

                 reply	other threads:[~2020-11-12 20:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='569c58$g58dr6@orsmga005-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=test-report@dpdk.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;
as well as URLs for NNTP newsgroup(s).