Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] LLVM Buildbot Web UI slow responds"
2020 Oct 13
2
[Lldb-commits] Upcoming upgrade of LLVM buildbot
Switched all but PPC, I don't have access to them. But they run the same
script as sanitizer-x86_64-linux.
http://lab.llvm.org:8014/#/waterfall?tags=sanitizer
On Mon, 12 Oct 2020 at 19:19, Galina Kistanova <gkistanova at gmail.com> wrote:
> We have a better version of AnnotatedCommand on the staging. It should be
> a functional equivalent of the old one.
> We need to stress
2020 Oct 08
2
[cfe-dev] Upcoming upgrade of LLVM buildbot
Hi Paula,
This error is fine. The buildbot has tested the worker version. 0.8.x
apparently does not have that method.
The error gets handled gracefully on the server side. At least it seems so
so far.
That should not prevent your bot from connecting.
Thanks
Galina
On Thu, Oct 8, 2020 at 2:11 PM Paula Askar <paulatoth at google.com> wrote:
> Hey Andrzej,
>
> What are you seeing
2020 Oct 08
3
[cfe-dev] Upcoming upgrade of LLVM buildbot
Our Flang-aarch64 buildbots just won't connect to the main Buildbot
master anymore. I switched them to the staging buildbot master instead
and it seems fine for now. Is there anything that we can/should tweak at
our end?
http://lab.llvm.org:8014/#/waterfall?tags=flang
-Andrzej
On 08/10/2020 00:31, Galina Kistanova via cfe-dev wrote:
> They are online now -
2020 Oct 12
3
[Lldb-commits] Upcoming upgrade of LLVM buildbot
On Wed, Oct 7, 2020 at 4:32 PM Galina Kistanova via lldb-commits <
lldb-commits at lists.llvm.org> wrote:
> They are online now - http://lab.llvm.org:8011/#/waterfall?tags=sanitizer
>
> AnnotatedCommand has severe design conflict with the new buildbot.
> We have changed it to be safe and still do something useful, but it will
> need more love and care.
>
> Please let me
2020 Oct 07
4
Upcoming upgrade of LLVM buildbot
It looks like all sanitizer builder are still offline
http://lab.llvm.org:8011/#/builders
On Tue, 6 Oct 2020 at 00:34, Galina Kistanova via cfe-commits <
cfe-commits at lists.llvm.org> wrote:
> Hello everyone,
>
> The staging buildbot was up and running for 6 days now, and looks good.
>
> Tomorrow at 12:00 PM PDT we will switch the production buildbot to the new
>
2012 Nov 15
0
[LLVMdev] Code Ownership - Buildbot
kinda random, but do we have a centralized list of all of the
buildbots? I see a lot of different URL's in IRC, but no list so I can
check "all of the waterfalls". I'm not talking about the specific bots
(e.g. llvm-x86_64-ubuntu) but the "fleets" (e.g.http://lab.llvm.org).
Could you maybe add a little bulleted list (or link to a list) to
docs/HowToAddABuilder.rst?
2012 Nov 15
3
[LLVMdev] Code Ownership - Buildbot
I'd like to take code ownership of the LLVM Buildbot code.
Thanks
Galina
2015 Jun 18
2
[LLVMdev] Contributing a buildbot for the BPF backend
Thank you.
Alexei just committed the change to SVN.
Regards,
Marco Leogrande
Sent by a carbon-based life form; hence, it may contain repetitions,
inaccuracies, logical fallacies and repetitions.
On Wed, Jun 17, 2015 at 2:52 PM, Galina Kistanova <gkistanova at gmail.com> wrote:
> LGTM.
> Please commit.
>
> Thanks
>
> Galina
>
> On Tue, Jun 16, 2015 at 8:32 PM,
2011 Sep 20
2
[LLVMdev] Clang build "clang-native-arm-cortex-a9" is broken
The host c++ standard library is missing <utility>, it appears.
On Sep 20, 2011, at 11:22 AM, Galina Kistanova wrote:
> Please use the correct link :
> http://63.145.236.72:8011
> and ignore the previous.
>
> Also log for broken build is here:
>
> make[1]: Entering directory
>
2011 Oct 31
1
[LLVMdev] LLVM buildbot infrastructure
Hello everyone,
We have a number of issues with the current buildbot infrastructure.
During this week I will be addressing 2 which I think are most
important.
1. There is no well specified dependencies, so all builders get
triggered by any change in any of watched projects. I.e. lldb change
triggers clang build and versa versa.
2. If a project depends on multiple others, sequential changes could
2012 Nov 15
3
[LLVMdev] Code Ownership - Buildbot
On Thu, Nov 15, 2012 at 2:10 PM, Sean Silva <silvas at purdue.edu> wrote:
> kinda random, but do we have a centralized list of all of the
> buildbots? I see a lot of different URL's in IRC, but no list so I can
> check "all of the waterfalls". I'm not talking about the specific bots
> (e.g. llvm-x86_64-ubuntu) but the "fleets"
2011 Sep 20
3
[LLVMdev] Clang build "clang-native-arm-cortex-a9" is broken
Hello everybody,
Just a short note that clang build "clang-native-arm-cortex-a9" is
broken and the very last successful build was for revision 139932.
All newer revisions fail.
The builder is available here:
http://172.16.0.135:8011/waterfall
Thanks
Galina
2011 Sep 20
0
[LLVMdev] Clang build "clang-native-arm-cortex-a9" is broken
Please use the correct link :
http://63.145.236.72:8011
and ignore the previous.
Also log for broken build is here:
make[1]: Entering directory
`/home/buildslave/zorg/buildbot/osuosl/slave/clang-native-arm-cortex-a9/llvm/lib/Support'
llvm[1]: Compiling APFloat.cpp for Release+Asserts build
llvm[1]: Compiling APInt.cpp for Release+Asserts build
In file included from APFloat.cpp:15:
In file
2011 Sep 20
1
[LLVMdev] [cfe-commits] Clang build "clang-native-arm-cortex-a9" is broken
Yeah. That code has been there since r91421 and wouldn't have failed recently otherwise. Did something change on the host?
-eric
On Sep 20, 2011, at 11:27 AM, Jim Grosbach wrote:
> The host c++ standard library is missing <utility>, it appears.
>
>
> On Sep 20, 2011, at 11:22 AM, Galina Kistanova wrote:
>
>> Please use the correct link :
>>
2011 Sep 21
0
[LLVMdev] [cfe-commits] Clang build "clang-native-arm-cortex-a9" is broken
I have tracked it down to the real reason.
The revisions 139934-139937 has changed the order in which configure
chooses a compiler. Clang is checked first, then llvm-gcc, and then
gcc.
I can see the reason for this change.
However, in this particular case it has broken the build because
Ubuntu includes clang 2.8 which doesn't know where includes are.
I have removed clang from the host to
2017 Dec 06
3
buildbot failure in LLVM on llvm-clang-x86_64-expensive-checks-win
I’ve had another look, and some of the failing tests don’t use temporary files, so I don’t think this is a case of tests having side-effects.
Instead, I’ve noticed that in the build log (http://lab.llvm.org:8011/builders/llvm-clang-x86_64-expensive-checks-win/builds/6552/steps/build-unified-tree/logs/stdio), llvm-tblgen.exe is built (my patch modified it), but the table-generation steps of the
2015 Nov 03
2
Revisions that cause buildbot problems but aren't on blame lists
Hi Galina,
The failing build was http://lab.llvm.org:8011/builders/clang-cmake-mips/builds/10220 and the commit that caused it was 'r251331 [compiler-rt] Fix ptrace interceptor for aarch64'.
________________________________
From: Galina Kistanova [gkistanova at gmail.com]
Sent: 02 November 2015 16:03
To: Daniel Sanders
Cc: Renato Golin; Bill Seurer; LLVM Dev
Subject: Re: [llvm-dev]
2011 Nov 19
1
[LLVMdev] [llvm-commits] [zorg] r144978 - /zorg/trunk/buildbot/osuosl/master/config/builders.py
Galina,
Looks like the build bots have frozen.
Expected?
Joe
Joe Abbey
Software Architect
Arxan Technologies, Inc.
1305 Cumberland Ave, Ste 215
West Lafayette, IN 47906
jabbey at arxan.com<mailto:jabbey at arxan.com>
www.arxan.com<http://www.arxan.com/>
On Nov 18, 2011, at 11:49 AM, Galina Kistanova wrote:
Author: gkistanova
Date: Fri Nov 18 13:49:26 2011
New Revision: 144978
2015 Jun 17
2
[LLVMdev] Contributing a buildbot for the BPF backend
Galina,
thanks again for your help.
I have cooked a new patch that should make a bit more sense.
I have added the new builder under
_get_experimental_scheduled_builders(), as the comment above that
function suggested me it would be a good idea. :)
Does it look a reasonable start?
Regards,
Marco Leogrande
Sent by a carbon-based life form; hence, it may contain repetitions,
inaccuracies,
2020 Sep 11
4
Upcoming upgrade of LLVM buildbot
Hello everyone,
The buildbot upgrade is entering the phase when the results to become
visible.
No change is required at this time on any of the builders. The bot owners
could upgrade the buildbot on build computers later, at their convenience,
as this is not on the critical path.
We are going to upgrade the staging bot first. Then, once that is stable
and all detected issues are resolved, we