Ruifeng Wang <ruifeng.w...@arm.com> writes: >> -----Original Message----- >> From: David Marchand <david.march...@redhat.com> >> Sent: Friday, March 13, 2020 23:54 >> To: Aaron Conole <acon...@redhat.com> >> Cc: Ruifeng Wang <ruifeng.w...@arm.com>; Michael Santana >> <maicolgabr...@hotmail.com>; Bruce Richardson >> <bruce.richard...@intel.com>; Ananyev, Konstantin >> <konstantin.anan...@intel.com>; Cristian Dumitrescu >> <cristian.dumitre...@intel.com>; Wang, Yipeng1 >> <yipeng1.w...@intel.com>; Gobriel, Sameh <sameh.gobr...@intel.com>; >> dev <dev@dpdk.org>; Burakov, Anatoly <anatoly.bura...@intel.com>; >> Gavin Hu <gavin...@arm.com>; Honnappa Nagarahalli >> <honnappa.nagaraha...@arm.com>; juraj.lin...@pantheon.tech; nd >> <n...@arm.com> >> Subject: Re: [PATCH v3 0/4] no-huge unit test >> >> On Fri, Mar 13, 2020 at 2:04 PM Aaron Conole <acon...@redhat.com> wrote: >> > >> > 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? >> >> It seems to repeat. >> https://travis-ci.com/github/ovsrobot/dpdk/jobs/297840285#L2975 >> >> Do you know how much space we have in travis? >> Is the (c?)cache getting too big? > > Yes, it is probably caused by cache. > I hit the disk quota issue as well when running Travis against the latest > Master code. > After deleting caches, the issue was gone. Then Travis run with this > series of patches also got a pass. > > Hi Aaron, > Is is OK to clear cache of robot and re-run the build?
I can do this, but I am concerned that we will need to disable the cache to avoid this error on a consistent basis. > Thanks. > /Ruifeng > >> You can find out the per job cache size via the travis cli. >> >> >> -- >> David Marchand
