automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: harry.van.haaren@intel.com
Subject: [dpdk-test-report] |FAILURE| pw37296 [PATCH] eal/service: remove experimental tags
Date: 17 Apr 2018 05:09:35 -0700	[thread overview]
Message-ID: <a7de25$14942l@fmsmga002.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Harry van Haaren <harry.van.haaren@intel.com>
Date: Thu,  5 Apr 2018 14:15:46 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:fe5abd3150bc1caa8369e743c395c39f53265597
                   Repo:dpdk-next-crypto, Branch:master, CommitID:25b13dcbd5a779548d1a67f60684cabf532a17f8
                   Repo:dpdk-next-net, Branch:master, CommitID:b4b25ce3282cd32c1e5b194adc72cafc0e0a88b2
                   Repo:dpdk-next-virtio, Branch:master, CommitID:8adbe7e4847060d091c46abcbecd3dfea8362b7a
                   Repo:dpdk, Branch:master, CommitID:b4ca812986131b5ca90e558b2066f6e904aa08ea
                   
Apply patch file failed:
Repo: dpdk
37296:
patching file MAINTAINERS
Hunk #1 succeeded at 188 (offset 32 lines).
patching file doc/guides/rel_notes/release_18_05.rst
Hunk #1 succeeded at 115 with fuzz 2 (offset 43 lines).
patching file examples/service_cores/Makefile
patching file examples/service_cores/meson.build
patching file lib/librte_eal/common/include/rte_service.h
patching file lib/librte_eal/common/include/rte_service_component.h
patching file lib/librte_eal/common/rte_service.c
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 211.
Hunk #2 succeeded at 286 with fuzz 1 (offset 30 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej

Repo: dpdk-next-crypto
37296:
patching file MAINTAINERS
Hunk #1 succeeded at 188 (offset 32 lines).
patching file doc/guides/rel_notes/release_18_05.rst
Hunk #1 succeeded at 127 with fuzz 2 (offset 55 lines).
patching file examples/service_cores/Makefile
patching file examples/service_cores/meson.build
patching file lib/librte_eal/common/include/rte_service.h
patching file lib/librte_eal/common/include/rte_service_component.h
patching file lib/librte_eal/common/rte_service.c
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 211.
Hunk #2 succeeded at 286 with fuzz 1 (offset 30 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej

Repo: dpdk-next-net
37296:
patching file MAINTAINERS
Hunk #1 succeeded at 188 (offset 32 lines).
patching file doc/guides/rel_notes/release_18_05.rst
Hunk #1 succeeded at 124 with fuzz 2 (offset 52 lines).
patching file examples/service_cores/Makefile
patching file examples/service_cores/meson.build
patching file lib/librte_eal/common/include/rte_service.h
patching file lib/librte_eal/common/include/rte_service_component.h
patching file lib/librte_eal/common/rte_service.c
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 211.
Hunk #2 succeeded at 286 with fuzz 1 (offset 30 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej

Repo: dpdk-next-virtio
37296:
patching file MAINTAINERS
Hunk #1 succeeded at 188 (offset 32 lines).
patching file doc/guides/rel_notes/release_18_05.rst
Hunk #1 succeeded at 82 with fuzz 2 (offset 10 lines).
patching file examples/service_cores/Makefile
patching file examples/service_cores/meson.build
patching file lib/librte_eal/common/include/rte_service.h
patching file lib/librte_eal/common/include/rte_service_component.h
patching file lib/librte_eal/common/rte_service.c
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 211.
Hunk #2 succeeded at 282 with fuzz 1 (offset 26 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej

Repo: dpdk-next-eventdev
37296:
patching file MAINTAINERS
Hunk #1 succeeded at 188 (offset 32 lines).
patching file doc/guides/rel_notes/release_18_05.rst
Hunk #1 succeeded at 77 with fuzz 2 (offset 5 lines).
patching file examples/service_cores/Makefile
patching file examples/service_cores/meson.build
patching file lib/librte_eal/common/include/rte_service.h
patching file lib/librte_eal/common/include/rte_service_component.h
patching file lib/librte_eal/common/rte_service.c
patching file lib/librte_eal/rte_eal_version.map
Hunk #1 FAILED at 211.
Hunk #2 succeeded at 286 with fuzz 1 (offset 30 lines).
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/rte_eal_version.map.rej


DPDK STV team

                 reply	other threads:[~2018-04-17 12:09 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='a7de25$14942l@fmsmga002.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=harry.van.haaren@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).