[dpdk-test-report] |FAILURE| pw39858 [PATCH 3/5] crypto/qat: rename log macro for non-dp logs

sys_stv at intel.com sys_stv at intel.com
Mon May 14 10:39:17 CEST 2018
Previous message: [dpdk-test-report] |SUCCESS| pw39927[dpdk-dev] net/mlx5: fix compilation without tunnel RSS support
Next message: [dpdk-test-report] |FAILURE| pw39859 [PATCH 4/5] crypto/qat: move to dynamic logging for data-path trace
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/39858

_apply patch file failure_

Submitter: Fiona Trahe <fiona.trahe at intel.com>
Date: Fri, 11 May 2018 12:31:45 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:3c955492b601d65402c02ac81dfdc7eeb62f23c9
                   Repo:dpdk-next-crypto, Branch:master, CommitID:e0d88a394e91f446234aa04d0f9e01c150b0d347
                   Repo:dpdk-next-net, Branch:master, CommitID:dc33238da4be9cf69e44049cd44950fb4fe74e3b
                   Repo:dpdk-next-virtio, Branch:master, CommitID:037c0996bc927342f157426739e0cb63f2db8689
                   Repo:dpdk, Branch:master, CommitID:3b97888ab2a8405bcbe198abdcc8ac98ee0f0e96
                   
Apply patch file failed:
Repo: dpdk
39858:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_common.c b/drivers/crypto/qat/qat_common.c
|index c10c142..c206d3b 100644
|--- a/drivers/crypto/qat/qat_common.c
|+++ b/drivers/crypto/qat/qat_common.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
can't find file to patch at input line 60
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_device.c b/drivers/crypto/qat/qat_device.c
|index 0cab2e9..4b97c84 100644
|--- a/drivers/crypto/qat/qat_device.c
|+++ b/drivers/crypto/qat/qat_device.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
patching file drivers/crypto/qat/qat_logs.h
patching file drivers/crypto/qat/qat_qp.c
Hunk #1 succeeded at 60 (offset -65 lines).
Hunk #2 succeeded at 73 (offset -65 lines).
Hunk #3 FAILED at 155.
Hunk #4 succeeded at 124 with fuzz 1 (offset -51 lines).
Hunk #5 succeeded at 132 with fuzz 1 (offset -51 lines).
Hunk #6 FAILED at 193.
Hunk #7 FAILED at 215.
Hunk #8 succeeded at 169 with fuzz 1 (offset -55 lines).
Hunk #9 FAILED at 241.
Hunk #10 FAILED at 261.
Hunk #11 FAILED at 298.
Hunk #12 succeeded at 289 (offset -21 lines).
Hunk #13 succeeded at 309 with fuzz 2 (offset -27 lines).
Hunk #14 succeeded at 324 with fuzz 2 (offset -27 lines).
Hunk #15 succeeded at 332 with fuzz 1 (offset -27 lines).
Hunk #16 FAILED at 368.
Hunk #17 FAILED at 378.
Hunk #18 FAILED at 399.
Hunk #19 succeeded at 395 (offset -37 lines).
9 out of 19 hunks FAILED -- saving rejects to file drivers/crypto/qat/qat_qp.c.rej
can't find file to patch at input line 353
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym.c b/drivers/crypto/qat/qat_sym.c
|index 887d4eb..7bedad3 100644
|--- a/drivers/crypto/qat/qat_sym.c
|+++ b/drivers/crypto/qat/qat_sym.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
7 out of 7 hunks ignored
can't find file to patch at input line 434
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym.h b/drivers/crypto/qat/qat_sym.h
|index ddd0f47..b693a4d 100644
|--- a/drivers/crypto/qat/qat_sym.h
|+++ b/drivers/crypto/qat/qat_sym.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 447
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_pmd.c b/drivers/crypto/qat/qat_sym_pmd.c
|index 8797c0e..1156390 100644
|--- a/drivers/crypto/qat/qat_sym_pmd.c
|+++ b/drivers/crypto/qat/qat_sym_pmd.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
6 out of 6 hunks ignored
can't find file to patch at input line 512
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_session.c b/drivers/crypto/qat/qat_sym_session.c
|index 83d0fb1..dc1c200 100644
|--- a/drivers/crypto/qat/qat_sym_session.c
|+++ b/drivers/crypto/qat/qat_sym_session.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
41 out of 41 hunks ignored

