llvm dev - Dec 2014 - [LLVMdev] [cfe-dev] Major ARM bots failure

r223478 seems to be responsible for PR21770:
http://llvm.org/bugs/show_bug.cgi?id=21770

On Fri, Dec 5, 2014 at 3:10 PM, Daniel Sanders <Daniel.Sanders at
imgtec.com>
wrote:
> I'm not sure if it helps but the clang builder for mips has been dying
of
> timeouts since
> http://lab.llvm.org:8011/builders/clang-cmake-mips/builds/389 which only
> has one commit in the blamelist (r223478 - LLVMContext: Store APInt/APFloat
> directly into the ConstantInt/FP DenseMaps.). I see the same commit in the
> build you linked to.
> ________________________________________
> From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] on
behalf
> of Renato Golin [renato.golin at linaro.org]
> Sent: 05 December 2014 22:46
> To: LLVM Dev; Clang Dev
> Cc: Benjamin Kramer
> Subject: [LLVMdev] Major ARM bots failure
>
> Folks,
>
> I'm not sure what happened, but some commit in this build made Clang
> run forever on ARM:
>
> http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15/builds/2203
>
> The missing commits are to the sanitizers and they are not even
> checked out on this bot, so I don't think it has anything to do with
> that. It's also unlikely to be something on the Hexagon back-end,
> since all changes are self-contained.
>
> Any ideas?
>
> I had to completely turn off all bots, since the tests time out and
> the next build starts with the current build running at 100% CPU,
> accumulating, and killing the board.
>
> cheers,
> --renato
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20141205/248a3990/attachment.html>

> On 06.12.2014, at 00:49, David Majnemer <david.majnemer at gmail.com>
wrote:
> 
> r223478 seems to be responsible for PR21770:
http://llvm.org/bugs/show_bug.cgi?id=21770
Reverted for now. Not sure what's going on there. Sorry for the breakage.

- Ben
> 
> On Fri, Dec 5, 2014 at 3:10 PM, Daniel Sanders <Daniel.Sanders at
imgtec.com> wrote:
> I'm not sure if it helps but the clang builder for mips has been dying
of timeouts since http://lab.llvm.org:8011/builders/clang-cmake-mips/builds/389
which only has one commit in the blamelist (r223478 - LLVMContext: Store
APInt/APFloat directly into the ConstantInt/FP DenseMaps.). I see the same
commit in the build you linked to.
> ________________________________________
> From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] on
behalf of Renato Golin [renato.golin at linaro.org]
> Sent: 05 December 2014 22:46
> To: LLVM Dev; Clang Dev
> Cc: Benjamin Kramer
> Subject: [LLVMdev] Major ARM bots failure
> 
> Folks,
> 
> I'm not sure what happened, but some commit in this build made Clang
> run forever on ARM:
> 
> http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15/builds/2203
> 
> The missing commits are to the sanitizers and they are not even
> checked out on this bot, so I don't think it has anything to do with
> that. It's also unlikely to be something on the Hexagon back-end,
> since all changes are self-contained.
> 
> Any ideas?
> 
> I had to completely turn off all bots, since the tests time out and
> the next build starts with the current build running at 100% CPU,
> accumulating, and killing the board.
> 
> cheers,
> --renato
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> 
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>

On 6 December 2014 at 00:03, Benjamin Kramer <benny.kra at gmail.com>
wrote:
> Reverted for now. Not sure what's going on there. Sorry for the
breakage.
No worries, at least that was easy to spot. Huzzah for buildbots! :)

cheers,
--renato