David Marchand <[email protected]> writes:

> On Mon, Mar 16, 2020 at 6:53 PM Aaron Conole <[email protected]> wrote:
>>
>> Bruce Richardson <[email protected]> writes:
>>
>> > Static builds can take a lot of space, so reduce the number of examples
>> > built when doing those static builds.
>> >
>> > Signed-off-by: Bruce Richardson <[email protected]>
>> > ---
>>
>> It looks good to me.  I'll try a run with Ruifeng's no-huge series and
>> see if I can trigger errors on my side (and then see what happens with
>> the cache sizes, too).  Might take some time as I adjust some things
>> here.
>
> - The disk quota issue was reproduced on master without Ruifeng patches:
> https://travis-ci.com/github/DPDK/dpdk/jobs/298584616
> https://travis-ci.com/github/DPDK/dpdk/jobs/298858638

Okay - guess I should just ack those patches, then.  They look good otherwise.

>
> And for this, the cache is not really big.
> cache-arm64-linux-bionic-a550182015679db90d1e0a2460464d106712e1c2c29f3efc7db1dc1b6fd86ebb--compiler-gcc.tgz
>    last modified: 2020-03-16 11:28:59  size: 160.84 MiB
> I remember bigger caches in the past.
>
> I deleted this job cache and restarted the first job, and it passed.
> Restarted again, and then it failed o_O.
>
>
> - So I went and restarted a couple of times both of those jobs
> (leaving the cache as is, which now contains 60MB of data).
> I get random failures.
> It does not seem to depend on the system: it failed once on
> [email protected], then
> worked later.

Seems it's all arm64 builds that are failing.  I went to file an issue,
but looks like you beat me to it :)

https://travis-ci.community/t/disk-quota-exceeded-on-arm64/7619

I'll help promote the issue however I can

> hostname: [email protected]: KO
> hostname: [email protected]: ok
> hostname: [email protected]: ok
> hostname: [email protected]: ok
> hostname: [email protected]: ok
>
> hostname: [email protected]: KO
> hostname: [email protected]: ok
> hostname: [email protected]: ok
> hostname: [email protected]: KO
> hostname: [email protected]: ok

Reply via email to