Repo: dpdk-next-crypto
39858:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_common.c b/drivers/crypto/qat/qat_common.c
|index c10c142..c206d3b 100644
|--- a/drivers/crypto/qat/qat_common.c
|+++ b/drivers/crypto/qat/qat_common.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
can't find file to patch at input line 60
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_device.c b/drivers/crypto/qat/qat_device.c
|index 0cab2e9..4b97c84 100644
|--- a/drivers/crypto/qat/qat_device.c
|+++ b/drivers/crypto/qat/qat_device.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
patching file drivers/crypto/qat/qat_logs.h
patching file drivers/crypto/qat/qat_qp.c
Hunk #1 succeeded at 60 (offset -65 lines).
Hunk #2 succeeded at 73 (offset -65 lines).
Hunk #3 FAILED at 155.
Hunk #4 succeeded at 124 with fuzz 1 (offset -51 lines).
Hunk #5 succeeded at 132 with fuzz 1 (offset -51 lines).
Hunk #6 FAILED at 193.
Hunk #7 FAILED at 215.
Hunk #8 succeeded at 169 with fuzz 1 (offset -55 lines).
Hunk #9 FAILED at 241.
Hunk #10 FAILED at 261.
Hunk #11 FAILED at 298.
Hunk #12 succeeded at 289 (offset -21 lines).
Hunk #13 succeeded at 309 with fuzz 2 (offset -27 lines).
Hunk #14 succeeded at 324 with fuzz 2 (offset -27 lines).
Hunk #15 succeeded at 332 with fuzz 1 (offset -27 lines).
Hunk #16 FAILED at 368.
Hunk #17 FAILED at 378.
Hunk #18 FAILED at 399.
Hunk #19 succeeded at 395 (offset -37 lines).
9 out of 19 hunks FAILED -- saving rejects to file drivers/crypto/qat/qat_qp.c.rej
can't find file to patch at input line 353
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym.c b/drivers/crypto/qat/qat_sym.c
|index 887d4eb..7bedad3 100644
|--- a/drivers/crypto/qat/qat_sym.c
|+++ b/drivers/crypto/qat/qat_sym.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
7 out of 7 hunks ignored
can't find file to patch at input line 434
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym.h b/drivers/crypto/qat/qat_sym.h
|index ddd0f47..b693a4d 100644
|--- a/drivers/crypto/qat/qat_sym.h
|+++ b/drivers/crypto/qat/qat_sym.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 447
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_pmd.c b/drivers/crypto/qat/qat_sym_pmd.c
|index 8797c0e..1156390 100644
|--- a/drivers/crypto/qat/qat_sym_pmd.c
|+++ b/drivers/crypto/qat/qat_sym_pmd.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
6 out of 6 hunks ignored
can't find file to patch at input line 512
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_session.c b/drivers/crypto/qat/qat_sym_session.c
|index 83d0fb1..dc1c200 100644
|--- a/drivers/crypto/qat/qat_sym_session.c
|+++ b/drivers/crypto/qat/qat_sym_session.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
41 out of 41 hunks ignored

