From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] travis builds: failing because of duff data in ccache cache?
Date: Mon, 22 Aug 2016 10:33:48 +0100 [thread overview]
Message-ID: <87eg5hw3k3.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA-UugbO4SEyYvkR9BFHTpi624twfGFA4o6n2sjt55e5cA@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> Hi; since commit 4b887ae travis builds have been persistently
> failing on one particular config with the error:
> exec.o: could not read symbols: File truncated
> trying to link the mipsn32-linux-user binary.
>
> My theory is that the problem here is that:
> * for one build, the build host ran out of disk space or otherwise
> hiccupped, resulting in a truncated .o file
> * since travis saves the ccache cache across builds, the truncated .o
> file has persisted and now every build is going to fail the same
> way (until something gets committed that results in exec.c or one
> of its included headers changing)
>
> It looks like there's a way to manually clear the cache, so that
> seems like a good first step to see if it fixes things:
> https://docs.travis-ci.com/user/caching/#Clearing-Caches
>
> Could somebody with admin access to our travis config try this,
> please?
I've reset the cache for the master branch and restarted the build.
FWIW anyone who is a member of the QEMU project on Github should have
the permissions to tweak the Travis caches for the project.
>
> thanks
> -- PMM
--
Alex Bennée
next prev parent reply other threads:[~2016-08-22 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 17:10 [Qemu-devel] travis builds: failing because of duff data in ccache cache? Peter Maydell
2016-08-22 9:33 ` Alex Bennée [this message]
2016-08-22 9:36 ` Peter Maydell
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=87eg5hw3k3.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--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).