DPDK patches and discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [RFC 0/3] ci: enable unit tests for non-aarch64 platforms
Date: Fri, 29 Mar 2019 13:22:38 -0400	[thread overview]
Message-ID: <20190329172241.11916-1-aconole@redhat.com> (raw)

This series is submitted as an RFC because a number of the unit tests are
not successful in the travis environment.  If all of them were passing,
this would be submitted as PATCH instead.  It could be accepted as-is but I
would prefer to see all the tests passing first.

The first patch fixes up the tests to auto-detect the number of cores on
a machine.  This helps on lower-end systems (such as i3 laptops or something)
where someone wants to verify the functionality.  The number of available
cores on the running system will be picked based on the running system
parameters.

The second patch moves some tests out - these tests don't produce output or
complete in any reasonable amount of time (10m+ for a single unit test is
a little strange - they should be investigated to see if the run time can
be reduced).  I prefer to see these separated out since travis will completely
bail if the test takes longer than 10m to produce output.

The third actually enables the testing, and runs each test leg independently.
This version populates the hugepages mapping.  However, it might be useful
to have the option of running without hugepages enabled (and I have a
separate series that can do this).  However, the --no-huge flag seems to cause
most of the unit tests to break since they either spawn a new instance of
the EAL without passing the hugepage flags, or check against the hugepage API
and use that to determine whether memory can be allocated.

Aaron Conole (3):
  test/meson: auto detect number of cores
  meson-tests: separate slower tests
  ci: enable tests on non-arm platforms

 .ci/linux-build.sh   |  7 +++++++
 .ci/linux-setup.sh   |  6 +++++-
 app/test/meson.build | 43 +++++++++++++++++++++++++++++++++----------
 3 files changed, 45 insertions(+), 11 deletions(-)

-- 
2.19.1

             reply	other threads:[~2019-03-29 17:22 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 17:22 Aaron Conole [this message]
2019-03-29 17:22 ` Aaron Conole
2019-03-29 17:22 ` [dpdk-dev] [RFC 1/3] test/meson: auto detect number of cores Aaron Conole
2019-03-29 17:22   ` Aaron Conole
2019-04-01 13:48   ` David Marchand
2019-04-01 13:48     ` David Marchand
2019-04-01 14:07     ` Aaron Conole
2019-04-01 14:07       ` Aaron Conole
2019-04-01 16:23   ` Pattan, Reshma
2019-04-01 16:23     ` Pattan, Reshma
2019-04-01 17:48     ` Aaron Conole
2019-04-01 17:48       ` Aaron Conole
2019-04-01 19:39       ` Thomas Monjalon
2019-04-01 19:39         ` Thomas Monjalon
2019-04-01 19:58         ` Aaron Conole
2019-04-01 19:58           ` Aaron Conole
2019-03-29 17:22 ` [dpdk-dev] [RFC 2/3] meson-tests: separate slower tests Aaron Conole
2019-03-29 17:22   ` Aaron Conole
2019-03-29 17:22 ` [dpdk-dev] [RFC 3/3] ci: enable tests on non-arm platforms Aaron Conole
2019-03-29 17:22   ` Aaron Conole
2019-04-17  8:32   ` Jerin Jacob Kollanukkaran
2019-04-17  8:32     ` Jerin Jacob Kollanukkaran
2019-04-17 12:39     ` Aaron Conole
2019-04-17 12:39       ` Aaron Conole
2019-04-17 15:32       ` [dpdk-dev] [EXT] " Jerin Jacob Kollanukkaran
2019-04-17 15:32         ` Jerin Jacob Kollanukkaran
2019-04-01 19:15 ` [dpdk-dev] [RFC 0/3] ci: enable unit tests for non-aarch64 platforms David Marchand
2019-04-01 19:15   ` David Marchand
2019-04-01 19:28   ` Aaron Conole
2019-04-01 19:28     ` Aaron Conole
2019-04-01 19:29     ` David Marchand
2019-04-01 19:29       ` David Marchand
2019-04-02  9:37       ` Bruce Richardson
2019-04-02  9:37         ` Bruce Richardson
2019-04-02 10:09         ` David Marchand
2019-04-02 10:09           ` David Marchand
2019-04-02 12:49           ` Aaron Conole
2019-04-02 12:49             ` Aaron Conole

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=20190329172241.11916-1-aconole@redhat.com \
    --to=aconole@redhat.com \
    --cc=dev@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).