Repo: dpdk-next-net
39858:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_common.c b/drivers/crypto/qat/qat_common.c
|index c10c142..c206d3b 100644
|--- a/drivers/crypto/qat/qat_common.c
|+++ b/drivers/crypto/qat/qat_common.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
can't find file to patch at input line 60
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_device.c b/drivers/crypto/qat/qat_device.c
|index 0cab2e9..4b97c84 100644
|--- a/drivers/crypto/qat/qat_device.c
|+++ b/drivers/crypto/qat/qat_device.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
patching file drivers/crypto/qat/qat_logs.h
patching file drivers/crypto/qat/qat_qp.c
Hunk #1 succeeded at 60 (offset -65 lines).
Hunk #2 succeeded at 73 (offset -65 lines).
Hunk #3 FAILED at 155.
Hunk #4 succeeded at 124 with fuzz 1 (offset -51 lines).
Hunk #5 succeeded at 132 with fuzz 1 (offset -51 lines).
Hunk #6 FAILED at 193.
Hunk #7 FAILED at 215.
Hunk #8 succeeded at 169 with fuzz 1 (offset -55 lines).
Hunk #9 FAILED at 241.
Hunk #10 FAILED at 261.
Hunk #11 FAILED at 298.
Hunk #12 succeeded at 289 (offset -21 lines).
Hunk #13 succeeded at 309 with fuzz 2 (offset -27 lines).
Hunk #14 succeeded at 324 with fuzz 2 (offset -27 lines).
Hunk #15 succeeded at 332 with fuzz 1 (offset -27 lines).
Hunk #16 FAILED at 368.
Hunk #17 FAILED at 378.
Hunk #18 FAILED at 399.
Hunk #19 succeeded at 395 (offset -37 lines).
9 out of 19 hunks FAILED -- saving rejects to file drivers/crypto/qat/qat_qp.c.rej
can't find file to patch at input line 353
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym.c b/drivers/crypto/qat/qat_sym.c
|index 887d4eb..7bedad3 100644
|--- a/drivers/crypto/qat/qat_sym.c
|+++ b/drivers/crypto/qat/qat_sym.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
7 out of 7 hunks ignored
can't find file to patch at input line 434
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym.h b/drivers/crypto/qat/qat_sym.h
|index ddd0f47..b693a4d 100644
|--- a/drivers/crypto/qat/qat_sym.h
|+++ b/drivers/crypto/qat/qat_sym.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 447
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_pmd.c b/drivers/crypto/qat/qat_sym_pmd.c
|index 8797c0e..1156390 100644
|--- a/drivers/crypto/qat/qat_sym_pmd.c
|+++ b/drivers/crypto/qat/qat_sym_pmd.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
6 out of 6 hunks ignored
can't find file to patch at input line 512
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_session.c b/drivers/crypto/qat/qat_sym_session.c
|index 83d0fb1..dc1c200 100644
|--- a/drivers/crypto/qat/qat_sym_session.c
|+++ b/drivers/crypto/qat/qat_sym_session.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
41 out of 41 hunks ignored

Repo: dpdk-next-virtio
39858:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_common.c b/drivers/crypto/qat/qat_common.c
|index c10c142..c206d3b 100644
|--- a/drivers/crypto/qat/qat_common.c
|+++ b/drivers/crypto/qat/qat_common.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
can't find file to patch at input line 60
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_device.c b/drivers/crypto/qat/qat_device.c
|index 0cab2e9..4b97c84 100644
|--- a/drivers/crypto/qat/qat_device.c
|+++ b/drivers/crypto/qat/qat_device.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
patching file drivers/crypto/qat/qat_logs.h
patching file drivers/crypto/qat/qat_qp.c
Hunk #1 succeeded at 60 (offset -65 lines).
Hunk #2 succeeded at 73 (offset -65 lines).
Hunk #3 FAILED at 155.
Hunk #4 succeeded at 124 with fuzz 1 (offset -51 lines).
Hunk #5 succeeded at 132 with fuzz 1 (offset -51 lines).
Hunk #6 FAILED at 193.
Hunk #7 FAILED at 215.
Hunk #8 succeeded at 169 with fuzz 1 (offset -55 lines).
Hunk #9 FAILED at 241.
Hunk #10 FAILED at 261.
Hunk #11 FAILED at 298.
Hunk #12 succeeded at 289 (offset -21 lines).
Hunk #13 succeeded at 309 with fuzz 2 (offset -27 lines).
Hunk #14 succeeded at 324 with fuzz 2 (offset -27 lines).
Hunk #15 succeeded at 332 with fuzz 1 (offset -27 lines).
Hunk #16 FAILED at 368.
Hunk #17 FAILED at 378.
Hunk #18 FAILED at 399.
Hunk #19 succeeded at 395 (offset -37 lines).
9 out of 19 hunks FAILED -- saving rejects to file drivers/crypto/qat/qat_qp.c.rej
can't find file to patch at input line 353
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym.c b/drivers/crypto/qat/qat_sym.c
|index 887d4eb..7bedad3 100644
|--- a/drivers/crypto/qat/qat_sym.c
|+++ b/drivers/crypto/qat/qat_sym.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
7 out of 7 hunks ignored
can't find file to patch at input line 434
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym.h b/drivers/crypto/qat/qat_sym.h
|index ddd0f47..b693a4d 100644
|--- a/drivers/crypto/qat/qat_sym.h
|+++ b/drivers/crypto/qat/qat_sym.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 447
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_pmd.c b/drivers/crypto/qat/qat_sym_pmd.c
|index 8797c0e..1156390 100644
|--- a/drivers/crypto/qat/qat_sym_pmd.c
|+++ b/drivers/crypto/qat/qat_sym_pmd.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
6 out of 6 hunks ignored
can't find file to patch at input line 512
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_session.c b/drivers/crypto/qat/qat_sym_session.c
|index 83d0fb1..dc1c200 100644
|--- a/drivers/crypto/qat/qat_sym_session.c
|+++ b/drivers/crypto/qat/qat_sym_session.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
41 out of 41 hunks ignored

