qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"Bastian Koppelmann" <kbastian@mail.uni-paderborn.de>
Subject: Re: tricore-debian-cross-container CI job failing
Date: Thu, 12 Jan 2023 14:30:45 +0000	[thread overview]
Message-ID: <CAFEAcA8hFu4sGgJ3CQhc26+j4s=JDbxLRcv1mVdtLTe9wsqLRA@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA9zUTAeSbMd_TaOzWfimHOus-=SdNA1XZ+3FO9-fAG3qg@mail.gmail.com>

On Thu, 12 Jan 2023 at 14:13, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> The tricore-debian-cross-container CI job has started failing for
> no obvious reason:
>
> https://gitlab.com/qemu-project/qemu/-/jobs/3593581274
>
> gcc -DHAVE_CONFIG_H -I. -I. -I. -D_GNU_SOURCE -I. -I. -I../bfd
> -I./../bfd -I./../include -I./../intl -I../intl -w
> -DLOCALEDIR="\"/usr/local/share/locale\"" -W -Wall -Wstrict-prototypes
> -Wmissing-prototypes -w -c `test -f 'ldgram.c' || echo './'`ldgram.c
> `test -f ldlex.l || echo './'`ldlex.l
> /bin/sh: 1: ldlex.l: not found

For comparison, here's another run of the same job, which
succeeded:
https://gitlab.com/qemu-project/qemu/-/jobs/3594096306

The difference is that in the success case Make doesn't think
it needs to rebuild ldlex.c or ldgram.c, but in the failure
case it does (and falls over because it can't). I don't know
why this is, maybe a random timestamp thing?

Anyway, to make the job reliable I think we need to have
flex and bison in the container.

thanks
-- PMM


      reply	other threads:[~2023-01-12 15:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 14:13 tricore-debian-cross-container CI job failing Peter Maydell
2023-01-12 14:30 ` Peter Maydell [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='CAFEAcA8hFu4sGgJ3CQhc26+j4s=JDbxLRcv1mVdtLTe9wsqLRA@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=kbastian@mail.uni-paderborn.de \
    --cc=qemu-devel@nongnu.org \
    /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).