automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: anatoly.burakov@intel.com
Subject: [dpdk-test-report] |FAILURE| pw35718 [PATCH v3] eal: add asynchronous request API to DPDK IPC
Date: 07 Mar 2018 11:26:13 -0800	[thread overview]
Message-ID: <a797f1$12jfde@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Wed,  7 Mar 2018 16:57:01 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:92924b207b124c156f7b6dff75110d6af83d971f
                   Repo:dpdk-next-crypto, Branch:master, CommitID:92924b207b124c156f7b6dff75110d6af83d971f
                   Repo:dpdk-next-net, Branch:master, CommitID:317debafe8e154cc81f5053c7424c8cc41ac8812
                   Repo:dpdk-next-virtio, Branch:master, CommitID:fc33e147ae5e63a28c2b2c9bec5ad378c612ca36
                   Repo:dpdk, Branch:master, CommitID:c06ddf9698e0c2a9653cfa971f9ddc205065662c
                   
Apply patch file failed:
Repo: dpdk
35718:
patching file lib/librte_eal/common/eal_common_proc.c
Hunk #1 succeeded at 25 (offset -1 lines).
Hunk #2 succeeded at 39 (offset -1 lines).
Hunk #3 succeeded at 63 (offset -2 lines).
Hunk #4 succeeded at 101 (offset -2 lines).
Hunk #5 succeeded at 178 (offset -13 lines).
Hunk #6 succeeded at 225 with fuzz 1 (offset -137 lines).
Hunk #7 FAILED at 465.
Hunk #8 succeeded at 364 with fuzz 1 (offset -150 lines).
Hunk #9 FAILED at 774.
Hunk #10 succeeded at 653 with fuzz 2 (offset -158 lines).
Hunk #11 FAILED at 831.
Hunk #12 FAILED at 879.
Hunk #13 FAILED at 914.
Hunk #14 succeeded at 926 (offset -54 lines).
Hunk #15 FAILED at 1009.
Hunk #16 succeeded at 949 (offset -72 lines).
6 out of 16 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_proc.c.rej
patching file lib/librte_eal/common/include/rte_eal.h
patching file lib/librte_eal/rte_eal_version.map

Repo: dpdk-next-crypto
35718:
patching file lib/librte_eal/common/eal_common_proc.c
Hunk #1 succeeded at 25 (offset -1 lines).
Hunk #2 succeeded at 39 (offset -1 lines).
Hunk #3 succeeded at 63 (offset -2 lines).
Hunk #4 succeeded at 101 (offset -2 lines).
Hunk #5 succeeded at 178 (offset -13 lines).
Hunk #6 succeeded at 225 with fuzz 1 (offset -137 lines).
Hunk #7 FAILED at 465.
Hunk #8 succeeded at 364 with fuzz 1 (offset -150 lines).
Hunk #9 FAILED at 774.
Hunk #10 succeeded at 653 with fuzz 2 (offset -158 lines).
Hunk #11 FAILED at 831.
Hunk #12 FAILED at 879.
Hunk #13 FAILED at 914.
Hunk #14 succeeded at 926 (offset -54 lines).
Hunk #15 FAILED at 1009.
Hunk #16 succeeded at 949 (offset -72 lines).
6 out of 16 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_proc.c.rej
patching file lib/librte_eal/common/include/rte_eal.h
patching file lib/librte_eal/rte_eal_version.map

Repo: dpdk-next-net
35718:
patching file lib/librte_eal/common/eal_common_proc.c
Hunk #1 succeeded at 25 (offset -1 lines).
Hunk #2 succeeded at 39 (offset -1 lines).
Hunk #3 succeeded at 63 (offset -2 lines).
Hunk #4 succeeded at 101 (offset -2 lines).
Hunk #5 succeeded at 178 (offset -13 lines).
Hunk #6 succeeded at 225 with fuzz 1 (offset -137 lines).
Hunk #7 FAILED at 465.
Hunk #8 succeeded at 364 with fuzz 1 (offset -150 lines).
Hunk #9 FAILED at 774.
Hunk #10 succeeded at 653 with fuzz 2 (offset -158 lines).
Hunk #11 FAILED at 831.
Hunk #12 FAILED at 879.
Hunk #13 FAILED at 914.
Hunk #14 succeeded at 926 (offset -54 lines).
Hunk #15 FAILED at 1009.
Hunk #16 succeeded at 949 (offset -72 lines).
6 out of 16 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_proc.c.rej
patching file lib/librte_eal/common/include/rte_eal.h
patching file lib/librte_eal/rte_eal_version.map

Repo: dpdk-next-virtio
35718:
patching file lib/librte_eal/common/eal_common_proc.c
Hunk #1 succeeded at 25 (offset -1 lines).
Hunk #2 succeeded at 39 (offset -1 lines).
Hunk #3 succeeded at 63 (offset -2 lines).
Hunk #4 succeeded at 101 (offset -2 lines).
Hunk #5 succeeded at 178 (offset -13 lines).
Hunk #6 succeeded at 225 with fuzz 1 (offset -137 lines).
Hunk #7 FAILED at 465.
Hunk #8 succeeded at 364 with fuzz 1 (offset -150 lines).
Hunk #9 FAILED at 774.
Hunk #10 succeeded at 653 with fuzz 2 (offset -158 lines).
Hunk #11 FAILED at 831.
Hunk #12 FAILED at 879.
Hunk #13 FAILED at 914.
Hunk #14 succeeded at 926 (offset -54 lines).
Hunk #15 FAILED at 1009.
Hunk #16 succeeded at 949 (offset -72 lines).
6 out of 16 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_proc.c.rej
patching file lib/librte_eal/common/include/rte_eal.h
patching file lib/librte_eal/rte_eal_version.map

Repo: dpdk-next-eventdev
35718:
patching file lib/librte_eal/common/eal_common_proc.c
Hunk #1 succeeded at 25 (offset -1 lines).
Hunk #2 succeeded at 39 (offset -1 lines).
Hunk #3 succeeded at 63 (offset -2 lines).
Hunk #4 succeeded at 101 (offset -2 lines).
Hunk #5 succeeded at 178 (offset -13 lines).
Hunk #6 succeeded at 225 with fuzz 1 (offset -137 lines).
Hunk #7 FAILED at 465.
Hunk #8 succeeded at 364 with fuzz 1 (offset -150 lines).
Hunk #9 FAILED at 774.
Hunk #10 succeeded at 653 with fuzz 2 (offset -158 lines).
Hunk #11 FAILED at 831.
Hunk #12 FAILED at 879.
Hunk #13 FAILED at 914.
Hunk #14 succeeded at 926 (offset -54 lines).
Hunk #15 FAILED at 1009.
Hunk #16 succeeded at 949 (offset -72 lines).
6 out of 16 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_proc.c.rej
patching file lib/librte_eal/common/include/rte_eal.h
patching file lib/librte_eal/rte_eal_version.map


DPDK STV team

                 reply	other threads:[~2018-03-07 19:26 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='a797f1$12jfde@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=anatoly.burakov@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).