automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xinfengx.zhao@intel.com, zhaoyan.chen@intel.com, peipeix.lu@intel.com
Subject: [dpdk-test-report]  |FAILURE| pw38895[dpdk-dev, 18.05-RC2, 4/4] eal: move all runtime data into DPDK runtime dir
Date: 25 Apr 2018 05:32:20 -0700	[thread overview]
Message-ID: <0590c7$1gb4um@orsmga001.jf.intel.com> (raw)

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

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

_apply issues_

Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: 2018-04-25 12:24:37
DPDK git baseline:
	Repo:dpdk-master, CommitID: 4754ceaa09f4b77facde941a9a35414d0cd732bb
	Repo:dpdk-next-eventdev, CommitID: fe5abd3150bc1caa8369e743c395c39f53265597
	Repo:dpdk-next-net, CommitID: 7789dc16eff2da27ea50a6e569969db85cdbf8dc
	Repo:dpdk-next-crypto, CommitID: eb8a86e275ef15a5455948d679d1a2c43dd4c740
	Repo:dpdk-next-virtio, CommitID: 81daf0ba4f2eb20c00975b474cb9b6ab71c44e25

*Repo: dpdk-master
Checking patch lib/librte_eal/bsdapp/eal/eal.c...
Checking patch lib/librte_eal/common/eal_filesystem.h...
error: while searching for:
#ifndef EAL_FILESYSTEM_H
#define EAL_FILESYSTEM_H

/** Path of rte config file. */
#define RUNTIME_CONFIG_FMT "%s/.%s_config"
--

#include <stdint.h>
#include <limits.h>
#include <unistd.h>

error: patch failed: lib/librte_eal/common/eal_filesystem.h:11
error: lib/librte_eal/common/eal_filesystem.h: patch does not apply
Checking patch lib/librte_eal/linuxapp/eal/eal.c...
*Repo: dpdk-next-eventdev
Checking patch lib/librte_eal/bsdapp/eal/eal.c...
Hunk #1 succeeded at 86 (offset -1 lines).
Checking patch lib/librte_eal/common/eal_filesystem.h...
error: while searching for:
}

/** String format for hugepage map lock files. */
#define HUGEFILE_LOCK_FMT "%s/.%smap_%d.lock"

--
			internal_config.hugefile_prefix, f_id);
	buffer[buflen - 1] = '\0';
	return buffer;
}

error: patch failed: lib/librte_eal/common/eal_filesystem.h:122
error: lib/librte_eal/common/eal_filesystem.h: patch does not apply
Checking patch lib/librte_eal/linuxapp/eal/eal.c...
*Repo: dpdk-next-net
Checking patch lib/librte_eal/bsdapp/eal/eal.c...
Checking patch lib/librte_eal/common/eal_filesystem.h...
error: while searching for:
#ifndef EAL_FILESYSTEM_H
#define EAL_FILESYSTEM_H

/** Path of rte config file. */
#define RUNTIME_CONFIG_FMT "%s/.%s_config"
--

#include <stdint.h>
#include <limits.h>
#include <unistd.h>

error: patch failed: lib/librte_eal/common/eal_filesystem.h:11
error: lib/librte_eal/common/eal_filesystem.h: patch does not apply
Checking patch lib/librte_eal/linuxapp/eal/eal.c...
*Repo: dpdk-next-crypto
Checking patch lib/librte_eal/bsdapp/eal/eal.c...
Checking patch lib/librte_eal/common/eal_filesystem.h...
error: while searching for:
#ifndef EAL_FILESYSTEM_H
#define EAL_FILESYSTEM_H

/** Path of rte config file. */
#define RUNTIME_CONFIG_FMT "%s/.%s_config"
--

#include <stdint.h>
#include <limits.h>
#include <unistd.h>

error: patch failed: lib/librte_eal/common/eal_filesystem.h:11
error: lib/librte_eal/common/eal_filesystem.h: patch does not apply
Checking patch lib/librte_eal/linuxapp/eal/eal.c...
*Repo: dpdk-next-virtio
Checking patch lib/librte_eal/bsdapp/eal/eal.c...
Checking patch lib/librte_eal/common/eal_filesystem.h...
error: while searching for:
}

/** String format for hugepage map lock files. */
#define HUGEFILE_LOCK_FMT "%s/.%smap_%d.lock"

--
			internal_config.hugefile_prefix, f_id);
	buffer[buflen - 1] = '\0';
	return buffer;
}

error: patch failed: lib/librte_eal/common/eal_filesystem.h:122
error: lib/librte_eal/common/eal_filesystem.h: patch does not apply
Checking patch lib/librte_eal/linuxapp/eal/eal.c...

DPDK STV team

                 reply	other threads:[~2018-04-25 12:32 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='0590c7$1gb4um@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=peipeix.lu@intel.com \
    --cc=test-report@dpdk.org \
    --cc=xinfengx.zhao@intel.com \
    --cc=zhaoyan.chen@intel.com \
    /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).