Aaron Conole <acon...@redhat.com> writes: > Ruifeng Wang <ruifeng.w...@arm.com> writes: > >> For environments (such as containers) where hugetlbfs are not available, >> some unit tests can be run with 'no-huge' option. >> >> fast-tests suites is generated dynamically according to hugetlbfs >> availability in building environment. This allows unit test to run >> in different environments using the same suite name. >> >> Several test cases are fixed to be able to run in no-huge mode. > > This looks great! Thanks, Ruifeng. > > I'm going to ack it once I see it run under the robot :)
Just looking through the robot's run, it seems that on the statically linked Arm64 build, the disk quota is getting exceeded. Do we need to request some more disk quota for this somehow? Is the build getting too large? >> v3: >> Use a single suite instead of create additional one for no-huge. (Aaron) >> Fix several test cases in no-huge mode. >> >> v2: >> Add a patch to enable running multiple suites in a job. (David) >> >> >> Ruifeng Wang (4): >> test: enable tests to run in no-huge mode >> ci: generate fast-tests suite base on hugepage availability >> ci: proceed with verification without hugepage >> ci: enable unit test for aarch64 >> >> .ci/linux-setup.sh | 11 +- >> .travis.yml | 5 +- >> app/test/meson.build | 216 ++++++++++++++++++--------------- >> app/test/test_acl.c | 22 ++-- >> app/test/test_hash.c | 7 +- >> app/test/test_table_pipeline.c | 12 +- >> 6 files changed, 152 insertions(+), 121 deletions(-)
