automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw63977[1/2] ci: add travis ci support for aarch64
Date: 20 Jan 2020 15:36:54 -0800	[thread overview]
Message-ID: <ee68f5$94q1bj@orsmga001.jf.intel.com> (raw)

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

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

_apply issues_

Submitter: Ruifeng Wang <ruifeng.wang@arm.com>
Date: 2019-12-18 05:39:01
Reply_mail: 20191218053902.193417-2-ruifeng.wang@arm.com
DPDK git baseline:
	Repo:dpdk-next-net, CommitID: 2c723f69b97766fb77923171ce155a5b251fd278
	Repo:dpdk, CommitID: a4feffcfe1604e967a70012078eb80f90463da2e

*Repo: dpdk-next-net
# setup hugepages
cat /proc/meminfo
sudo sh -c 'echo 1024 > /proc/sys/vm/nr_hugepages'
cat /proc/meminfo

error: patch failed: .ci/linux-setup.sh:3
error: .ci/linux-setup.sh: patch does not apply
Checking patch .travis.yml...
error: while searching for:
      apt:
        packages:
          - *extra_packages


script: ./.ci/${TRAVIS_OS_NAME}-build.sh

error: patch failed: .travis.yml:115
error: .travis.yml: patch does not apply
*Repo: dpdk
# setup hugepages
cat /proc/meminfo
sudo sh -c 'echo 1024 > /proc/sys/vm/nr_hugepages'
cat /proc/meminfo

error: patch failed: .ci/linux-setup.sh:3
error: .ci/linux-setup.sh: patch does not apply
Checking patch .travis.yml...
error: while searching for:
      apt:
        packages:
          - *extra_packages


script: ./.ci/${TRAVIS_OS_NAME}-build.sh

error: patch failed: .travis.yml:115
error: .travis.yml: patch does not apply

DPDK STV team

             reply	other threads:[~2020-01-20 23:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20 23:36 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-12-18  6:20 sys_stv

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$94q1bj@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).