automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: bruce.richardson@intel.com
Subject: [dpdk-test-report] |FAILURE| pw32556 [PATCH 2/2] test/test: add return value to mark unit tests as skipped
Date: 09 Jan 2018 17:15:38 -0800	[thread overview]
Message-ID: <b11803$8e9id@fmsmga002.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Thu, 21 Dec 2017 10:15:10 +0000
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:36d020c107ba65a584784a3f52484ea1698d4f9d
                   Repo:dpdk-next-crypto, Branch:master, CommitID:5df818d05d9586d8c00be2bb0a4b38b0b6410f50
                   Repo:dpdk-next-net, Branch:master, CommitID:d54afeb1a9810d5bdf0d69e572682fd3686667f7
                   Repo:dpdk-next-virtio, Branch:master, CommitID:e9e957b8725bffb3d2ffb18467ffab91e3f2fa2e
                   Repo:dpdk, Branch:master, CommitID:f06125c07d6203a84e9b242c62d6a8e532a5c51d
                   
Apply patch file failed:
Repo: dpdk
32556:
patching file test/test/test.c
Hunk #1 FAILED at 152.
1 out of 1 hunk FAILED -- saving rejects to file test/test/test.c.rej
patching file test/test/test.h
Hunk #1 succeeded at 11 (offset -29 lines).
patching file test/test/test_cryptodev.c
Hunk #1 succeeded at 9563 (offset -28 lines).
Hunk #2 succeeded at 9579 (offset -28 lines).
Hunk #3 succeeded at 9595 (offset -28 lines).
Hunk #4 succeeded at 9611 (offset -28 lines).
Hunk #5 succeeded at 9627 (offset -28 lines).
Hunk #6 succeeded at 9643 (offset -28 lines).
Hunk #7 succeeded at 9659 (offset -28 lines).
Hunk #8 succeeded at 9675 (offset -28 lines).
Hunk #9 succeeded at 9691 (offset -28 lines).
Hunk #10 succeeded at 9707 (offset -28 lines).
Hunk #11 succeeded at 9725 (offset -28 lines).
Hunk #12 succeeded at 9751 (offset -28 lines).
Hunk #13 succeeded at 9767 (offset -28 lines).

Repo: dpdk-next-crypto
32556:
patching file test/test/test.c
Hunk #1 FAILED at 152.
1 out of 1 hunk FAILED -- saving rejects to file test/test/test.c.rej
patching file test/test/test.h
Hunk #1 succeeded at 11 (offset -29 lines).
patching file test/test/test_cryptodev.c
Hunk #1 succeeded at 9577 (offset -14 lines).
Hunk #2 succeeded at 9593 (offset -14 lines).
Hunk #3 succeeded at 9609 (offset -14 lines).
Hunk #4 succeeded at 9625 (offset -14 lines).
Hunk #5 succeeded at 9641 (offset -14 lines).
Hunk #6 succeeded at 9657 (offset -14 lines).
Hunk #7 succeeded at 9673 (offset -14 lines).
Hunk #8 succeeded at 9689 (offset -14 lines).
Hunk #9 succeeded at 9705 (offset -14 lines).
Hunk #10 succeeded at 9721 (offset -14 lines).
Hunk #11 succeeded at 9739 (offset -14 lines).
Hunk #12 succeeded at 9765 (offset -14 lines).
Hunk #13 succeeded at 9781 (offset -14 lines).

Repo: dpdk-next-net
32556:
patching file test/test/test.c
Hunk #1 FAILED at 152.
1 out of 1 hunk FAILED -- saving rejects to file test/test/test.c.rej
patching file test/test/test.h
Hunk #1 succeeded at 11 (offset -29 lines).
patching file test/test/test_cryptodev.c
Hunk #1 succeeded at 9563 (offset -28 lines).
Hunk #2 succeeded at 9579 (offset -28 lines).
Hunk #3 succeeded at 9595 (offset -28 lines).
Hunk #4 succeeded at 9611 (offset -28 lines).
Hunk #5 succeeded at 9627 (offset -28 lines).
Hunk #6 succeeded at 9643 (offset -28 lines).
Hunk #7 succeeded at 9659 (offset -28 lines).
Hunk #8 succeeded at 9675 (offset -28 lines).
Hunk #9 succeeded at 9691 (offset -28 lines).
Hunk #10 succeeded at 9707 (offset -28 lines).
Hunk #11 succeeded at 9725 (offset -28 lines).
Hunk #12 succeeded at 9751 (offset -28 lines).
Hunk #13 succeeded at 9767 (offset -28 lines).

Repo: dpdk-next-virtio
32556:
patching file test/test/test.c
Hunk #1 FAILED at 152.
1 out of 1 hunk FAILED -- saving rejects to file test/test/test.c.rej
patching file test/test/test.h
patching file test/test/test_cryptodev.c

Repo: dpdk-next-eventdev
32556:
patching file test/test/test.c
Hunk #1 FAILED at 152.
1 out of 1 hunk FAILED -- saving rejects to file test/test/test.c.rej
patching file test/test/test.h
patching file test/test/test_cryptodev.c


DPDK STV team

                 reply	other threads:[~2018-01-10  1:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='b11803$8e9id@fmsmga002.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=test-report@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).