From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw65350[v2, 3/4] build: test meson installation
Date: 17 Feb 2020 12:05:19 -0800 [thread overview]
Message-ID: <ee68f5$9c8srt@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/65350
_apply issues_
Submitter: David Marchand <david.marchand@redhat.com>
Date: 2020-01-29 17:26:20
Reply_mail: 20200129172621.28565-4-david.marchand@redhat.com
DPDK git baseline:
Repo:dpdk-next-net, CommitID: b4f0d798756da08d1a061b26bd8fffbcd5968ea8
Repo:dpdk, CommitID: bc3282125b72ccfe8641f0826955a384f40ca775
*Repo: dpdk-next-net
devtools/test-null.sh
fi
if [ "$RUN_TESTS" = "1" ]; then
error: patch failed: .ci/linux-build.sh:29
error: .ci/linux-build.sh: patch does not apply
Checking patch devtools/test-meson-builds.sh...
error: while searching for:
shift
builddir=$1
--
options="--werror -Dexamples=all"
for option in $DPDK_MESON_OPTIONS ; do
options="$options -D$option"
done
error: patch failed: devtools/test-meson-builds.sh:63
error: devtools/test-meson-builds.sh: patch does not apply
Checking patch devtools/test-null.sh...
*Repo: dpdk
devtools/test-null.sh
fi
if [ "$RUN_TESTS" = "1" ]; then
error: patch failed: .ci/linux-build.sh:29
error: .ci/linux-build.sh: patch does not apply
Checking patch devtools/test-meson-builds.sh...
error: while searching for:
shift
builddir=$1
--
options="--werror -Dexamples=all"
for option in $DPDK_MESON_OPTIONS ; do
options="$options -D$option"
done
error: patch failed: devtools/test-meson-builds.sh:63
error: devtools/test-meson-builds.sh: patch does not apply
Checking patch devtools/test-null.sh...
DPDK STV team
reply other threads:[~2020-02-17 20:05 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$9c8srt@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).