Repo: dpdk-next-eventdev
39858:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_common.c b/drivers/crypto/qat/qat_common.c
|index c10c142..c206d3b 100644
|--- a/drivers/crypto/qat/qat_common.c
|+++ b/drivers/crypto/qat/qat_common.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
can't find file to patch at input line 60
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_device.c b/drivers/crypto/qat/qat_device.c
|index 0cab2e9..4b97c84 100644
|--- a/drivers/crypto/qat/qat_device.c
|+++ b/drivers/crypto/qat/qat_device.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
5 out of 5 hunks ignored
patching file drivers/crypto/qat/qat_logs.h
patching file drivers/crypto/qat/qat_qp.c
Hunk #1 succeeded at 60 (offset -65 lines).
Hunk #2 succeeded at 73 (offset -65 lines).
Hunk #3 FAILED at 155.
Hunk #4 succeeded at 124 with fuzz 1 (offset -51 lines).
Hunk #5 succeeded at 132 with fuzz 1 (offset -51 lines).
Hunk #6 FAILED at 193.
Hunk #7 FAILED at 215.
Hunk #8 succeeded at 169 with fuzz 1 (offset -55 lines).
Hunk #9 FAILED at 241.
Hunk #10 FAILED at 261.
Hunk #11 FAILED at 298.
Hunk #12 succeeded at 289 (offset -21 lines).
Hunk #13 succeeded at 309 with fuzz 2 (offset -27 lines).
Hunk #14 succeeded at 324 with fuzz 2 (offset -27 lines).
Hunk #15 succeeded at 332 with fuzz 1 (offset -27 lines).
Hunk #16 FAILED at 368.
Hunk #17 FAILED at 378.
Hunk #18 FAILED at 399.
Hunk #19 succeeded at 395 (offset -37 lines).
9 out of 19 hunks FAILED -- saving rejects to file drivers/crypto/qat/qat_qp.c.rej
can't find file to patch at input line 353
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym.c b/drivers/crypto/qat/qat_sym.c
|index 887d4eb..7bedad3 100644
|--- a/drivers/crypto/qat/qat_sym.c
|+++ b/drivers/crypto/qat/qat_sym.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
7 out of 7 hunks ignored
can't find file to patch at input line 434
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym.h b/drivers/crypto/qat/qat_sym.h
|index ddd0f47..b693a4d 100644
|--- a/drivers/crypto/qat/qat_sym.h
|+++ b/drivers/crypto/qat/qat_sym.h
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 447
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_pmd.c b/drivers/crypto/qat/qat_sym_pmd.c
|index 8797c0e..1156390 100644
|--- a/drivers/crypto/qat/qat_sym_pmd.c
|+++ b/drivers/crypto/qat/qat_sym_pmd.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
6 out of 6 hunks ignored
can't find file to patch at input line 512
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/qat/qat_sym_session.c b/drivers/crypto/qat/qat_sym_session.c
|index 83d0fb1..dc1c200 100644
|--- a/drivers/crypto/qat/qat_sym_session.c
|+++ b/drivers/crypto/qat/qat_sym_session.c
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
41 out of 41 hunks ignored


DPDK STV team
Previous message: [dpdk-test-report] |SUCCESS| pw39927[dpdk-dev] net/mlx5: fix compilation without tunnel RSS support
Next message: [dpdk-test-report] |FAILURE| pw39859 [PATCH 4/5] crypto/qat: move to dynamic logging for data-path trace
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the test-report mailing list