If you look at the bot online, there's usually an admin listed. For example:
http://lab.llvm.org:8011/buildslaves
I've CC'd the admins of the bots from Paul's list that are failing.
Thanks,
-Stella
-Original Message-
From: Davide Italiano
Sent: Friday, January 11, 2019 3:12 PM
To: Ste
I own this one: lldb-x86-windows-msvc2015
It can be removed, especially now that Stella's is strictly better than
mine was even when it was working.
There will probably be an effort on our side to get the Linux bots up and
running again "soon", but I don't have an exact timeline right now.
On Fr
On Fri, Jan 11, 2019 at 3:07 PM Stella Stamenova wrote:
>
> 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.
>
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.
Thanks,
-Stella
-Original Message-
From: Davide Italiano
Se
https://bugs.llvm.org/show_bug.cgi?id=40295
Bug ID: 40295
Summary: TestLibCxxFunction is flaky on Linux (Ubuntu)
Product: lldb
Version: 7.0
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
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:
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-andro
Hi Gabor
Is this behavior reproducible with the current upstream LLDB? (after
https://reviews.llvm.org/D55013)
Did you follow the instructions in docs/code-signing.txt?
> There is a setting to disable it. These days, you should be able to achieve
> it with LLDB_CODESIGN_IDENTITY="" or SKIP_DEBU
