qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 4/5] travis.yml: Fix the ccache lines


From: Philippe Mathieu-Daudé
Subject: Re: [PATCH 4/5] travis.yml: Fix the ccache lines
Date: Thu, 10 Oct 2019 13:51:32 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0

On 10/10/19 1:29 PM, Thomas Huth wrote:
On 10/10/2019 13.16, Philippe Mathieu-Daudé wrote:
On 10/10/19 11:38 AM, Thomas Huth wrote:
On 09/10/2019 21.04, Philippe Mathieu-Daudé wrote:
On 10/9/19 7:07 PM, Thomas Huth wrote:
The "command -v ccache && ccache ..." likely were supposed to test
the availability of ccache before running the program. But this
shell construct causes Travis to abort if ccache is not available.

Oops.

Why can't you install ccache if these are Ubuntu systems?
It is even more wanted if the arm64 machine are slow...

I just tried to add "ccache" to the list of packages that should be
installed, but I don't see a difference in the runtime.

First run with ccache enabled:

   https://travis-ci.com/huth/qemu/jobs/244117945

Second run where I'd expect a speedup:

   https://travis-ci.com/huth/qemu/jobs/244124599

The statistics at the end say that it had only 1 cache hit. Any ideas
what might be wrong here?

Looking there and your following commit
(https://github.com/huth/qemu/commit/eaf80e7851) I see you already
figured this out :)

No, that was just a try, but it did not change anything:

  https://travis-ci.com/huth/qemu/jobs/244137697#L5813

Oh I checked the x86 build then...

https://travis-ci.com/huth/qemu/jobs/244137696#L11299

But I also noticed that in the arm64 builds, the cache information is
missing:

  https://travis-ci.com/huth/qemu/jobs/244137697#L1844

... so I assume that ccache support needs to be supported in the image
that is provided by Travis, and you can not simply install it
afterwards. So this is likely just a quirk that hopefully will be fixed
by Travis later (arm64 is still marked as "alpha" there if I've got that
right).

Ah, you might be correct.

If so, your job is now ready to use the feature once they enable it :)



reply via email to

[Prev in Thread] Current Thread [Next in Thread]