Displaying 6 results from an estimated 6 matches for "numbuild".
Did you mean:
numbuilds
2020 Jul 30
2
[Buildbots] - Looking for help with new 32 bit Windows buildbot
...ding LLVM on Windows with Visual Studio
- running a Windows buildbot
- Running Windows in a cloud environment in a stable, reproducible and
maintainable way
So I'm looking for someone to help me to debug and fix the buildbot
<http://lab.llvm.org:8014/builders/clang-x86-ninja-win10?numbuilds=200>and
get it into a stable state.
Links on the current state and the setup:
- Builder
<http://lab.llvm.org:8014/builders/clang-x86-ninja-win10?numbuilds=200> on
staging with current list of failing tests
- generic Visual Studio Docker image
<https://github.com/llvm/l...
2015 May 29
2
[LLVMdev] Confusing buildbot failure in LLVM on sanitizer-x86_64-linux
Happened to me again:
http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/18273/steps/annotate/logs/stdio
In fact, this whole bot has a 20% failure rate with the same failure mode,
from looking at the history:
http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/?numbuilds=50
They all end with this:
[100%] Running ThreadSanitizer tests
-- Testing: 258 tests, 16 threads --
Testing: 0 .. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90..
command timed out: 1200 seconds without output, attempting to kill
It seems like we'd get a lot more value from this bot if we just...
2015 May 14
0
[LLVMdev] Confusing buildbot failure in LLVM on sanitizer-x86_64-linux
+dvyukov
On Wed, May 13, 2015 at 11:08 AM, David Blaikie <dblaikie at gmail.com> wrote:
>
>
> On Wed, May 13, 2015 at 10:39 AM, Reid Kleckner <rnk at google.com> wrote:
>
>> It's a 20m timeout without output.
>>
>> If you back up to the build and look at the 'annotate' step output,
>> there's this text:
>>
>>
2012 Nov 12
0
[LLVMdev] Need help reading the LLVM Buildbot results
On Mon, Nov 12, 2012 at 7:03 AM, David Tweed <david.tweed at arm.com> wrote:
>> I don't believe so - I think only a certain sliding window of logs are
>> kept (& I don't know of an easy way to view a particular revision
>> across the bots either)
>
> For me a bigger issue has been inability to see a long list of results for a
> particular builder (say,
2015 May 13
2
[LLVMdev] Confusing buildbot failure in LLVM on sanitizer-x86_64-linux
On Wed, May 13, 2015 at 10:39 AM, Reid Kleckner <rnk at google.com> wrote:
> It's a 20m timeout without output.
>
> If you back up to the build and look at the 'annotate' step output,
> there's this text:
>
> http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux/builds/17916/steps/annotate/logs/stdio
>
> -- Testing: 258 tests, 16 threads --
>
2012 Nov 10
6
[LLVMdev] Need help reading the LLVM Buildbot results
>From r167602 and onwards I get a fail in 'make check-all' for llvm+clang, built with gcc-4.7.1 (but not with clang-3.1) on Linux x86_64:
Failing Tests (1):
Clang :: CodeGenCXX/mangle-ms-templates.cpp
clang: /dev/shm/uabpath/master/include/llvm/Support/Casting.h:208: typename llvm::cast_retty<To, From>::ret_type llvm::cast(const Y&) [with X =