automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report]  |FAILURE| pw56144[v3, 3/3] test/mcslock: add mcs queued lock unit test
Date: 07 Jul 2019 20:54:56 -0700	[thread overview]
Message-ID: <ee68f5$7d5d28@orsmga001.jf.intel.com> (raw)

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

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

_apply issues_

Submitter: Phil Yang <phil.yang@arm.com>
Date: 2019-07-05 10:27:08
Reply_mail: 1562322429-18635-4-git-send-email-phil.yang@arm.com
DPDK git baseline:
	Repo:dpdk, CommitID: 7ddd2e81697bfc04eafac35082c4e3271721a780

*Repo: dpdk

F: lib/librte_eal/common/include/generic/rte_mcslock.h

ARM v7
M: Jan Viktorin <viktorin@rehivetech.com>

error: patch failed: MAINTAINERS:237
error: MAINTAINERS: patch does not apply
Checking patch app/test/Makefile...
error: while searching for:
SRCS-y += test_barrier.c
SRCS-y += test_malloc.c
SRCS-y += test_cycles.c
SRCS-y += test_spinlock.c
SRCS-y += test_ticketlock.c
SRCS-y += test_memory.c

error: patch failed: app/test/Makefile:64
error: app/test/Makefile: patch does not apply
Checking patch app/test/autotest_data.py...
Hunk #1 succeeded at 183 (offset 6 lines).
Checking patch app/test/autotest_test_funcs.py...
error: while searching for:
--


def logs_autotest(child, test_name):
    child.sendline(test_name)

error: patch failed: app/test/autotest_test_funcs.py:164
error: app/test/autotest_test_funcs.py: patch does not apply
Checking patch app/test/meson.build...
error: while searching for:
	'test_memzone.c',
	'test_meter.c',
	'test_metrics.c',
	'test_mp_secondary.c',
	'test_pdump.c',
	'test_per_lcore.c',

error: patch failed: app/test/meson.build:80
error: app/test/meson.build: patch does not apply
Checking patch app/test/test_mcslock.c...
error: app/test/test_mcslock.c: already exists in working directory

DPDK STV team

                 reply	other threads:[~2019-07-08  3:55 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='ee68f5$7d5d28@orsmga001.jf.intel.com' \
    --to=sys_stv@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).