llvm dev - Aug 2015 - buildbot failure in LLVM on clang-native-arm-cortex-a9

@Galina: It seems this bot is now almost permanently running into a compile-time
timeout. Maybe you can fix this by either increasing the timeout or by
switching to a cmake/ninja based build as suggested by Renato.

On 08/26/2015 05:21 PM, Renato Golin via llvm-dev wrote:
> On 26 August 2015 at 15:44, Tobias Grosser <tobias at grosser.es>
wrote:
>> What time-line do you have in mind for this fix? If you are in charge
>> and can make this happen within a day, giving cmake + ninja a chance
seems
>> OK.
>
> It's not my bot. All my bots are CMake+Ninja based and are stable
enough.
I should have looked it up myself. I did not want to finger-point, but
ensure we understand who will address this issue. I just looked up who
owns these builders and to my understanding it is Galina herself.
I CC her such that she can take action.

I also have the feeling I was generally to harsh in my mail, as I seem
to have triggered a rather defensive reply. Sorry for this.

Regarding the discussion about disabling/enabling buildbots. I agree with
Mehdi there is no black and white. For this bot, it seems important to
address this issue as it seems to start failing very regularly now.

Regarding my own bots: In case you see flaky polly buildbots or any other
of my bots sending emails without reason, please send me a short ping
such that I can fix the issue. None of my LNT bots send emails as they
run too long before starting to report.

Best,
Tobias

On 26 August 2015 at 17:27, Tobias Grosser <tobias at grosser.es>
wrote:
> @Galina: It seems this bot is now almost permanently running into a
> compile-time
> timeout. Maybe you can fix this by either increasing the timeout or by
> switching to a cmake/ninja based build as suggested by Renato.
How I fixed my bots:

1. Remove cmake and ninja from your system. They are too old.
2. Download cmake stable sources (3.2+), untar, bootstrap, make, make install
3. Checkout ninja from github, bootstrap, copy "ninja" to
/usr/local/bin
4. Install ccache from packages, add ccache to path
5. Change the builder to ClangCMakeBuilder like all ARM and AArch64 bots now in.
6. Restart.

The Ninja+CMake combo has a feature that makes sure you print
everything without buffering, so the time out works exactly as
intended: if any single process takes more than that time, it's a bug.

I'm copying Gabor, as AFAIK, his bot is not based on the new
CMake+Ninja fix, but on an old polling script we had, which makes
timeouts useless.

Let's try this one first, and only consider any more drastic solution after.

cheers,
--renato

On Wed, Aug 26, 2015 at 9:34 AM, Renato Golin via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On 26 August 2015 at 17:27, Tobias Grosser <tobias at grosser.es>
wrote:
> > @Galina: It seems this bot is now almost permanently running into a
> > compile-time
> > timeout. Maybe you can fix this by either increasing the timeout or by
> > switching to a cmake/ninja based build as suggested by Renato.
>
> How I fixed my bots:
>
> 1. Remove cmake and ninja from your system. They are too old.
> 2. Download cmake stable sources (3.2+), untar, bootstrap, make, make
> install
> 3. Checkout ninja from github, bootstrap, copy "ninja" to
/usr/local/bin
> 4. Install ccache from packages, add ccache to path
> 5. Change the builder to ClangCMakeBuilder like all ARM and AArch64 bots
> now in.
> 6. Restart.
>
> The Ninja+CMake combo has a feature that makes sure you print
> everything without buffering, so the time out works exactly as
> intended: if any single process takes more than that time, it's a bug.
>
> I'm copying Gabor, as AFAIK, his bot is not based on the new
> CMake+Ninja fix, but on an old polling script we had, which makes
> timeouts useless.
>
> Let's try this one first, and only consider any more drastic solution
> after.
>
*shrug* I haven't looked at whatever specific bots are under discussion,
but I really wouldn't mind/would like if the bots had a more "revert to
green" feel to them just like we have for commits: take a bot offline,
fix/iterate/improve it, see if it comes good, then bring it back to the
mainline.

>
> cheers,
> --renato
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20150826/b7ad08d6/attachment.html>