On Mon, Feb 08, 2021 at 10:16:19AM +0100, Philippe Mathieu-Daudé wrote: > Hi Thomas, > > On 2/8/21 6:54 AM, Thomas Huth wrote: > > On 06/02/2021 21.05, Philippe Mathieu-Daudé wrote: > >> Travis-CI seems to have enforced memory limit on containers, > >> and the 'GCC check-tcg' job started to fail [*]: > >> > >> [2041/3679] Compiling C++ object libcommon.fa.p/disas_nanomips.cpp.o > >> FAILED: libcommon.fa.p/disas_nanomips.cpp.o > >> {standard input}: Assembler messages: > >> {standard input}:577781: Warning: end of file not at end of a line; > >> newline inserted > >> {standard input}:577882: Error: unknown pseudo-op: `.lvl35769' > >> {standard input}: Error: open CFI at the end of file; missing > >> .cfi_endproc directive > >> c++: fatal error: Killed signal terminated program cc1plus > >> compilation terminated. > > > > If disabling C++ "fixes" the issue, ok ... > > Otherwise, we should maybe rather limit the amount of parallel jobs > > there instead? (i.e. compiling with "make -j1" in the worst case?) > > I exhausted my Travis-CI credits (frankly I don't plan to pay for it > with my own money). If the project expects developers to use Travis-CI, > we should think at some way to buy credits and give them to developers > on demand? [Cc'ing Stefan]
We should just stop wasting our time here. Simply delete the travis config right now and worry about adding more coverage to gitlab separately. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|