A raspi test that determines it needs to be skipped exits with exit code
125. Handle that exit code gracefully so that such a skipped test passes
with GOOD rather than fails with ERROR.
This switches the execution of the overlayfs smoke test to use that set
of tests. The original `ubuntu_overlayfs_smoke_test.sh` test was moved
to the same repo to preserve the test coverage.
Signed-off-by: Francis Ginther <email address hidden>
Acked-by: Sean Feole <email address hidden>
Acked-by: Po-Hsu Lin <email address hidden>
The time we need for the ftrace-direct.tc test is depend on the number
of CPUs on a SUT. Test shows it will take about 46 minutes to run on a
system with 224 CPUs, give it 60 minutes to run.
Improve the ftracetest granularity by running sub-tests one-by-one.
With this patch, we will be able to hint specific known failures
without letting other regressions to slip through.
Test case listing is achieved by porting the find_testcases() code
in ftracetest script from tools/testing/selftests/ftrace of a kernel
tree. Test verbosity increased by using -vvv flag, this will increase
report file size but it will be easier for debugging.
As we're not running the whole test altogether, the timeout threshold
has been modified to 10 minutes for each case on non-riscv64 systems.
For riscv64 the timeout will need to be disabled due to the autotest
timeout on it is incorrect (LP: #1940080)
I have also removed some leftovers when we copy this test from
ubuntu_kernel_selftests.
Signed-off-by: Po-Hsu Lin <email address hidden>
Acked-by: Francis Ginther <email address hidden>
Acked-by: Sean Feole <email address hidden>
Signed-off-by: Po-Hsu Lin <email address hidden>
UBUNTU: SAUCE: ubuntu_xfstests_*: use loop device for the test
Use loop device for the test, courtesy to Francis who add this code
on AWS cloud first. This patch was ported from there and rebased
on the xfstest build fix (LP: #2008049), and use /dev/loop0 for
finding which free loop device to use.
By doing so we can avoid destroying data in /dev/sdb accidentally.
Also it can reduce the hardware limit of this test, it will no
longer require a scratch drive to run but just 20G free disk space
as suggested in XFSTests doc.
cpuset_hotplug will hang on X-aws-4.4 VMs (those with CPU <=2). This
issue can be reproduced all the way back to X-aws-1128, with current
and previous LTP fork.
When this happens, it will cause failure to cpuset_memory as well and
eventually leads to an incomplete test report. Let's fail this test
directly on this kernel to get the test going.
This issue didn't emerge until we begin to run ubuntu_ltp_controllers on
Xenial in recent cycle.
Signed-off-by: Po-Hsu Lin <email address hidden>
Acked-by: Cory Todd <email address hidden>
Acked-by: Francis Ginther <email address hidden>
Acked-by: Sean Feole <email address hidden>
Signed-off-by: Po-Hsu Lin <email address hidden>
UBUNTU: SAUCE: ubuntu_performance_gpudirect_rdma: porting peer memory test
This commit introduce a peer memory test running on specific machines
with loopback infinite bands. The info of those machines enlisted in
hosts.d. The loopback setup is a must for running this test job.
Expanding host.d is able to support more machines.
The job is expected to run on Jammy with linux-nvidia kernel and above.
The original version of this test job is mainly implemented by
dann frazier <email address hidden> .
Signed-off-by: Taihsiang Ho (tai271828) <email address hidden>
Acked-by: Po-Hsu Lin <email address hidden>
Signed-off-by: Po-Hsu Lin <email address hidden>
UBUNTU: SAUCE: ubuntu_performance_gpudirect_rdma: create GPUDirect test cases
The goal of this test is to exercise the performance test of nvidia GPUDirect
technology. This commit introduces the entrypoint of the whole testing
framework. The implementation of the corresponding test jobs will be
introduced in the following commits.
Signed-off-by: Taihsiang Ho (tai271828) <email address hidden>
Acked-by: Po-Hsu Lin <email address hidden>
Signed-off-by: Po-Hsu Lin <email address hidden>