[LLVMdev] [cfe-dev] LLVM IRC channel flooded?

David Blaikie dblaikie at gmail.com
Tue May 19 12:44:00 PDT 2015


On Tue, May 19, 2015 at 12:25 PM, Tobias Grosser <tobias at grosser.es> wrote:

> On 05/19/2015 08:50 PM, Chris Matthews wrote:
>
>> Just some stats, after looking through lab.llvm.org
>> <http://lab.llvm.org>:8011
>>
>> Maybe these should be marked as experimental, and removed from the
>> builders link on the main page.
>>
>> Never passed at all:
>> libcxx-libcxxabi-x86_64-linux-ubuntu-cxx03
>> libcxx-libcxxabi-x86_64-linux-ubuntu-ubsan
>> libcxx-libcxxabi-x86_64-linux-ubuntu-tsan
>> libcxx-libcxxabi-x86_64-linux-ubuntu-gcc
>> libcxx-libcxxabi-x86_64-apple-darwin14-system-lib
>> lldb-x86_64-ubuntu-14.04-android
>> llgo-x86_64-linux
>>
>> Not pass in at least a month:
>>
>> llvm-clang-lld-x86_64-debian-fast
>> clang-native-mingw32-win7
>> clang-x86_64-linux-selfhost-abi-test
>> clang-x64-ninja-win7-debug
>> perf-x86_64-penryn-O3-polly-detect-only
>> sanitizer-x86_64-linux-bootstrap
>> sanitizer_x86_64-freebsd
>> sanitizer-windows
>> libcxx-libcxxabi-x86_64-apple-darwin14-tot-clang
>> clang-amd64-openbsd
>> lldb-x86_64-debian-clang
>> lldb-x86_64-freebsd
>> lldb-x86_64-ubuntu-14.10
>>
>
> Chris, thanks for going through this!
>

Yep, totally - is there an easy way to gather this data on an ongoing
basis? (perhaps every month or so?)


> I am all in favor of removing/disabling these bots (and would be OK with
> being even more aggressive).
>

Yep, agreed - I'd say removing the buildbots that've never passed and at
least moving the ones that haven't passed recently to "experimental" is a
totally reasonable approach.


>
> The one Polly bot listed is a performance buildbot which has emails or IRC
> messages disabled. I now removed it completely from the buildbot list to
> also keep the web interface clean.
>
> Best,
> Tobias
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150519/53be340f/attachment.html>


More information about the llvm-dev mailing list