DPDK CI discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jeremy Plsek <jplsek@iol.unh.edu>
Cc: ci@dpdk.org
Subject: Re: [dpdk-ci] CI Test Cases
Date: Tue, 09 Apr 2019 18:44:40 +0200	[thread overview]
Message-ID: <3095021.C5hMUMoUle@xps> (raw)
In-Reply-To: <CA+xUZB67UM0b2kN=sSPAYBQMOuDisVWx8D7MSKjbP9FmUNE-tA@mail.gmail.com>

18/03/2019 16:55, Jeremy Plsek:
> This also gives the Community Lab a list of tests that can be
> implemented in the mean time.
> 
> https://docs.google.com/document/d/1WbRoIq0f5SmHM6D5sLbeh7hxRJdE2ppwB5JECHllLjg/edit?usp=sharing
> (This document is publicly editable. If I notice the document changes
> outside the scope of the goal, I'll try to revert it and give
> individual access instead.)

After the meeting of today, Ferruh, David and me have added more tests
to discuss next time:

	- Coverage gcov with unit tests
	- devtools/check-symbol-maps.sh
	- devtools/validate-abi.sh
	- Spell checks
	- clang-analyzer
	- cppcheck

And we have enumerated the items for the compilation tests:

Target CPU:
	Aarch64
	i686
	x86_32
	x86_64
	Power64
OS:
	FreeBSD 10.4
	FreeBSD 11
	FreeBSD 12.0
	Fedora 28
	Fedora 29
	CentOS 7.6
	Ubuntu 16.04
	Ubuntu 18.04
	Ubuntu 19.04
	Debian 9 stable
	Debian 10 testing
	OpenSuse 12-sp3
	OpenSuse 15
	Archlinux - latest Linux/gcc/clang
	Windows 10 (only meson+clang)
Make options (config in test-build.sh):
	examples (included in test-build.sh)
	HTML doc (included in test-build.sh)
	PDF doc - make doc-guides-pdf
	+shared
	+debug
	+ASSERT
	+LIBBSD
	+ARM64_MEMCPY
	+ARCH_STRICT_ALIGN
	+ALLOW_INV_SOCKET_ID
	+ALWAYS_PANIC_ON_ERROR
	+ENABLE_AVX512
	+PROFILE_WITH_VTUNE
	+TX_PREPARE_NOOP
	+USE_HPET
	+IBVERBS_LINK_DLOPEN
Meson options (config in meson_options.txt):
	examples (included in test-meson-builds.sh)
	enable_docs=true
	allow_invalid_socket_id=true
	use_hpet=true - should it be dropped?
	ibverbs_link=dlopen
	per_library_versions=false
Toolchain:
	Latest gcc
	Latest clang
Dependencies:
	make
	meson
	ninja
	doxygen
	sphinx
	latex
	inkscape
	libnuma
	libpcap
	libelf
	libarchive
	zlib
	libjansson
	openssl
	rdma-core
	musdk
	szedata2
	ipsec_mb
	libsso-snow3g
	libsso-kasumi
	libsso-zuc
	libqos
	isa-l
	libmnl
	libvirt




      parent reply	other threads:[~2019-04-09 16:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 15:55 Jeremy Plsek
2019-03-19  8:38 ` David Marchand
2019-04-09 16:44 ` Thomas Monjalon [this message]

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=3095021.C5hMUMoUle@xps \
    --to=thomas@monjalon.net \
    --cc=ci@dpdk.org \
    --cc=jplsek@iol.unh.edu \
    /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).