From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Fam Zheng" <fam@euphon.net>, "Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH v2] travis-ci: Disable C++ on Aarch64 container
Date: Mon, 8 Feb 2021 15:41:26 +0000 [thread overview]
Message-ID: <20210208154126.GL1141037@redhat.com> (raw)
In-Reply-To: <4304f273-2320-e302-f8ca-b72fb69061b5@amsat.org>
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 :|
prev parent reply other threads:[~2021-02-08 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 20:05 [PATCH v2] travis-ci: Disable C++ on Aarch64 container Philippe Mathieu-Daudé
2021-02-08 5:54 ` Thomas Huth
2021-02-08 9:16 ` Philippe Mathieu-Daudé
2021-02-08 10:09 ` Thomas Huth
2021-02-08 10:20 ` Philippe Mathieu-Daudé
2021-02-08 15:41 ` Daniel P. Berrangé [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210208154126.GL1141037@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).