automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: rasland@mellanox.com
Subject: [dpdk-test-report] |FAILURE| pw29480 [PATCH 1/3] ethdev: add Rx HW timestamp capability
Date: 02 Oct 2017 08:17:51 -0700	[thread overview]
Message-ID: <1a8a4b$13pki9h@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Raslan Darawsheh <rasland@mellanox.com>
Date: Mon,  2 Oct 2017 17:50:41 +0300
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:b4b3260b63d2d8d76ff1c66ab4b70e6d1b6a4bbe
                   Repo:dpdk-next-crypto, Branch:master, CommitID:51c8fe28d6f6c7329c86a695afc5c7def741fe94
                   Repo:dpdk-next-net, Branch:master, CommitID:b4fd9dcfcec56db1caa127cd03362500f9d5bd6b
                   Repo:dpdk-next-virtio, Branch:master, CommitID:fee08fe0d67d46639d25c201738d9b1b867e443c
                   Repo:dpdk, Branch:master, CommitID:5dce9fcdb2308becb7de7470118af3eeccfe4fd7
                   
Apply patch file failed:
Repo: dpdk
29480:
patching file doc/guides/nics/features.rst
patching file lib/librte_ether/rte_ethdev.c
Hunk #1 FAILED at 715.
Hunk #2 FAILED at 763.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_ether/rte_ethdev.c.rej
patching file lib/librte_ether/rte_ethdev.h
Hunk #1 succeeded at 357 (offset -11 lines).
Hunk #2 succeeded at 908 (offset -17 lines).

Repo: dpdk-next-crypto
29480:
patching file doc/guides/nics/features.rst
patching file lib/librte_ether/rte_ethdev.c
Hunk #1 FAILED at 715.
Hunk #2 FAILED at 763.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_ether/rte_ethdev.c.rej
patching file lib/librte_ether/rte_ethdev.h
Hunk #1 succeeded at 357 (offset -11 lines).
Hunk #2 succeeded at 908 (offset -17 lines).

Repo: dpdk-next-net
29480:
patching file doc/guides/nics/features.rst
patching file lib/librte_ether/rte_ethdev.c
Hunk #1 FAILED at 715.
Hunk #2 FAILED at 763.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_ether/rte_ethdev.c.rej
patching file lib/librte_ether/rte_ethdev.h
Hunk #1 succeeded at 357 (offset -11 lines).
Hunk #2 succeeded at 908 (offset -17 lines).

Repo: dpdk-next-virtio
29480:
patching file doc/guides/nics/features.rst
Hunk #1 succeeded at 567 (offset 1 line).
patching file lib/librte_ether/rte_ethdev.c
Hunk #1 FAILED at 715.
Hunk #2 FAILED at 763.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_ether/rte_ethdev.c.rej
patching file lib/librte_ether/rte_ethdev.h
Hunk #1 succeeded at 357 (offset -11 lines).
Hunk #2 succeeded at 908 (offset -17 lines).

Repo: dpdk-next-eventdev
29480:
patching file doc/guides/nics/features.rst
patching file lib/librte_ether/rte_ethdev.c
Hunk #1 FAILED at 715.
Hunk #2 FAILED at 763.
2 out of 2 hunks FAILED -- saving rejects to file lib/librte_ether/rte_ethdev.c.rej
patching file lib/librte_ether/rte_ethdev.h
Hunk #1 succeeded at 357 (offset -11 lines).
Hunk #2 succeeded at 908 (offset -17 lines).


DPDK STV team

                 reply	other threads:[~2017-10-02 15:17 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='1a8a4b$13pki9h@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=rasland@mellanox.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).