automatic DPDK test reports
 help / color / mirror / Atom feed
* [dpdk-test-report] |FAILURE| pw25857 [PATCH v5 3/4] net/mlx4: support for the RSS flow action
@ 2017-06-28 14:30 sys_stv
  0 siblings, 0 replies; only message in thread
From: sys_stv @ 2017-06-28 14:30 UTC (permalink / raw)
  To: test-report; +Cc: vasilyf

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

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

_apply patch file failure_

Submitter: Vasily Philipov <vasilyf@mellanox.com>
Date: Wed, 28 Jun 2017 17:03:56 +0300
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:c687cebe095b2ea325aa012e2834b830f1f74eba
                   Repo:dpdk-next-crypto, Branch:master, CommitID:46622a025067fa9f16968e74834c0e3d5d18b322
                   Repo:dpdk-next-net, Branch:master, CommitID:02fa0ea6c05696d9018b96b9dcde734872ea893c
                   Repo:dpdk-next-virtio, Branch:master, CommitID:da5129d9b6b53375667690970f6824565c1f1443
                   Repo:dpdk, Branch:master, CommitID:c1923afc0999b5b6f109190bc5b69b6c3d334635
                   
Apply patch file failed:
Repo: dpdk
25857:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 554.
Hunk #2 FAILED at 568.
Hunk #3 FAILED at 587.
Hunk #4 succeeded at 577 (offset -62 lines).
Hunk #5 FAILED at 695.
4 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 355 with fuzz 2 (offset -15 lines).
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_flow.h
Hunk #1 succeeded at 93 (offset -5 lines).

Repo: dpdk-next-crypto
25857:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 554.
Hunk #2 FAILED at 568.
Hunk #3 FAILED at 587.
Hunk #4 succeeded at 577 (offset -62 lines).
Hunk #5 FAILED at 695.
4 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 355 with fuzz 2 (offset -15 lines).
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_flow.h
Hunk #1 succeeded at 93 (offset -5 lines).

Repo: dpdk-next-net
25857:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 554.
Hunk #2 FAILED at 568.
Hunk #3 FAILED at 587.
Hunk #4 succeeded at 571 (offset -68 lines).
Hunk #5 FAILED at 695.
4 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 356 with fuzz 2 (offset -14 lines).
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_flow.h
Hunk #1 succeeded at 93 (offset -5 lines).

Repo: dpdk-next-virtio
25857:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 554.
Hunk #2 FAILED at 568.
Hunk #3 FAILED at 587.
Hunk #4 succeeded at 577 (offset -62 lines).
Hunk #5 FAILED at 695.
4 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 355 with fuzz 2 (offset -15 lines).
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_flow.h
Hunk #1 succeeded at 93 (offset -5 lines).

Repo: dpdk-next-eventdev
25857:
patching file drivers/net/mlx4/mlx4.c
Hunk #1 FAILED at 554.
Hunk #2 FAILED at 568.
Hunk #3 FAILED at 587.
Hunk #4 succeeded at 577 (offset -62 lines).
Hunk #5 FAILED at 695.
4 out of 5 hunks FAILED -- saving rejects to file drivers/net/mlx4/mlx4.c.rej
patching file drivers/net/mlx4/mlx4.h
Hunk #1 succeeded at 355 with fuzz 2 (offset -15 lines).
patching file drivers/net/mlx4/mlx4_flow.c
patching file drivers/net/mlx4/mlx4_flow.h
Hunk #1 succeeded at 93 (offset -5 lines).


DPDK STV team

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

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

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-06-28 14:30 [dpdk-test-report] |FAILURE| pw25857 [PATCH v5 3/4] net/mlx4: support for the RSS flow action 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).