Thanks Davide,

I think several of these bots have not been maintained for a while. One thing 
we could do is try to ping the owners and see if it's possible to update the 
bots or if they're no longer useful, then remove them.


-----Original Message-----
From: Davide Italiano <> 
Sent: Friday, January 11, 2019 12:54 PM
To: Robinson, Paul <>; Pavel Labath <>; 
Zachary Turner <>; Stella Stamenova <>
Cc: LLDB <>
Subject: Re: [lldb-dev] LLDB bot health

On Fri, Jan 11, 2019 at 9:20 AM via lldb-dev <> wrote:
> Inspired by people recently asking about or filing bugs for test fails 
> that happen in their own environments, I thought I might do the same.
> "But wait," I thought, "maybe some bots are already finding these."
> Which led me to discover:
> lldb-amd64-ninja-netbsd8             green
> lldb-windows7-android                test failures
> lldb-x64-windows-ninja               test failures
> lldb-x86-windows-msvc2015            out of disk space
> lldb-x86_64-darwin-13.4              cmake errors
> lldb-x86_64-ubuntu-14.04-android     cmake errors
> lldb-x86_64-ubuntu-14.04-buildserver green
> lldb-x86_64-ubuntu-14.04-cmake       test failures

Thanks for your feedback. As one of the people who encouraged users to report 
failures they see locally, I would like to point out I wasn't really aware of 
the existence of many of these bots.
I'm aware there's a subset of people watching the MacOS bots, which are now in 
a decent state (as part of their day job).
(I personally never heard of the darwin-13.4 bot but if overlaps with what the 
lldb greendragon bots are testing, it could be as well dismissed, i.e.;;sdata=5UGO69QDiMvM2reR9FP5CxoJeGHQswClNbBdfYFpT4I%3D&amp;reserved=0)

I will personally watch these bots more closely, I cc:ed some of the people 
involved to see if we can make the situation better.
Have you considered debugging some of the issues you're seeing locally? I'm 
pretty sure some help would be appreciated.

lldb-dev mailing list

Reply via email to