automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: gaetan.rivet@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw21339 [PATCH 2/5] net/mlx4: device removal event support
Date: 06 Mar 2017 15:19:37 -0800	[thread overview]
Message-ID: <e81775$11bchab@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Gaetan Rivet <gaetan.rivet@6wind.com>
Date: Fri,  3 Mar 2017 16:40:20 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:720dbd63fd5083f8cacd6c59aa3f2651121d562a
                   Repo:dpdk-next-crypto, Branch:master, CommitID:13f57aba3e9f4f6818f525c2e402ac75d5ec7967
                   Repo:dpdk-next-net, Branch:master, CommitID:3aebbdad639c264ce7aef94582ecaddf208ca547
                   Repo:dpdk-next-virtio, Branch:master, CommitID:14d3a8536b51f9c1e7d65bcf536b5b348ead1ec1
                   Repo:dpdk, Branch:master, CommitID:b0c958e14dee3570a684fafb0ef5ca9c86c6f80d
                   
Apply patch file failed:
Repo: dpdk
21339:
patching file doc/guides/nics/features/mlx4.ini
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 4092 (offset 161 lines).
Hunk #2 FAILED at 3992.
Hunk #3 succeeded at 4264 (offset 153 lines).
Hunk #4 succeeded at 4336 (offset 153 lines).
Hunk #5 succeeded at 4897 (offset 153 lines).
Hunk #6 succeeded at 5382 (offset 103 lines).
Hunk #7 succeeded at 5434 (offset 103 lines).
Hunk #8 succeeded at 5452 (offset 103 lines).
Hunk #9 succeeded at 5477 (offset 103 lines).
Hunk #10 succeeded at 5507 (offset 103 lines).
Hunk #11 succeeded at 5540 with fuzz 1 (offset 103 lines).
Hunk #12 succeeded at 6070 (offset 7 lines).
1 out of 12 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 356.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej

Repo: dpdk-next-crypto
21339:
patching file doc/guides/nics/features/mlx4.ini
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 4092 (offset 161 lines).
Hunk #2 FAILED at 3992.
Hunk #3 succeeded at 4264 (offset 153 lines).
Hunk #4 succeeded at 4336 (offset 153 lines).
Hunk #5 succeeded at 4897 (offset 153 lines).
Hunk #6 succeeded at 5382 (offset 103 lines).
Hunk #7 succeeded at 5434 (offset 103 lines).
Hunk #8 succeeded at 5452 (offset 103 lines).
Hunk #9 succeeded at 5477 (offset 103 lines).
Hunk #10 succeeded at 5507 (offset 103 lines).
Hunk #11 succeeded at 5540 with fuzz 1 (offset 103 lines).
Hunk #12 succeeded at 6070 (offset 7 lines).
1 out of 12 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 356.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej

Repo: dpdk-next-net
21339:
patching file doc/guides/nics/features/mlx4.ini
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 4092 (offset 161 lines).
Hunk #2 FAILED at 3992.
Hunk #3 succeeded at 4264 (offset 153 lines).
Hunk #4 succeeded at 4336 (offset 153 lines).
Hunk #5 succeeded at 4897 (offset 153 lines).
Hunk #6 succeeded at 5382 (offset 103 lines).
Hunk #7 succeeded at 5434 (offset 103 lines).
Hunk #8 succeeded at 5452 (offset 103 lines).
Hunk #9 succeeded at 5477 (offset 103 lines).
Hunk #10 succeeded at 5507 (offset 103 lines).
Hunk #11 succeeded at 5540 with fuzz 1 (offset 103 lines).
Hunk #12 succeeded at 6070 (offset 7 lines).
1 out of 12 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 356.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej

Repo: dpdk-next-virtio
21339:
patching file doc/guides/nics/features/mlx4.ini
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 4092 (offset 161 lines).
Hunk #2 FAILED at 3992.
Hunk #3 succeeded at 4264 (offset 153 lines).
Hunk #4 succeeded at 4336 (offset 153 lines).
Hunk #5 succeeded at 4897 (offset 153 lines).
Hunk #6 succeeded at 5382 (offset 103 lines).
Hunk #7 succeeded at 5434 (offset 103 lines).
Hunk #8 succeeded at 5452 (offset 103 lines).
Hunk #9 succeeded at 5477 (offset 103 lines).
Hunk #10 succeeded at 5507 (offset 103 lines).
Hunk #11 succeeded at 5540 with fuzz 1 (offset 103 lines).
Hunk #12 succeeded at 6070 (offset 7 lines).
1 out of 12 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 356.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej

Repo: dpdk-next-eventdev
21339:
patching file doc/guides/nics/features/mlx4.ini
patching file drivers/net/mlx4/mlx4.c
Hunk #1 succeeded at 4092 (offset 161 lines).
Hunk #2 FAILED at 3992.
Hunk #3 succeeded at 4264 (offset 153 lines).
Hunk #4 succeeded at 4336 (offset 153 lines).
Hunk #5 succeeded at 4897 (offset 153 lines).
Hunk #6 succeeded at 5382 (offset 103 lines).
Hunk #7 succeeded at 5434 (offset 103 lines).
Hunk #8 succeeded at 5452 (offset 103 lines).
Hunk #9 succeeded at 5477 (offset 103 lines).
Hunk #10 succeeded at 5507 (offset 103 lines).
Hunk #11 succeeded at 5540 with fuzz 1 (offset 103 lines).
Hunk #12 succeeded at 6070 (offset 7 lines).
1 out of 12 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 FAILED at 356.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/mlx4.h.rej


DPDK STV team

                 reply	other threads:[~2017-03-06 23:19 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='e81775$11bchab@fmsmga001.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=gaetan.rivet@6wind.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).