* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 13:10 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 13:10 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-10 0:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-10 0:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-10 0:29 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-10 0:29 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-10 0:10 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-10 0:10 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-10 0:03 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-10 0:03 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 23:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 23:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 23:27 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 23:27 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 23:12 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 23:12 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 22:57 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 22:57 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 22:46 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 22:46 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 22:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 22:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 22:21 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 22:21 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 21:57 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 21:57 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 21:42 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 21:42 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 21:27 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 21:27 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 21:16 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 21:16 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 20:59 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 20:59 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 20:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 20:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 20:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 20:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 20:10 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 20:10 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 19:55 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 19:55 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 19:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 19:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 19:38 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 19:38 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 19:14 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 19:14 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 19:01 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 19:01 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 18:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 18:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 18:31 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 18:31 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 18:12 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 18:12 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 18:01 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 18:01 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 17:46 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 17:46 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 17:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 17:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 17:12 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 17:12 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 16:57 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 16:57 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 16:46 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 16:46 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 16:38 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 16:38 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 16:21 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 16:21 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 15:57 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 15:57 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 15:42 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 15:42 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 15:33 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 15:33 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 15:18 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 15:18 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 14:57 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 14:57 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 14:42 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 14:42 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 14:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 14:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 14:14 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 14:14 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 13:55 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 13:55 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 13:44 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 13:44 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 13:33 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 13:33 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 13:03 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 13:03 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 12:49 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 12:49 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 12:29 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 12:29 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 12:12 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 12:12 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 11:55 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 11:55 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 11:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 11:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 11:34 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 11:34 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 11:14 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 11:14 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 10:55 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 10:55 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 10:51 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 10:51 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 10:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 10:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 10:12 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 10:12 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 10:01 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 10:01 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 9:48 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 9:48 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 9:27 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 9:27 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 9:12 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 9:12 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 8:59 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 8:59 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 8:42 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 8:42 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 8:29 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 8:29 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 8:12 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 8:12 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 7:57 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 7:57 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 7:44 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 7:44 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 7:27 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 7:27 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 7:10 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 7:10 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 6:55 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 6:55 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 6:44 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 6:44 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 6:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 6:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 6:16 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 6:16 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 5:59 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 5:59 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 5:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 5:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 5:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 5:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 5:12 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 5:12 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 5:04 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 5:04 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 4:51 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 4:51 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 4:27 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 4:27 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 4:10 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 4:10 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 3:55 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 3:55 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 3:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 3:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 3:31 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 3:31 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 3:12 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 3:12 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 2:57 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 2:57 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 2:51 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 2:51 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 2:27 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 2:27 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 2:16 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 2:16 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 1:59 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 1:59 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 1:48 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 1:48 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 1:33 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 1:33 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 1:10 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 1:10 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 0:55 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 0:55 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 0:49 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 0:49 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 0:34 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 0:34 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-09 0:12 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-09 0:12 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 23:55 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 23:55 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 23:48 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 23:48 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 23:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 23:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 23:10 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 23:10 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 22:55 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 22:55 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 22:44 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 22:44 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 22:29 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 22:29 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 22:12 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 22:12 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 21:59 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 21:59 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 21:44 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 21:44 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 21:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 21:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 21:14 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 21:14 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 21:03 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 21:03 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 20:48 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 20:48 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 20:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 20:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 20:14 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 20:14 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 19:55 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 19:55 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 19:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 19:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 19:33 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 19:33 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 19:14 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 19:14 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 18:59 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 18:59 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 18:44 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 18:44 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 18:34 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 18:34 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 18:10 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 18:10 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 18:01 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 18:01 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 17:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 17:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 17:36 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 17:36 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 17:19 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 17:19 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 16:55 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 16:55 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 16:42 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 16:42 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 16:27 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 16:27 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 16:10 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 16:10 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 15:55 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 15:55 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 15:51 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 15:51 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 15:27 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 15:27 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 15:14 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 15:14 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 14:55 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 14:55 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 14:44 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 14:44 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 14:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 14:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 14:10 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 14:10 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 13:57 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 13:57 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 13:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 13:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 13:29 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 13:29 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 13:16 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 13:16 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 12:59 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 12:59 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 12:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 12:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 12:29 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 12:29 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 12:14 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 12:14 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 12:06 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 12:06 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 11:51 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 11:51 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 11:27 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 11:27 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 11:21 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 11:21 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 10:55 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 10:55 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 10:44 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 10:44 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 10:29 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 10:29 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 10:21 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 10:21 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 9:57 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 9:57 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 9:42 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 9:42 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 9:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 9:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 9:14 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 9:14 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 8:59 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 8:59 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 8:51 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 8:51 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 8:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 8:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 8:21 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 8:21 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 7:59 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 7:59 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 7:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 7:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 7:36 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 7:36 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 7:14 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 7:14 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 7:06 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 7:06 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 6:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 6:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 6:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 6:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 6:10 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 6:10 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 5:55 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 5:55 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 5:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 5:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 5:31 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 5:31 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 5:12 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 5:12 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 4:59 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 4:59 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 4:42 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 4:42 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 4:29 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 4:29 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 4:12 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 4:12 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 4:06 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 4:06 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 3:42 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 3:42 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 3:31 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 3:31 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 3:18 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 3:18 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 2:59 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 2:59 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 2:51 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 2:51 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 2:27 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 2:27 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 2:18 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 2:18 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 1:59 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 1:59 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 1:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 1:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 1:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 1:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 1:14 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 1:14 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 0:57 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 0:57 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 0:42 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 0:42 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 0:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 0:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-08 0:12 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-08 0:12 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 23:59 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 23:59 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 23:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 23:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 23:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 23:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 23:10 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 23:10 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 22:59 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 22:59 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 22:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 22:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 22:33 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 22:33 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 22:12 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 22:12 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 21:57 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 21:57 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 21:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 21:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 21:31 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 21:31 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 21:14 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 21:14 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 21:01 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 21:01 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 20:44 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 20:44 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 20:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 20:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 20:16 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 20:16 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 20:01 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 20:01 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 19:46 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 19:46 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 19:29 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 19:29 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 19:18 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 19:18 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 19:03 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 19:03 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 18:40 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 18:40 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 18:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 18:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 18:11 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 18:11 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 17:59 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 17:59 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 17:48 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 17:48 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 17:27 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 17:27 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 17:12 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 17:12 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 16:57 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 16:57 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 16:42 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 16:42 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 16:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 16:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 16:10 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 16:10 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 16:06 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 16:06 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 15:41 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 15:41 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 15:27 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 15:27 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 15:10 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 15:10 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 14:57 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 14:57 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 14:45 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 14:45 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 14:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 14:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 14:10 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 14:10 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 14:06 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 14:06 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 13:42 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 13:42 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 13:27 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 13:27 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 13:16 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 13:16 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 12:59 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 12:59 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 12:51 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 12:51 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 12:27 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 12:27 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 12:10 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 12:10 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 12:03 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 12:03 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 11:49 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 11:49 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 11:25 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 11:25 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 11:10 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 11:10 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 11:01 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 11:01 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 10:49 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 10:49 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 10:29 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 10:29 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 10:14 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 10:14 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 9:55 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 9:55 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 9:42 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 9:42 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
* [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support
@ 2017-04-07 9:29 sys_stv
0 siblings, 0 replies; 254+ messages in thread
From: sys_stv @ 2017-04-07 9:29 UTC (permalink / raw)
To: test-report; +Cc: roy.fan.zhang
[-- Attachment #1: Type: text/plain, Size: 7669 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23232
_apply patch file failure_
Submitter: Fan Zhang <roy.fan.zhang@intel.com>
Date: Wed, 5 Apr 2017 10:02:23 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:bf6933813312c4440947991b2e1d129450d3ec11
Repo:dpdk-next-net, Branch:master, CommitID:4e66a6fef321d8015f6bde1aac5018c9ec91721c
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Apply patch file failed:
Repo: dpdk
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-crypto
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 479 (offset 13 lines).
Hunk #2 succeeded at 530 (offset 13 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #2 succeeded at 222 (offset 27 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
patching file drivers/crypto/scheduler/scheduler_failover.c
patching file drivers/crypto/scheduler/scheduler_pkt_size_distr.c
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Repo: dpdk-next-net
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-virtio
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
Repo: dpdk-next-eventdev
23232:
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.c
Hunk #1 succeeded at 451 (offset -15 lines).
Hunk #2 succeeded at 471 with fuzz 2 (offset -46 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler.h
Hunk #1 succeeded at 54 (offset -16 lines).
Hunk #2 succeeded at 160 with fuzz 2 (offset -35 lines).
patching file drivers/crypto/scheduler/rte_cryptodev_scheduler_operations.h
patching file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/scheduler/rte_pmd_crypto_scheduler_version.map.rej
can't find file to patch at input line 239
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_failover.c b/drivers/crypto/scheduler/scheduler_failover.c
|index 6359f04..2471a5f 100644
|--- a/drivers/crypto/scheduler/scheduler_failover.c
|+++ b/drivers/crypto/scheduler/scheduler_failover.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 252
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|index 1066451..94196d9 100644
|--- a/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
|+++ b/drivers/crypto/scheduler/scheduler_pkt_size_distr.c
--------------------------
File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
patching file drivers/crypto/scheduler/scheduler_roundrobin.c
Hunk #1 succeeded at 421 (offset 156 lines).
DPDK STV team
^ permalink raw reply [flat|nested] 254+ messages in thread
end of thread, other threads:[~2017-04-10 0:40 UTC | newest]
Thread overview: 254+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-04-09 13:10 [dpdk-test-report] |FAILURE| pw23232 [PATCH v3] crypto/scheduler: add mode specific option support sys_stv
-- strict thread matches above, loose matches on Subject: below --
2017-04-10 0:40 sys_stv
2017-04-10 0:29 sys_stv
2017-04-10 0:10 sys_stv
2017-04-10 0:03 sys_stv
2017-04-09 23:40 sys_stv
2017-04-09 23:27 sys_stv
2017-04-09 23:12 sys_stv
2017-04-09 22:57 sys_stv
2017-04-09 22:46 sys_stv
2017-04-09 22:25 sys_stv
2017-04-09 22:21 sys_stv
2017-04-09 21:57 sys_stv
2017-04-09 21:42 sys_stv
2017-04-09 21:27 sys_stv
2017-04-09 21:16 sys_stv
2017-04-09 20:59 sys_stv
2017-04-09 20:40 sys_stv
2017-04-09 20:25 sys_stv
2017-04-09 20:10 sys_stv
2017-04-09 19:55 sys_stv
2017-04-09 19:40 sys_stv
2017-04-09 19:38 sys_stv
2017-04-09 19:14 sys_stv
2017-04-09 19:01 sys_stv
2017-04-09 18:40 sys_stv
2017-04-09 18:31 sys_stv
2017-04-09 18:12 sys_stv
2017-04-09 18:01 sys_stv
2017-04-09 17:46 sys_stv
2017-04-09 17:25 sys_stv
2017-04-09 17:12 sys_stv
2017-04-09 16:57 sys_stv
2017-04-09 16:46 sys_stv
2017-04-09 16:38 sys_stv
2017-04-09 16:21 sys_stv
2017-04-09 15:57 sys_stv
2017-04-09 15:42 sys_stv
2017-04-09 15:33 sys_stv
2017-04-09 15:18 sys_stv
2017-04-09 14:57 sys_stv
2017-04-09 14:42 sys_stv
2017-04-09 14:25 sys_stv
2017-04-09 14:14 sys_stv
2017-04-09 13:55 sys_stv
2017-04-09 13:44 sys_stv
2017-04-09 13:33 sys_stv
2017-04-09 13:03 sys_stv
2017-04-09 12:49 sys_stv
2017-04-09 12:29 sys_stv
2017-04-09 12:12 sys_stv
2017-04-09 11:55 sys_stv
2017-04-09 11:40 sys_stv
2017-04-09 11:34 sys_stv
2017-04-09 11:14 sys_stv
2017-04-09 10:55 sys_stv
2017-04-09 10:51 sys_stv
2017-04-09 10:25 sys_stv
2017-04-09 10:12 sys_stv
2017-04-09 10:01 sys_stv
2017-04-09 9:48 sys_stv
2017-04-09 9:27 sys_stv
2017-04-09 9:12 sys_stv
2017-04-09 8:59 sys_stv
2017-04-09 8:42 sys_stv
2017-04-09 8:29 sys_stv
2017-04-09 8:12 sys_stv
2017-04-09 7:57 sys_stv
2017-04-09 7:44 sys_stv
2017-04-09 7:27 sys_stv
2017-04-09 7:10 sys_stv
2017-04-09 6:55 sys_stv
2017-04-09 6:44 sys_stv
2017-04-09 6:25 sys_stv
2017-04-09 6:16 sys_stv
2017-04-09 5:59 sys_stv
2017-04-09 5:40 sys_stv
2017-04-09 5:25 sys_stv
2017-04-09 5:12 sys_stv
2017-04-09 5:04 sys_stv
2017-04-09 4:51 sys_stv
2017-04-09 4:27 sys_stv
2017-04-09 4:10 sys_stv
2017-04-09 3:55 sys_stv
2017-04-09 3:40 sys_stv
2017-04-09 3:31 sys_stv
2017-04-09 3:12 sys_stv
2017-04-09 2:57 sys_stv
2017-04-09 2:51 sys_stv
2017-04-09 2:27 sys_stv
2017-04-09 2:16 sys_stv
2017-04-09 1:59 sys_stv
2017-04-09 1:48 sys_stv
2017-04-09 1:33 sys_stv
2017-04-09 1:10 sys_stv
2017-04-09 0:55 sys_stv
2017-04-09 0:49 sys_stv
2017-04-09 0:34 sys_stv
2017-04-09 0:12 sys_stv
2017-04-08 23:55 sys_stv
2017-04-08 23:48 sys_stv
2017-04-08 23:25 sys_stv
2017-04-08 23:10 sys_stv
2017-04-08 22:55 sys_stv
2017-04-08 22:44 sys_stv
2017-04-08 22:29 sys_stv
2017-04-08 22:12 sys_stv
2017-04-08 21:59 sys_stv
2017-04-08 21:44 sys_stv
2017-04-08 21:25 sys_stv
2017-04-08 21:14 sys_stv
2017-04-08 21:03 sys_stv
2017-04-08 20:48 sys_stv
2017-04-08 20:25 sys_stv
2017-04-08 20:14 sys_stv
2017-04-08 19:55 sys_stv
2017-04-08 19:40 sys_stv
2017-04-08 19:33 sys_stv
2017-04-08 19:14 sys_stv
2017-04-08 18:59 sys_stv
2017-04-08 18:44 sys_stv
2017-04-08 18:34 sys_stv
2017-04-08 18:10 sys_stv
2017-04-08 18:01 sys_stv
2017-04-08 17:40 sys_stv
2017-04-08 17:36 sys_stv
2017-04-08 17:19 sys_stv
2017-04-08 16:55 sys_stv
2017-04-08 16:42 sys_stv
2017-04-08 16:27 sys_stv
2017-04-08 16:10 sys_stv
2017-04-08 15:55 sys_stv
2017-04-08 15:51 sys_stv
2017-04-08 15:27 sys_stv
2017-04-08 15:14 sys_stv
2017-04-08 14:55 sys_stv
2017-04-08 14:44 sys_stv
2017-04-08 14:25 sys_stv
2017-04-08 14:10 sys_stv
2017-04-08 13:57 sys_stv
2017-04-08 13:40 sys_stv
2017-04-08 13:29 sys_stv
2017-04-08 13:16 sys_stv
2017-04-08 12:59 sys_stv
2017-04-08 12:40 sys_stv
2017-04-08 12:29 sys_stv
2017-04-08 12:14 sys_stv
2017-04-08 12:06 sys_stv
2017-04-08 11:51 sys_stv
2017-04-08 11:27 sys_stv
2017-04-08 11:21 sys_stv
2017-04-08 10:55 sys_stv
2017-04-08 10:44 sys_stv
2017-04-08 10:29 sys_stv
2017-04-08 10:21 sys_stv
2017-04-08 9:57 sys_stv
2017-04-08 9:42 sys_stv
2017-04-08 9:25 sys_stv
2017-04-08 9:14 sys_stv
2017-04-08 8:59 sys_stv
2017-04-08 8:51 sys_stv
2017-04-08 8:25 sys_stv
2017-04-08 8:21 sys_stv
2017-04-08 7:59 sys_stv
2017-04-08 7:40 sys_stv
2017-04-08 7:36 sys_stv
2017-04-08 7:14 sys_stv
2017-04-08 7:06 sys_stv
2017-04-08 6:40 sys_stv
2017-04-08 6:25 sys_stv
2017-04-08 6:10 sys_stv
2017-04-08 5:55 sys_stv
2017-04-08 5:40 sys_stv
2017-04-08 5:31 sys_stv
2017-04-08 5:12 sys_stv
2017-04-08 4:59 sys_stv
2017-04-08 4:42 sys_stv
2017-04-08 4:29 sys_stv
2017-04-08 4:12 sys_stv
2017-04-08 4:06 sys_stv
2017-04-08 3:42 sys_stv
2017-04-08 3:31 sys_stv
2017-04-08 3:18 sys_stv
2017-04-08 2:59 sys_stv
2017-04-08 2:51 sys_stv
2017-04-08 2:27 sys_stv
2017-04-08 2:18 sys_stv
2017-04-08 1:59 sys_stv
2017-04-08 1:40 sys_stv
2017-04-08 1:25 sys_stv
2017-04-08 1:14 sys_stv
2017-04-08 0:57 sys_stv
2017-04-08 0:42 sys_stv
2017-04-08 0:25 sys_stv
2017-04-08 0:12 sys_stv
2017-04-07 23:59 sys_stv
2017-04-07 23:40 sys_stv
2017-04-07 23:25 sys_stv
2017-04-07 23:10 sys_stv
2017-04-07 22:59 sys_stv
2017-04-07 22:40 sys_stv
2017-04-07 22:33 sys_stv
2017-04-07 22:12 sys_stv
2017-04-07 21:57 sys_stv
2017-04-07 21:40 sys_stv
2017-04-07 21:31 sys_stv
2017-04-07 21:14 sys_stv
2017-04-07 21:01 sys_stv
2017-04-07 20:44 sys_stv
2017-04-07 20:25 sys_stv
2017-04-07 20:16 sys_stv
2017-04-07 20:01 sys_stv
2017-04-07 19:46 sys_stv
2017-04-07 19:29 sys_stv
2017-04-07 19:18 sys_stv
2017-04-07 19:03 sys_stv
2017-04-07 18:40 sys_stv
2017-04-07 18:25 sys_stv
2017-04-07 18:11 sys_stv
2017-04-07 17:59 sys_stv
2017-04-07 17:48 sys_stv
2017-04-07 17:27 sys_stv
2017-04-07 17:12 sys_stv
2017-04-07 16:57 sys_stv
2017-04-07 16:42 sys_stv
2017-04-07 16:25 sys_stv
2017-04-07 16:10 sys_stv
2017-04-07 16:06 sys_stv
2017-04-07 15:41 sys_stv
2017-04-07 15:27 sys_stv
2017-04-07 15:10 sys_stv
2017-04-07 14:57 sys_stv
2017-04-07 14:45 sys_stv
2017-04-07 14:25 sys_stv
2017-04-07 14:10 sys_stv
2017-04-07 14:06 sys_stv
2017-04-07 13:42 sys_stv
2017-04-07 13:27 sys_stv
2017-04-07 13:16 sys_stv
2017-04-07 12:59 sys_stv
2017-04-07 12:51 sys_stv
2017-04-07 12:27 sys_stv
2017-04-07 12:10 sys_stv
2017-04-07 12:03 sys_stv
2017-04-07 11:49 sys_stv
2017-04-07 11:25 sys_stv
2017-04-07 11:10 sys_stv
2017-04-07 11:01 sys_stv
2017-04-07 10:49 sys_stv
2017-04-07 10:29 sys_stv
2017-04-07 10:14 sys_stv
2017-04-07 9:55 sys_stv
2017-04-07 9:42 sys_stv
2017-04-07 9:29 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).