automatic DPDK test reports
 help / color / mirror / Atom feed
* [dpdk-test-report] |FAILURE| pw28247 [PATCH v2 48/51] net/mlx4: separate memory management functions
@ 2017-09-04 14:06 sys_stv
  0 siblings, 0 replies; only message in thread
From: sys_stv @ 2017-09-04 14:06 UTC (permalink / raw)
  To: test-report; +Cc: adrien.mazarguil

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

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

_apply patch file failure_

Submitter: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Date: Fri,  1 Sep 2017 10:06:50 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:85238f501ec36bc6f0e15e6434296312841259bd
                   Repo:dpdk-next-crypto, Branch:master, CommitID:85238f501ec36bc6f0e15e6434296312841259bd
                   Repo:dpdk-next-net, Branch:master, CommitID:5c489b4543c1ee73bc180f13065c5c5f0633dcb4
                   Repo:dpdk-next-virtio, Branch:master, CommitID:6c157fe64650167646ff1312f9f7e7dc3674d7eb
                   Repo:dpdk, Branch:master, CommitID:06791a4bcedf3eb97f05c13debff90272e3b0d54
                   
Apply patch file failed:
Repo: dpdk
28247:
patching file drivers/net/mlx4/Makefile
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/Makefile.rej
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 48.
Hunk #2 FAILED at 110.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 162 (offset 47 lines).
Hunk #2 succeeded at 187 (offset 47 lines).
patching file drivers/net/mlx4/mlx4_mr.c

Repo: dpdk-next-crypto
28247:
patching file drivers/net/mlx4/Makefile
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/Makefile.rej
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 48.
Hunk #2 FAILED at 110.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 162 (offset 47 lines).
Hunk #2 succeeded at 187 (offset 47 lines).
patching file drivers/net/mlx4/mlx4_mr.c

Repo: dpdk-next-net
28247:
patching file drivers/net/mlx4/Makefile
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/Makefile.rej
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 48.
Hunk #2 FAILED at 110.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 162 (offset 47 lines).
Hunk #2 succeeded at 187 (offset 47 lines).
patching file drivers/net/mlx4/mlx4_mr.c

Repo: dpdk-next-virtio
28247:
patching file drivers/net/mlx4/Makefile
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/Makefile.rej
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 48.
Hunk #2 FAILED at 110.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 156 (offset 41 lines).
Hunk #2 succeeded at 181 (offset 41 lines).
patching file drivers/net/mlx4/mlx4_mr.c

Repo: dpdk-next-eventdev
28247:
patching file drivers/net/mlx4/Makefile
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file drivers/net/mlx4/Makefile.rej
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 48.
Hunk #2 FAILED at 110.
2 out of 2 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 162 (offset 47 lines).
Hunk #2 succeeded at 187 (offset 47 lines).
patching file drivers/net/mlx4/mlx4_mr.c


DPDK STV team

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2017-09-04 14:06 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-09-04 14:06 [dpdk-test-report] |FAILURE| pw28247 [PATCH v2 48/51] net/mlx4: separate memory management functions sys_stv

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).