> -----Original Message----- > From: Thomas Monjalon <[email protected]> > Sent: Thursday, April 16, 2020 10:40 PM > To: Aaron Conole <[email protected]> > Cc: David Marchand <[email protected]>; dev <[email protected]>; > Ruifeng Wang <[email protected]>; Gavin Hu <[email protected]>; > Honnappa Nagarahalli <[email protected]>; Michael Santana > <[email protected]> > Subject: Re: [PATCH] ci: remove aarch64 from Travis jobs > > 16/04/2020 15:45, Aaron Conole: > > David Marchand <[email protected]> writes: > > > On Thu, Apr 16, 2020 at 2:44 PM Aaron Conole <[email protected]> > wrote: > > >> Thomas Monjalon <[email protected]> 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 <[email protected]> > > >> > --- > > >> > > >> 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. Thanks. /Ruifeng > >
