automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: qi.z.zhang@intel.com
Subject: [dpdk-test-report] |FAILURE| pw32540 [PATCH RFC 1/5] version: 17.11.0
Date: 09 Jan 2018 14:54:34 -0800	[thread overview]
Message-ID: <1f4ae4$ollgs@orsmga002.jf.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Qi Zhang <qi.z.zhang@intel.com>
Date: Wed, 20 Dec 2017 16:34:45 -0500
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:36d020c107ba65a584784a3f52484ea1698d4f9d
                   Repo:dpdk-next-crypto, Branch:master, CommitID:5df818d05d9586d8c00be2bb0a4b38b0b6410f50
                   Repo:dpdk-next-net, Branch:master, CommitID:d54afeb1a9810d5bdf0d69e572682fd3686667f7
                   Repo:dpdk-next-virtio, Branch:master, CommitID:e9e957b8725bffb3d2ffb18467ffab91e3f2fa2e
                   Repo:dpdk, Branch:master, CommitID:b45056be0429d6df2313e5e49aa8f78e5d840a97
                   
Apply patch file failed:
Repo: dpdk
32540:
patching file lib/librte_eal/common/include/rte_version.h
Hunk #1 FAILED at 71.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/include/rte_version.h.rej
patching file pkg/dpdk.spec
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file pkg/dpdk.spec.rej

Repo: dpdk-next-crypto
32540:
patching file lib/librte_eal/common/include/rte_version.h
Hunk #1 FAILED at 71.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/include/rte_version.h.rej
patching file pkg/dpdk.spec
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file pkg/dpdk.spec.rej

Repo: dpdk-next-net
32540:
patching file lib/librte_eal/common/include/rte_version.h
Hunk #1 FAILED at 71.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/include/rte_version.h.rej
patching file pkg/dpdk.spec
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file pkg/dpdk.spec.rej

Repo: dpdk-next-virtio
32540:
patching file lib/librte_eal/common/include/rte_version.h
Hunk #1 FAILED at 71.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/include/rte_version.h.rej
patching file pkg/dpdk.spec
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file pkg/dpdk.spec.rej

Repo: dpdk-next-eventdev
32540:
patching file lib/librte_eal/common/include/rte_version.h
Hunk #1 FAILED at 71.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eal/common/include/rte_version.h.rej
patching file pkg/dpdk.spec
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file pkg/dpdk.spec.rej


DPDK STV team

                 reply	other threads:[~2018-01-09 22:54 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='1f4ae4$ollgs@orsmga002.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=qi.z.zhang@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).