| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Since we don't build for s390x make it clear in the test deps.
Otherwise it will be tried and fails to resolve there.
Change-Id: Ib0d27ee0955f25565cf78d66db9a80622db10b18
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
|
|
This test part of the test was arch specific e.g. not xen is
not build on ppc64el.
Change-Id: I71bed3a353c34b2785791406200eaf9bb275db2a
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
|
|
This dependency was arch specific so the test failed on e.g. ppc64el
Change-Id: I162bc77288aae3be56e1840764914d1264786b98
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
|
|
For now the autotest is too unreliable, so we run it to get some
logs in different environments, but never (want to ) fail until
it is stable.
This was already the intention and worked if certain tests failed
as we didn't check on the RC of the tests, but if the test overall
fatally fails we had a FAIL due to the set -e.
Change-Id: I54052351113a974d3e7810d55405f063e1fbe16a
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
|
|
The autotests we bundle can be used on machines able to run DPDK.
But sadly almost none of them can run inside most common build
environments which makes it unavailable for a classic "dh_autotest".
But we can define certain characteristics of an dep8 test.
In there at least the majority of the tests runs fine.
So this adds the autotests as dep8 test.
To do so it defines the test as "isolation-machine, needs-root", but
even then checks further required capabilities like sse3 and the
required huge pages.
If prereqs are not met it exits by skipping the test, which counts as
PASS.
The tests can run successful e.g. with an autopkgtest call that adds the
required CPU characteristics. To do so run it like usual but with:
autopkgtest [...] -- qemu --qemu-options='-cpu qemu64,+ssse3' [...]
So far only amd64 is supported and as mentioned before only if the
prereqs are met. But it is written in a way that this can be the groundwork
for any other architecture that wants to enable the autotests as well.
Change-Id: Ia2a2839ce349b3ea5c22f0b8a589f8a71378adc1
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
|
|
In case the test is failing this allows to debug the case as the adt
artifacts will include the dkms build logs.
Change-Id: I26a68199428b28332adea2a83da23a647f7756da
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
|
|
Since we already had the code from 1G pages to not fail if not supported
this was just adding about the same.
But for a 16M supporting environment we expect is to be able to get
2x16M hugepages, so as with 2M pages we test for mountpoints and the
actual alloc to be correct.
Change-Id: I0b4e106f11eaebfe068dbb20130add5840e98368
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
|
|
Tests are now functional on ppc64el as well, enable them in the guarding
script and d/t/control.
Change-Id: I0b92ccee43cab66fdb5bbb05b79902344a899746
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
|
|
Due to recent upgrades some commands of the reset function can fail
if the service wasn't loaded before.
But in that case no reset has to be done, so make it non fatal by adding
a ||/bin/true
Change-Id: I1da6bf315eefc9a4348c8dbae09d534a8fab9355
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
|
|
As discussed this shall be our initial baseline.
If history is needed for any sort of debugging or analysis it can be
found at https://code.launchpad.net/~ubuntu-server/dpdk/+git/dpdk
Change-Id: Ie95c7effbbea34d723df14f6451c1f782000cbc1
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
|
Dimitri John Ledkov
Christian Ehrhardt