17/04/2020 10:49, Ruifeng Wang: > From: Thomas Monjalon <tho...@monjalon.net> > > 16/04/2020 15:45, Aaron Conole: > > > David Marchand <david.march...@redhat.com> writes: > > > > On Thu, Apr 16, 2020 at 2:44 PM Aaron Conole <acon...@redhat.com> > > wrote: > > > >> Thomas Monjalon <tho...@monjalon.net> writes: > > > >> > > > >> > Travis is not reliable for native Arm and PPC: > > > >> > https://travis-ci.community/t/disk-quota-exceeded-on-arm64/7619/6 > > > >> > > > > >> > In order to get reliable Travis reports, the use of Arm machines > > > >> > is removed until Travis fixes it. > > > >> > > > > >> > Signed-off-by: Thomas Monjalon <tho...@monjalon.net> > > > >> > --- > > > >> > > > >> We should add back the cross-build if we do this - at least then we > > > >> could have a reliable compilation test of Arm64 code. Does it make > > > >> sense? > > > > > > > > I don't see them removed by this patch, the two jobs are still present ? > > > > > > Whoops - for some reason I missed them. Nevermind :) > > > > So? Acked? > > > Can we achieve this by allowing failures on AArch64 jobs? > https://docs.travis-ci.com/user/build-matrix/#rows-that-are-allowed-to-fail > > Add following setting: > jobs: > allow_failures: > - arch: arm64 > > So we can keep the jobs while not suffering from unstable infrastructure. > Results of these jobs will still observable. This gives us a chance to know > when jobs are stable.
I don't see the benefit. It will just make Travis reports unclear. I wait at least one more week to give Travis a chance to fix Arm support. Please work with them. If no result shortly, I will apply this patch to improve DPDK CI reliability.
