[clang] 00ecf3f - Added a note that "%p" is also a Lit token and needs to be escaped.

[Galina Kistanova via cfe-commits]

Author: Flash Sheridan
Date: 2023-01-27T17:57:59-08:00
New Revision: 00ecf3f339624dc8b44737a2347076382de3720f

URL: 
https://github.com/llvm/llvm-project/commit/00ecf3f339624dc8b44737a2347076382de3720f
DIFF: 
https://github.com/llvm/llvm-project/commit/00ecf3f339624dc8b44737a2347076382de3720f.diff

LOG: Added a note that "%p" is also a Lit token and needs to be escaped.

Differential revision: https://reviews.llvm.org/D140730

Added: 


Modified: 
clang/docs/SourceBasedCodeCoverage.rst

Removed: 




diff  --git a/clang/docs/SourceBasedCodeCoverage.rst 
b/clang/docs/SourceBasedCodeCoverage.rst
index f92e8d8fc4d6..3a5d1cefb7e5 100644
--- a/clang/docs/SourceBasedCodeCoverage.rst
+++ b/clang/docs/SourceBasedCodeCoverage.rst
@@ -130,7 +130,8 @@ backend during compilation.
 For a program such as the :doc:`Lit ` testing tool which
 invokes other programs, it may be necessary to set ``LLVM_PROFILE_FILE`` for
 each invocation. The pattern strings "%p" or "%Nm" may help to avoid
-corruption due to concurrency.
+corruption due to concurrency. Note that "%p" is also a Lit token and needs
+to be escaped as "%%p".
 
 .. code-block:: console
 



___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

[clang] 01f13f4 - Explain code coverage with Lit in docs/SourceBasedCodeCoverage.rst

[Galina Kistanova via cfe-commits]

Author: Flash Sheridan
Date: 2023-01-27T17:51:18-08:00
New Revision: 01f13f4877751e6d5aa6f07984ebd76f67047839

URL: 
https://github.com/llvm/llvm-project/commit/01f13f4877751e6d5aa6f07984ebd76f67047839
DIFF: 
https://github.com/llvm/llvm-project/commit/01f13f4877751e6d5aa6f07984ebd76f67047839.diff

LOG: Explain code coverage with Lit in docs/SourceBasedCodeCoverage.rst

The documentation for code coverage in clang/docs/SourceBasedCodeCoverage.rst 
omits a couple of crucial steps when using it with Lit.
This patch should fix that.

Differential revision: https://reviews.llvm.org/D140730

Added: 


Modified: 
clang/docs/SourceBasedCodeCoverage.rst

Removed: 




diff  --git a/clang/docs/SourceBasedCodeCoverage.rst 
b/clang/docs/SourceBasedCodeCoverage.rst
index 5f4bcf8e0ff09..f92e8d8fc4d65 100644
--- a/clang/docs/SourceBasedCodeCoverage.rst
+++ b/clang/docs/SourceBasedCodeCoverage.rst
@@ -127,6 +127,11 @@ copy that's mapped into memory). This implementation can 
be also enabled for
 other platforms by passing the ``-runtime-counter-relocation`` option to the
 backend during compilation.
 
+For a program such as the :doc:`Lit ` testing tool which
+invokes other programs, it may be necessary to set ``LLVM_PROFILE_FILE`` for
+each invocation. The pattern strings "%p" or "%Nm" may help to avoid
+corruption due to concurrency.
+
 .. code-block:: console
 
 % clang++ -fprofile-instr-generate -fcoverage-mapping -mllvm 
-runtime-counter-relocation foo.cc -o foo
@@ -143,6 +148,9 @@ coverage reports. This is done using the "merge" tool in 
``llvm-profdata``
 # Step 3(a): Index the raw profile.
 % llvm-profdata merge -sparse foo.profraw -o foo.profdata
 
+For an example of merging multiple profiles created by testing,
+see the LLVM `coverage build script 
`_.
+
 There are multiple 
diff erent ways to render coverage reports. The simplest
 option is to generate a line-oriented report:
 



___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM lab will be unavailable today starting 1:30 PM PST

[Galina Kistanova via cfe-commits]

Hello,

LLVM lab will be unavailable for a few hours today starting 1:30 PM PST for
maintenance.
I will send an update when it is completed.

Thank you for understanding.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted at 9pm PST today

[Galina Kistanova via cfe-commits]

Hello,

LLVM build master will be restarted at 9pm PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello,

LLVM build master will be restarted at 8pm PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted at 1PM PST

[Galina Kistanova via cfe-commits]

 Hello,

LLVM build master will be restarted at 1pm PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello,

LLVM build master will be restarted at 3 PM PST.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello,

LLVM build master will be restarted at 7pm PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted shortly

[Galina Kistanova via cfe-commits]

 Hello,

LLVM build master will be restarted shortly.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello,

LLVM build master will be restarted at 9 PM PST.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello,

LLVM build master will be restarted at 9 PM PST.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be restarted at 8 PM PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be restarted tonight

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be restarted after 6 PM PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be offline for 1 hr for maintenance

[Galina Kistanova via cfe-commits]

Hello everyone,

LLVM Lab along with the both production and staging build bots will be
offline for about 1 hrs starting at 7:00 PM PST for maintenance.

Thank you for understanding.

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted soon

[Galina Kistanova via cfe-commits]

Hello,

LLVM build master will be restarted in the nearest hour.

Thank you for understanding.

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Re: Maintenance works at llvm lab today at 7PM PST

[Galina Kistanova via cfe-commits]

LLVM lab and build bot are back to normal work.

Thanks

Galina

On Fri, Oct 1, 2021 at 4:50 PM Galina Kistanova 
wrote:

> Hello everyone,
>
> LLVM lab and build bot will be unavailable for about an hour starting from
> 7:00 PM PST today for some maintenance work.
>
> Thank you for understanding.
>
> Galina
>
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Maintenance works at llvm lab today at 6PM PST

[Galina Kistanova via cfe-commits]

Hello everyone,

LLVM lab and build bot will be unavailable for about an hour starting from
6:00 PM PST today for maintenance works.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello,

LLVM build master will be restarted in the nearest hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello,

LLVM build master will be restarted in the nearest hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello,

LLVM build master will be restarted in the nearest hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Maintenance works at llvm lab today

[Galina Kistanova via cfe-commits]

Hello everyone,

LLVM lab and build bot will be unavailable for about 3 hours starting from
6:00 PM PST today for lab maintenance work.

Thank you for understanding.

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello,

LLVM build master will be restarted in the nearest hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello,

LLVM build master will be restarted at 6 PM PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello,

LLVM build master will be restarted at 9 PM PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Maintenance works at llvm lab today at 7PM PST

[Galina Kistanova via cfe-commits]

Hello everyone,

LLVM lab and build bot will be unavailable for about an hour starting from
7:00 PM PST today for some maintenance work.

Thank you for understanding.

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Maintenance works in LLVM Lab today at 11:00 PM PDT

[Galina Kistanova via cfe-commits]

Hello everyone,

LLVM Lab and the build bot will be unavailable today, September 25th, for
about 30 minutes starting from 11:00 PM PDT due to some maintenance work.

Thank you for your understanding and patience.

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM lab and buildbot master are back to normal

[Galina Kistanova via cfe-commits]

Hello everyone,

The LLVM lab and buildbot master are back to normal, up and running.
Died network hardware has been replaced. Please let me know if you still
see issues.

Sorry for the inconvenience and thanks for your patience.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM lab network outage

[Galina Kistanova via cfe-commits]

Hello,

There is a network outage in the llvm lab.

We are working with the technical support, but there is no ETA yet.
I'll keep everyone updated.

Sorry for the inconvenience.

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Maintenance works in llvm lab today at 5PM

[Galina Kistanova via cfe-commits]

Hello,

LLVM lab and build master will be unavailable today September 2 for about
30 minutes starting 5PM PST due maintenance works in the lab.
Thank you for understanding.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be restarted tonight

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be restarted at 5 PM PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Maintenance works at llvm lab today

[Galina Kistanova via cfe-commits]

Hello everyone,

LLVM lab and buildmaster will be unavailable for about an hour starting 5
PM PST today for maintenance works.
Thank you for understanding.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Maintenance works in llvm lab tomorrow June 29

[Galina Kistanova via cfe-commits]

Hello,

LLVM lab and build master will be unavailable tomorrow June 29 for about an
hour starting 2PM PST due maintenance works in the lab.
Thank you for understanding.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello,

LLVM build master will be restarted in the nearest hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted soon

[Galina Kistanova via cfe-commits]

Hello,

LLVM build master will be restarted in the nearest hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be restarted tonight

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be restarted at 8PM PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be restarted in the nearest hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be restarted tonight

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be restarted at 8 PM PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be restarted in the nearest hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be restarted in the nearest hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM build master will be restarted soon

[Galina Kistanova via cfe-commits]

Hello everyone,

LLVM buildmaster will be restarted in the nearest hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be restarted in the nearest hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be restarted tonight

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be restarted after 7PM PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be restarted tonight

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be restarted at 6PM PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Re: Buildbot to listen main branch

[Galina Kistanova via cfe-commits]

Hello everyone,

The buildbot listens to the "main" branch now.

Please let me know if you will see issues.

Thanks

Galina


On Tue, Dec 8, 2020 at 9:57 PM Galina Kistanova 
wrote:

> Hello everyone,
>
> To follow the main branch creation I'm going to update the buildbot to
> listen for the changes in this branch and instruct all the workers to
> checkout this branch.
>
> No work is required on the workers.
>
> Please check your annotated scripts to make sure it accepts the branch
> name from the buildbot, or change it if that's hardcoded.
>
> The staging has been updated today. I forced clean builds just to play it
> safe. Please check your bots in the staging area, to make sure everything
> is good.
>
> If everything will go well, the production buildbot will be updated on
> this Saturday, December, 12th.
>
> Thanks
>
> Galina
>
>
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be restarted tonight

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be restarted at 9PM PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Buildbot to listen main branch

[Galina Kistanova via cfe-commits]

Hello everyone,

To follow the main branch creation I'm going to update the buildbot to
listen for the changes in this branch and instruct all the workers to
checkout this branch.

No work is required on the workers.

Please check your annotated scripts to make sure it accepts the branch name
from the buildbot, or change it if that's hardcoded.

The staging has been updated today. I forced clean builds just to play it
safe. Please check your bots in the staging area, to make sure everything
is good.

If everything will go well, the production buildbot will be updated on this
Saturday, December, 12th.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be updated and restarted tonight

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be updated and restarted after 7PM PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be updated and restarted tonight

[Galina Kistanova via cfe-commits]

Hello everyone,

LLVM buildmaster will be updated and restarted after 8PM PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be updated and restarted tonight

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be updated and restarted after 8PM PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be restarted tonight

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be restarted after 6pm PST.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be restarted tonight

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be restarted after 9pm PST.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Re: [llvm-dev] Upcoming upgrade of LLVM buildbot

[Galina Kistanova via cfe-commits]

Hello Florian,

Thanks for pointing to the problem. Appreciate this.

It has been fixed and now failed builds reported with the blamelist.

Thanks

Galina

On Wed, Oct 21, 2020 at 5:30 AM Florian Hahn  wrote:

>
>
> On Oct 20, 2020, at 03:35, Galina Kistanova via llvm-dev <
> llvm-...@lists.llvm.org> wrote:
>
> Hello everyone,
>
> We have reached the point when all the bots could be updated to a newer
> buildbot-worker software.
>
> We should be fine to go with whatever the version is current for the OS on
> your bots.
>
> If you are a bot owner, please feel free to move your bots to the staging,
> upgrade the buildbot worker, check to make sure it is still reliably green,
> and move it back to the production build bot. Please talk to me if for any
> reason you want to stay with the version you currently have installed.
>
> Feel free to ping me if you will get issues or will need help.
>
> In the meantime, we will lock the llvm-zorg repository for changes for a
> few days. I'm going to clean up the patches for the updated zorg and will
> commit them. Once that is done we are back to accepting the changes.
>
> Please let me know if you have any questions.
>
>
> Thanks for all the work making the buildbot upgrade possible!
>
> One thing I noticed is that since the upgrade, it appears like the IRC
> llvm-build bot stopped mentioning people on the blamelist for broken
> builds. Unfortunately I don’t know much about the bot, is there anything
> that needs adjusting to bring the blamelist functionality back?
>
> Cheers,
> Florian
>
>
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Re: Upcoming upgrade of LLVM buildbot

[Galina Kistanova via cfe-commits]

Hello everyone,

The LLVM buildbot is upgraded.

Thanks for your patience and support!

llvm-zorg source code has been updated, and now is open for new changes. If
you have pending patches, please rebase them on top of the llvm-zorg master
and update your reviews on the Phabricator. I'll start reviewing them
shortly.

If you are a bot owner and your bot is still using buildbot 0.8.x version,
please move your bots to the staging, upgrade the buildbot worker software,
check to make sure it is still reliably green, and move it back to the
production build bot. Please talk to me if for any reason you want to stay
with the version you currently have. Feel free to ping me if you will get
issues or will need help.

Please let me know if you have any questions or see issues.

Thanks

Galina

On Mon, Oct 19, 2020 at 7:35 PM Galina Kistanova 
wrote:

> Hello everyone,
>
> We have reached the point when all the bots could be updated to a newer
> buildbot-worker software.
>
> We should be fine to go with whatever the version is current for the OS on
> your bots.
>
> If you are a bot owner, please feel free to move your bots to the staging,
> upgrade the buildbot worker, check to make sure it is still reliably green,
> and move it back to the production build bot. Please talk to me if for any
> reason you want to stay with the version you currently have installed.
>
> Feel free to ping me if you will get issues or will need help.
>
> In the meantime, we will lock the llvm-zorg repository for changes for a
> few days. I'm going to clean up the patches for the updated zorg and will
> commit them. Once that is done we are back to accepting the changes.
>
> Please let me know if you have any questions.
>
> Thanks
>
> Galina
>
>
> On Tue, Sep 29, 2020 at 11:24 PM Galina Kistanova 
> wrote:
>
>> Hello everyone,
>>
>> Starting tomorrow we will be upgrading the staging and production LLVM
>> build bot.
>>
>> To make the transition smooth we would not accept any change to zorg from
>> tomorrow 11:00 AM PDT till the production bot is up and running the new
>> version. Please feel free to talk to me if you will have a special
>> situation and if you would absolutely have to make changes. Thanks for your
>> patience and understanding.
>>
>> If you are a bot owner, you do not need to do anything at this point,
>> unless I'll ask you to help.
>>
>> Here is the plan.
>>
>> * Tomorrow, on September 30th, 2020, at 11:00 AM PDT we will upgrade the
>> staging build bot to buildbot v2.8.4.
>>
>> If you are an owner of one of the staged builders, you would not need to
>> do anything. The staging will go down for a short period of time, and then
>> a new version will come up and will accept connections from your bots.
>>
>> We will be watching the staging and will be improving zorg for the next
>> week or so. Meaning that staging will be restarted more often than before,
>> and restarts will be done without further notices.
>>
>> * Once the staging is reliable you may want to move your bot from
>> production to staging to make sure it will work as expected after the
>> upgrade. I will send a note when this could be done.
>>
>> * After staging is good and we have about a week of running history, we
>> will upgrade the production bot. I will send a separate announcement for
>> this closer to the date.
>>
>> Once the production is up and running, I will need your feedback about
>> blame e-mails delivery, IRC reporting issues, and anything you could spot
>> wrong with the new bot. I  hope the transition will go smoothly and we will
>> handle issues quickly if any would come up.
>>
>> * After production is good and we have about a week of running history,
>> I'll ask the bot owners to upgrade buildbots on their side. Please do not
>> upgrade your buildbots unless I'll ask you to. We are trying to limit a
>> number of moving parts at this stage.
>>
>> Thanks for your support and help. And please feel free to ask if you have
>> questions.
>>
>> Galina
>>
>>
>> On Thu, Sep 10, 2020 at 9:35 PM Galina Kistanova 
>> wrote:
>>
>>> 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 will upgrade the production bot.
>>>
>>> I will need some help with testing, and will be asking to move some of
>>> the builders temporarily to the staging. LLVM buildbot is a piece of
>>> critical infrastructure, so more eyes and hands in making sure it works
>>> properly the better.
>>>
>>> I'll be posting updates and ETA of particular changes in this thread.
>>>
>>> Please feel free to ask if you have any questions or concerns.
>>>
>>> Thanks
>>>
>>> Galina
>>>
>>>

Re: [Lldb-commits] Upcoming upgrade of LLVM buildbot

[Galina Kistanova via cfe-commits]

Hello Vitaly,

This should be fixed.

Please let me know if you still see the issue.

Thanks

Galina



On Tue, Oct 27, 2020 at 4:45 PM Vitaly Buka  wrote:

> It looks fixed. I haven't seen them in recent reports.
>
> On Tue, 27 Oct 2020 at 16:32, Vitaly Buka  wrote:
>
>> Any news regarding false-negatives?
>>
>> +Mitch Phillips 
>>
>> On Mon, 19 Oct 2020 at 22:07, Galina Kistanova 
>> wrote:
>>
>>> Thanks, Vitaly.
>>> Somebody is looking at this.
>>>
>>>
>>> On Mon, Oct 19, 2020 at 9:56 PM Vitaly Buka 
>>> wrote:
>>>
 it's not just staging, this build must be marked as failed
 http://lab.llvm.org:8011/#/builders/74/builds/122


 On Mon, 19 Oct 2020 at 11:50, Vitaly Buka 
 wrote:

> There is some issue, at least on staging.
> http://lab.llvm.org:8014/#/builders/89/builds/184 has multiple failed
> stages but marked as SUCCESS
>
>
> On Mon, 19 Oct 2020 at 11:43, Vitaly Buka 
> wrote:
>
>> Thanks!
>> Done.
>>
>> On Sat, 17 Oct 2020 at 12:45, Galina Kistanova 
>> wrote:
>>
>>> Thanks everyone for keeping your annotated builders in the staging
>>> area! Much appreciated.
>>>
>>> Please feel free to move all the green builders back to the
>>> production. It has a new AnnotatedCommand now.
>>>
>>> Thanks
>>>
>>> Galina
>>>
>>>
>>> On Thu, Oct 15, 2020 at 12:46 AM Vitaly Buka 
>>> wrote:
>>>
 Ok, I can switch them back to staging. However today's staging was
 frequently offline.


 On Wed, 14 Oct 2020 at 21:44, Galina Kistanova <
 gkistan...@gmail.com> wrote:

> Thanks everyone!
>
> I would like to keep the bots in the staging till Friday. And if
> everything is good, then apply the changes to the production and let 
> you
> move all the green bots back there.
>
> Thanks
>
> Galina
>
>
> On Tue, Oct 13, 2020 at 10:43 PM Vitaly Buka <
> vitalyb...@google.com> wrote:
>
>> They do on staging.
>> http://lab.llvm.org:8014/#/builders/sanitizer-windows
>> http://lab.llvm.org:8014/#/builders/clang-x64-windows-msvc
>>
>> Galina, when do you plan to push this to the primary server?
>> If it's a few days, I'd rather keep bots on staging to have
>> colors.
>>
>>
>>
>> On Tue, 13 Oct 2020 at 11:11, Reid Kleckner 
>> wrote:
>>
>>> FWIW, I don't see any issues with my two bots that use buildbot
>>> annotated commands:
>>> http://lab.llvm.org:8011/#/builders/sanitizer-windows
>>> http://lab.llvm.org:8011/#/builders/clang-x64-windows-msvc
>>> The individual steps don't highlight as green or red, but that's
>>> OK for now.
>>>
>>> On Mon, Oct 12, 2020 at 7:19 PM Galina Kistanova <
>>> gkistan...@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 test it well before moving to the production
 build bot.

 For that we need all sanitizer + other bots which use the
 AnnotatedCommand directly or indirectly moved temporarily to the 
 staging.

 Please let me know when that could be arranged.

 Thanks

 Galina

 On Mon, Oct 12, 2020 at 11:39 AM Reid Kleckner 
 wrote:

> On Wed, Oct 7, 2020 at 4:32 PM Galina Kistanova via
> lldb-commits  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 know if you have some spare time to work on
>> porting AnnotatedCommand.
>>
>
> That's unfortunate, it would've been good to know that
> earlier. I and another team member have spent a fair amount of 
> time porting
> things to use more AnnotatedCommand steps, because it gives us the
> flexibility to test steps locally and make changes to the steps 
> without
> restarting the buildbot master. IMO that is the Right Way to 
> define steps:
> a script that you can run locally on a machine that satisfies the 
> OS and
> dep requirements of the script.
>
> I am restarting the two bots that I 

LLVM buildmaster will be restarted tonight

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be restarted after 9pm PST.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Re: [llvm-dev] Upcoming upgrade of LLVM buildbot

[Galina Kistanova via cfe-commits]

Thanks, Florian! I will look into this.

Cheers

Galina

On Wed, Oct 21, 2020 at 5:30 AM Florian Hahn  wrote:

>
>
> On Oct 20, 2020, at 03:35, Galina Kistanova via llvm-dev <
> llvm-...@lists.llvm.org> wrote:
>
> Hello everyone,
>
> We have reached the point when all the bots could be updated to a newer
> buildbot-worker software.
>
> We should be fine to go with whatever the version is current for the OS on
> your bots.
>
> If you are a bot owner, please feel free to move your bots to the staging,
> upgrade the buildbot worker, check to make sure it is still reliably green,
> and move it back to the production build bot. Please talk to me if for any
> reason you want to stay with the version you currently have installed.
>
> Feel free to ping me if you will get issues or will need help.
>
> In the meantime, we will lock the llvm-zorg repository for changes for a
> few days. I'm going to clean up the patches for the updated zorg and will
> commit them. Once that is done we are back to accepting the changes.
>
> Please let me know if you have any questions.
>
>
> Thanks for all the work making the buildbot upgrade possible!
>
> One thing I noticed is that since the upgrade, it appears like the IRC
> llvm-build bot stopped mentioning people on the blamelist for broken
> builds. Unfortunately I don’t know much about the bot, is there anything
> that needs adjusting to bring the blamelist functionality back?
>
> Cheers,
> Florian
>
>
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Re: [Lldb-commits] Upcoming upgrade of LLVM buildbot

[Galina Kistanova via cfe-commits]

Thanks, Vitaly.
Somebody is looking at this.


On Mon, Oct 19, 2020 at 9:56 PM Vitaly Buka  wrote:

> it's not just staging, this build must be marked as failed
> http://lab.llvm.org:8011/#/builders/74/builds/122
>
>
> On Mon, 19 Oct 2020 at 11:50, Vitaly Buka  wrote:
>
>> There is some issue, at least on staging.
>> http://lab.llvm.org:8014/#/builders/89/builds/184 has multiple failed
>> stages but marked as SUCCESS
>>
>>
>> On Mon, 19 Oct 2020 at 11:43, Vitaly Buka  wrote:
>>
>>> Thanks!
>>> Done.
>>>
>>> On Sat, 17 Oct 2020 at 12:45, Galina Kistanova 
>>> wrote:
>>>
 Thanks everyone for keeping your annotated builders in the staging
 area! Much appreciated.

 Please feel free to move all the green builders back to the production.
 It has a new AnnotatedCommand now.

 Thanks

 Galina


 On Thu, Oct 15, 2020 at 12:46 AM Vitaly Buka 
 wrote:

> Ok, I can switch them back to staging. However today's staging was
> frequently offline.
>
>
> On Wed, 14 Oct 2020 at 21:44, Galina Kistanova 
> wrote:
>
>> Thanks everyone!
>>
>> I would like to keep the bots in the staging till Friday. And if
>> everything is good, then apply the changes to the production and let you
>> move all the green bots back there.
>>
>> Thanks
>>
>> Galina
>>
>>
>> On Tue, Oct 13, 2020 at 10:43 PM Vitaly Buka 
>> wrote:
>>
>>> They do on staging.
>>> http://lab.llvm.org:8014/#/builders/sanitizer-windows
>>> http://lab.llvm.org:8014/#/builders/clang-x64-windows-msvc
>>>
>>> Galina, when do you plan to push this to the primary server?
>>> If it's a few days, I'd rather keep bots on staging to have colors.
>>>
>>>
>>>
>>> On Tue, 13 Oct 2020 at 11:11, Reid Kleckner  wrote:
>>>
 FWIW, I don't see any issues with my two bots that use buildbot
 annotated commands:
 http://lab.llvm.org:8011/#/builders/sanitizer-windows
 http://lab.llvm.org:8011/#/builders/clang-x64-windows-msvc
 The individual steps don't highlight as green or red, but that's OK
 for now.

 On Mon, Oct 12, 2020 at 7:19 PM Galina Kistanova <
 gkistan...@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 test it well before moving to the production
> build bot.
>
> For that we need all sanitizer + other bots which use the
> AnnotatedCommand directly or indirectly moved temporarily to the 
> staging.
>
> Please let me know when that could be arranged.
>
> Thanks
>
> Galina
>
> On Mon, Oct 12, 2020 at 11:39 AM Reid Kleckner 
> wrote:
>
>> On Wed, Oct 7, 2020 at 4:32 PM Galina Kistanova via lldb-commits <
>> lldb-comm...@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 know if you have some spare time to work on
>>> porting AnnotatedCommand.
>>>
>>
>> That's unfortunate, it would've been good to know that earlier. I
>> and another team member have spent a fair amount of time porting 
>> things to
>> use more AnnotatedCommand steps, because it gives us the flexibility 
>> to
>> test steps locally and make changes to the steps without restarting 
>> the
>> buildbot master. IMO that is the Right Way to define steps: a script 
>> that
>> you can run locally on a machine that satisfies the OS and dep 
>> requirements
>> of the script.
>>
>> I am restarting the two bots that I am responsible for, and may
>> need some help debugging further issues soon. I'll let you know.
>>
>
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Re: Upcoming upgrade of LLVM buildbot

[Galina Kistanova via cfe-commits]

Hello everyone,

We have reached the point when all the bots could be updated to a newer
buildbot-worker software.

We should be fine to go with whatever the version is current for the OS on
your bots.

If you are a bot owner, please feel free to move your bots to the staging,
upgrade the buildbot worker, check to make sure it is still reliably green,
and move it back to the production build bot. Please talk to me if for any
reason you want to stay with the version you currently have installed.

Feel free to ping me if you will get issues or will need help.

In the meantime, we will lock the llvm-zorg repository for changes for a
few days. I'm going to clean up the patches for the updated zorg and will
commit them. Once that is done we are back to accepting the changes.

Please let me know if you have any questions.

Thanks

Galina


On Tue, Sep 29, 2020 at 11:24 PM Galina Kistanova 
wrote:

> Hello everyone,
>
> Starting tomorrow we will be upgrading the staging and production LLVM
> build bot.
>
> To make the transition smooth we would not accept any change to zorg from
> tomorrow 11:00 AM PDT till the production bot is up and running the new
> version. Please feel free to talk to me if you will have a special
> situation and if you would absolutely have to make changes. Thanks for your
> patience and understanding.
>
> If you are a bot owner, you do not need to do anything at this point,
> unless I'll ask you to help.
>
> Here is the plan.
>
> * Tomorrow, on September 30th, 2020, at 11:00 AM PDT we will upgrade the
> staging build bot to buildbot v2.8.4.
>
> If you are an owner of one of the staged builders, you would not need to
> do anything. The staging will go down for a short period of time, and then
> a new version will come up and will accept connections from your bots.
>
> We will be watching the staging and will be improving zorg for the next
> week or so. Meaning that staging will be restarted more often than before,
> and restarts will be done without further notices.
>
> * Once the staging is reliable you may want to move your bot from
> production to staging to make sure it will work as expected after the
> upgrade. I will send a note when this could be done.
>
> * After staging is good and we have about a week of running history, we
> will upgrade the production bot. I will send a separate announcement for
> this closer to the date.
>
> Once the production is up and running, I will need your feedback about
> blame e-mails delivery, IRC reporting issues, and anything you could spot
> wrong with the new bot. I  hope the transition will go smoothly and we will
> handle issues quickly if any would come up.
>
> * After production is good and we have about a week of running history,
> I'll ask the bot owners to upgrade buildbots on their side. Please do not
> upgrade your buildbots unless I'll ask you to. We are trying to limit a
> number of moving parts at this stage.
>
> Thanks for your support and help. And please feel free to ask if you have
> questions.
>
> Galina
>
>
> On Thu, Sep 10, 2020 at 9:35 PM Galina Kistanova 
> wrote:
>
>> 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 will upgrade the production bot.
>>
>> I will need some help with testing, and will be asking to move some of
>> the builders temporarily to the staging. LLVM buildbot is a piece of
>> critical infrastructure, so more eyes and hands in making sure it works
>> properly the better.
>>
>> I'll be posting updates and ETA of particular changes in this thread.
>>
>> Please feel free to ask if you have any questions or concerns.
>>
>> Thanks
>>
>> Galina
>>
>>
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Re: [Lldb-commits] Upcoming upgrade of LLVM buildbot

[Galina Kistanova via cfe-commits]

Thanks everyone for keeping your annotated builders in the staging area!
Much appreciated.

Please feel free to move all the green builders back to the production. It
has a new AnnotatedCommand now.

Thanks

Galina


On Thu, Oct 15, 2020 at 12:46 AM Vitaly Buka  wrote:

> Ok, I can switch them back to staging. However today's staging was
> frequently offline.
>
>
> On Wed, 14 Oct 2020 at 21:44, Galina Kistanova 
> wrote:
>
>> Thanks everyone!
>>
>> I would like to keep the bots in the staging till Friday. And if
>> everything is good, then apply the changes to the production and let you
>> move all the green bots back there.
>>
>> Thanks
>>
>> Galina
>>
>>
>> On Tue, Oct 13, 2020 at 10:43 PM Vitaly Buka 
>> wrote:
>>
>>> They do on staging.
>>> http://lab.llvm.org:8014/#/builders/sanitizer-windows
>>> http://lab.llvm.org:8014/#/builders/clang-x64-windows-msvc
>>>
>>> Galina, when do you plan to push this to the primary server?
>>> If it's a few days, I'd rather keep bots on staging to have colors.
>>>
>>>
>>>
>>> On Tue, 13 Oct 2020 at 11:11, Reid Kleckner  wrote:
>>>
 FWIW, I don't see any issues with my two bots that use buildbot
 annotated commands:
 http://lab.llvm.org:8011/#/builders/sanitizer-windows
 http://lab.llvm.org:8011/#/builders/clang-x64-windows-msvc
 The individual steps don't highlight as green or red, but that's OK for
 now.

 On Mon, Oct 12, 2020 at 7:19 PM Galina Kistanova 
 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 test it well before moving to the production build
> bot.
>
> For that we need all sanitizer + other bots which use the
> AnnotatedCommand directly or indirectly moved temporarily to the staging.
>
> Please let me know when that could be arranged.
>
> Thanks
>
> Galina
>
> On Mon, Oct 12, 2020 at 11:39 AM Reid Kleckner  wrote:
>
>> On Wed, Oct 7, 2020 at 4:32 PM Galina Kistanova via lldb-commits <
>> lldb-comm...@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 know if you have some spare time to work on porting
>>> AnnotatedCommand.
>>>
>>
>> That's unfortunate, it would've been good to know that earlier. I and
>> another team member have spent a fair amount of time porting things to 
>> use
>> more AnnotatedCommand steps, because it gives us the flexibility to test
>> steps locally and make changes to the steps without restarting the 
>> buildbot
>> master. IMO that is the Right Way to define steps: a script that you can
>> run locally on a machine that satisfies the OS and dep requirements of 
>> the
>> script.
>>
>> I am restarting the two bots that I am responsible for, and may need
>> some help debugging further issues soon. I'll let you know.
>>
>
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildbot will be restarted soon

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be restarted in the nearest hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Re: [Lldb-commits] Upcoming upgrade of LLVM buildbot

[Galina Kistanova via cfe-commits]

Thanks everyone!

I would like to keep the bots in the staging till Friday. And if everything
is good, then apply the changes to the production and let you move all the
green bots back there.

Thanks

Galina


On Tue, Oct 13, 2020 at 10:43 PM Vitaly Buka  wrote:

> They do on staging.
> http://lab.llvm.org:8014/#/builders/sanitizer-windows
> http://lab.llvm.org:8014/#/builders/clang-x64-windows-msvc
>
> Galina, when do you plan to push this to the primary server?
> If it's a few days, I'd rather keep bots on staging to have colors.
>
>
>
> On Tue, 13 Oct 2020 at 11:11, Reid Kleckner  wrote:
>
>> FWIW, I don't see any issues with my two bots that use buildbot annotated
>> commands:
>> http://lab.llvm.org:8011/#/builders/sanitizer-windows
>> http://lab.llvm.org:8011/#/builders/clang-x64-windows-msvc
>> The individual steps don't highlight as green or red, but that's OK for
>> now.
>>
>> On Mon, Oct 12, 2020 at 7:19 PM Galina Kistanova 
>> 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 test it well before moving to the production build bot.
>>>
>>> For that we need all sanitizer + other bots which use the
>>> AnnotatedCommand directly or indirectly moved temporarily to the staging.
>>>
>>> Please let me know when that could be arranged.
>>>
>>> Thanks
>>>
>>> Galina
>>>
>>> On Mon, Oct 12, 2020 at 11:39 AM Reid Kleckner  wrote:
>>>
 On Wed, Oct 7, 2020 at 4:32 PM Galina Kistanova via lldb-commits <
 lldb-comm...@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 know if you have some spare time to work on porting
> AnnotatedCommand.
>

 That's unfortunate, it would've been good to know that earlier. I and
 another team member have spent a fair amount of time porting things to use
 more AnnotatedCommand steps, because it gives us the flexibility to test
 steps locally and make changes to the steps without restarting the buildbot
 master. IMO that is the Right Way to define steps: a script that you can
 run locally on a machine that satisfies the OS and dep requirements of the
 script.

 I am restarting the two bots that I am responsible for, and may need
 some help debugging further issues soon. I'll let you know.

>>>
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildbot will be updated and restarted soon

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be updated and restarted in the nearest hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Re: [Lldb-commits] Upcoming upgrade of LLVM buildbot

[Galina Kistanova via cfe-commits]

Thanks, Vitaly!

Let's have them there for at least 24 hours, shall we?

Could you move sanitizer-buildbot1, sanitizer-buildbot3,
sanitizer-buildbot7 as well, please?

AnnotatedCommand on the staging has been tested functionally and is good.
My only concern at this point is how it would handle a heavy load, so the
more bots we will have on the staging the better.

If somebody else could move their AnnotatedCommand bots to the staging
area, that would be much appreciated.

Thanks

Galina

On Mon, Oct 12, 2020 at 9:45 PM Vitaly Buka  wrote:

> Looks like staging AnnotatedCommand fixed step statuses, so we can see
> which one is green.
> Please let me know when to switch bots back from the staging.
> Thank you!
>
> On Mon, 12 Oct 2020 at 21:38, Vitaly Buka  wrote:
>
>> 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 
>> 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 test it well before moving to the production build bot.
>>>
>>> For that we need all sanitizer + other bots which use the
>>> AnnotatedCommand directly or indirectly moved temporarily to the staging.
>>>
>>> Please let me know when that could be arranged.
>>>
>>> Thanks
>>>
>>> Galina
>>>
>>> On Mon, Oct 12, 2020 at 11:39 AM Reid Kleckner  wrote:
>>>
 On Wed, Oct 7, 2020 at 4:32 PM Galina Kistanova via lldb-commits <
 lldb-comm...@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 know if you have some spare time to work on porting
> AnnotatedCommand.
>

 That's unfortunate, it would've been good to know that earlier. I and
 another team member have spent a fair amount of time porting things to use
 more AnnotatedCommand steps, because it gives us the flexibility to test
 steps locally and make changes to the steps without restarting the buildbot
 master. IMO that is the Right Way to define steps: a script that you can
 run locally on a machine that satisfies the OS and dep requirements of the
 script.

 I am restarting the two bots that I am responsible for, and may need
 some help debugging further issues soon. I'll let you know.

>>>
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Re: [Lldb-commits] Upcoming upgrade of LLVM buildbot

[Galina Kistanova via cfe-commits]

We have a better version of AnnotatedCommand on the staging. It should be a
functional equivalent of the old one.
We need to stress test it well before moving to the production build bot.

For that we need all sanitizer + other bots which use the AnnotatedCommand
directly or indirectly moved temporarily to the staging.

Please let me know when that could be arranged.

Thanks

Galina

On Mon, Oct 12, 2020 at 11:39 AM Reid Kleckner  wrote:

> On Wed, Oct 7, 2020 at 4:32 PM Galina Kistanova via lldb-commits <
> lldb-comm...@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 know if you have some spare time to work on porting
>> AnnotatedCommand.
>>
>
> That's unfortunate, it would've been good to know that earlier. I and
> another team member have spent a fair amount of time porting things to use
> more AnnotatedCommand steps, because it gives us the flexibility to test
> steps locally and make changes to the steps without restarting the buildbot
> master. IMO that is the Right Way to define steps: a script that you can
> run locally on a machine that satisfies the OS and dep requirements of the
> script.
>
> I am restarting the two bots that I am responsible for, and may need some
> help debugging further issues soon. I'll let you know.
>
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildbot will be updated and restarted soon

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be updated and restarted in the nearest hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Re: [llvm-dev] [cfe-dev] Upcoming upgrade of LLVM buildbot

[Galina Kistanova via cfe-commits]

Hello Andrzej,

Please do not update your bots yet. I will explicitly ask later.

Feel free to move other reliably green bots of yours to the production
buildbot.

Thanks

Galina

On Fri, Oct 9, 2020 at 3:51 AM Andrzej Warzynski 
wrote:

> I switched one of our workers to the main Buildbot and everything seems
> fine #fingers-crossed. I guess that that was a temporary glitch?
>
> We haven't updated our local Buildbot installations - still on 0.8.5.
> Should we update?
>
> -Andrzej
>
> On 09/10/2020 00:44, Galina Kistanova wrote:
> > 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  > <mailto:paulat...@google.com>> wrote:
> >
> > Hey Andrzej,
> >
> > What are you seeing in your buildbot logs? Is it this error?
> > `twisted.spread.flavors.NoSuchMethod: No such method:
> > remote_getWorkerInfo`
> >
> > If so, you might want to try updating your buildbot worker.
> > I updated llvmlibc's to 2.8.4 and that seemed to solve the connection
> > problem:
> >
> https://github.com/llvm/llvm-project/commit/f60686f35cc89504f3411f49cf16a651a74be6eb
> >
> > Best,
> > Paula Askar
> >
> >
> > On Thu, Oct 8, 2020 at 5:43 AM Andrzej Warzynski via llvm-dev
> > mailto:llvm-...@lists.llvm.org>> wrote:
> >  >
> >  > 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 -
> > 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 know if you have some spare time to work on
> porting
> >  > > AnnotatedCommand.
> >      > >
> >  > > Thanks
> >  > >
> >  > > Galina
> >  > >
> >  > > On Wed, Oct 7, 2020 at 2:57 PM Vitaly Buka
> > mailto:vitalyb...@google.com>
> >  > > <mailto:vitalyb...@google.com <mailto:vitalyb...@google.com>>>
> > wrote:
> >  > >
> >  > > 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
> >  > >  > <mailto:cfe-commits@lists.llvm.org>
> > <mailto:cfe-commits@lists.llvm.org
> > <mailto:cfe-commits@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 version.
> >  > >
> >  > > If you are a bot owner, you do not need to do anything
> > at this
> >  > > point, unless I'll ask you to help.
> >  > > The buildbot will go down for a short period of time,
> > and then a
> >  > > new version will come up and will accept connections
> > from your bots.
> >  > >
> >  > > Please note that the new version has a bit different URL
> >  > > structure. You will need to update the bookmarks or
> > scripts if
> >  > > you have stored direct URLs to inside the buldbot.
> &

Re: [llvm-dev] [cfe-dev] Upcoming upgrade of LLVM buildbot

[Galina Kistanova via cfe-commits]

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  wrote:

> Hey Andrzej,
>
> What are you seeing in your buildbot logs? Is it this error?
> `twisted.spread.flavors.NoSuchMethod: No such method:
> remote_getWorkerInfo`
>
> If so, you might want to try updating your buildbot worker.
> I updated llvmlibc's to 2.8.4 and that seemed to solve the connection
> problem:
> https://github.com/llvm/llvm-project/commit/f60686f35cc89504f3411f49cf16a651a74be6eb
>
> Best,
> Paula Askar
>
>
> On Thu, Oct 8, 2020 at 5:43 AM Andrzej Warzynski via llvm-dev
>  wrote:
> >
> > 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 -
> 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 know if you have some spare time to work on porting
> > > AnnotatedCommand.
> > >
> > > Thanks
> > >
> > > Galina
> > >
> > > On Wed, Oct 7, 2020 at 2:57 PM Vitaly Buka  > > <mailto:vitalyb...@google.com>> wrote:
> > >
> > > 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
> > > mailto:cfe-commits@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 version.
> > >
> > > If you are a bot owner, you do not need to do anything at this
> > > point, unless I'll ask you to help.
> > > The buildbot will go down for a short period of time, and then
> a
> > > new version will come up and will accept connections from your
> bots.
> > >
> > > Please note that the new version has a bit different URL
> > > structure. You will need to update the bookmarks or scripts if
> > > you have stored direct URLs to inside the buldbot.
> > >
> > > We will be watching the production and staging bots and will be
> > > improving zorg for the next week or so.
> > >
> > > I will need your feedback about blame e-mails delivery, IRC
> > > reporting issues, and anything you could spot wrong with the
> new
> > > bot. I  hope the transition will go smoothly and we will handle
> > > issues quickly if any would come up.
> > >
> > > After production is good and we have about a week of running
> > > history, I'll ask the bot owners to upgrade buildbots on their
> > > side. Please do not upgrade your buildbots unless I'll ask you
> > > to. We are trying to limit a number of moving parts at this
> > > stage. We will start accepting change to zorg at this point.
> > > Please feel free to talk to me if you will have a special
> > > situation and if you would absolutely have to make changes.
> > >
> > > Thanks for your support and help. And please feel free to ask
> if
> > > you have questions.
> > >
> > > Galina
> > >
> > >
> > > On Thu, Sep 10, 2020 at 9:35 PM Galina Kistanova
> > > mailto:gkistan...@gmail.com>> wrote:
> > >
> > > 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 builde

Re: [cfe-dev] Upcoming upgrade of LLVM buildbot

[Galina Kistanova via cfe-commits]

Hello bot owners,

I see a lot of builders went down and not connecting back to the production
buildbot.

Could you check your bots to make sure they are up and running, please?
And report connectivity issues if any with quotes from the logs directly to
me.

Thanks

Galina


On Thu, Oct 8, 2020 at 2:43 AM Andrzej Warzynski 
wrote:

> 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 -
> 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 know if you have some spare time to work on porting
> > AnnotatedCommand.
> >
> > Thanks
> >
> > Galina
> >
> > On Wed, Oct 7, 2020 at 2:57 PM Vitaly Buka  > <mailto:vitalyb...@google.com>> wrote:
> >
> >     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
> > mailto:cfe-commits@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 version.
> >
> > If you are a bot owner, you do not need to do anything at this
> > point, unless I'll ask you to help.
> > The buildbot will go down for a short period of time, and then a
> > new version will come up and will accept connections from your
> bots.
> >
> > Please note that the new version has a bit different URL
> > structure. You will need to update the bookmarks or scripts if
> > you have stored direct URLs to inside the buldbot.
> >
> > We will be watching the production and staging bots and will be
> > improving zorg for the next week or so.
> >
> > I will need your feedback about blame e-mails delivery, IRC
> > reporting issues, and anything you could spot wrong with the new
> > bot. I  hope the transition will go smoothly and we will handle
> > issues quickly if any would come up.
> >
> > After production is good and we have about a week of running
> > history, I'll ask the bot owners to upgrade buildbots on their
> > side. Please do not upgrade your buildbots unless I'll ask you
> > to. We are trying to limit a number of moving parts at this
> > stage. We will start accepting change to zorg at this point.
> > Please feel free to talk to me if you will have a special
> > situation and if you would absolutely have to make changes.
> >
> > Thanks for your support and help. And please feel free to ask if
> > you have questions.
> >
> > Galina
> >
> >
> > On Thu, Sep 10, 2020 at 9:35 PM Galina Kistanova
> > mailto:gkistan...@gmail.com>> wrote:
> >
> > 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 will
> > upgrade the production bot.
> >
> > I will need some help with testing, and will be asking to
> > move some of the builders temporarily to the staging. LLVM
> > buildbot is a piece of critical infrastructure, so more eyes
> > and hands in making sure it works properly the better.
> >
> > I'll be posting updates and ETA of particular changes in
> > this thread.
> >
> > Please feel free to ask if you have any questions 

Re: Upcoming upgrade of LLVM buildbot

[Galina Kistanova via cfe-commits]

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 know if you have some spare time to work on porting
AnnotatedCommand.

Thanks

Galina

On Wed, Oct 7, 2020 at 2:57 PM Vitaly Buka  wrote:

> 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@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 version.
>>
>> If you are a bot owner, you do not need to do anything at this point,
>> unless I'll ask you to help.
>> The buildbot will go down for a short period of time, and then a new
>> version will come up and will accept connections from your bots.
>>
>> Please note that the new version has a bit different URL structure. You
>> will need to update the bookmarks or scripts if you have stored direct URLs
>> to inside the buldbot.
>>
>> We will be watching the production and staging bots and will be improving
>> zorg for the next week or so.
>>
>> I will need your feedback about blame e-mails delivery, IRC reporting
>> issues, and anything you could spot wrong with the new bot. I  hope the
>> transition will go smoothly and we will handle issues quickly if any would
>> come up.
>>
>> After production is good and we have about a week of running history,
>> I'll ask the bot owners to upgrade buildbots on their side. Please do
>> not upgrade your buildbots unless I'll ask you to. We are trying to
>> limit a number of moving parts at this stage. We will start accepting
>> change to zorg at this point. Please feel free to talk to me if you will
>> have a special situation and if you would absolutely have to make changes.
>>
>> Thanks for your support and help. And please feel free to ask if you have
>> questions.
>>
>> Galina
>>
>>
>> On Thu, Sep 10, 2020 at 9:35 PM Galina Kistanova 
>> wrote:
>>
>>> 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 will upgrade the production bot.
>>>
>>> I will need some help with testing, and will be asking to move some of
>>> the builders temporarily to the staging. LLVM buildbot is a piece of
>>> critical infrastructure, so more eyes and hands in making sure it works
>>> properly the better.
>>>
>>> I'll be posting updates and ETA of particular changes in this thread.
>>>
>>> Please feel free to ask if you have any questions or concerns.
>>>
>>> Thanks
>>>
>>> Galina
>>>
>>> ___
>> cfe-commits mailing list
>> cfe-commits@lists.llvm.org
>> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
>>
>
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Re: Upcoming upgrade of LLVM buildbot

[Galina Kistanova via cfe-commits]

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
version.

If you are a bot owner, you do not need to do anything at this point,
unless I'll ask you to help.
The buildbot will go down for a short period of time, and then a new
version will come up and will accept connections from your bots.

Please note that the new version has a bit different URL structure. You
will need to update the bookmarks or scripts if you have stored direct URLs
to inside the buldbot.

We will be watching the production and staging bots and will be improving
zorg for the next week or so.

I will need your feedback about blame e-mails delivery, IRC reporting
issues, and anything you could spot wrong with the new bot. I  hope the
transition will go smoothly and we will handle issues quickly if any would
come up.

After production is good and we have about a week of running history, I'll
ask the bot owners to upgrade buildbots on their side. Please do not upgrade
your buildbots unless I'll ask you to. We are trying to limit a number of
moving parts at this stage. We will start accepting change to zorg at this
point. Please feel free to talk to me if you will have a special situation
and if you would absolutely have to make changes.

Thanks for your support and help. And please feel free to ask if you have
questions.

Galina


On Thu, Sep 10, 2020 at 9:35 PM Galina Kistanova 
wrote:

> 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 will upgrade the production bot.
>
> I will need some help with testing, and will be asking to move some of the
> builders temporarily to the staging. LLVM buildbot is a piece of critical
> infrastructure, so more eyes and hands in making sure it works properly the
> better.
>
> I'll be posting updates and ETA of particular changes in this thread.
>
> Please feel free to ask if you have any questions or concerns.
>
> Thanks
>
> Galina
>
>
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Buildbot numbers for the week of 09/20/2020 - 09/26/2020

[Galina Kistanova via cfe-commits]

Hello everyone,

Below are some buildbot numbers for the week of 09/20/2020 - 09/26/2020.

Please see the same data in attached csv files:

The longest time each builder was red during the week;
"Status change ratio" by active builder (percent of builds that changed the
builder status from green to red or from red to green);
Count of commits by project;
Number of completed builds, failed builds and average build time for
successful builds per active builder;
Average waiting time for a revision to get build result per active builder
(response time).

Thanks

Galina


The longest time each builder was red during the week:
   buildername   |  was_red
-+--
 clang-sphinx-docs   | 124:15:45
 llvm-clang-x86_64-expensive-checks-debian   | 105:33:42
 llvm-clang-x86_64-expensive-checks-ubuntu   | 105:29:51
 clang-ppc64be-linux-multistage  | 43:30:49
 sanitizer-ppc64be-linux | 43:01:03
 clang-ppc64be-linux | 42:19:23
 clang-ppc64be-linux-lnt | 41:53:03
 sanitizer-ppc64le-linux | 35:34:26
 clang-ppc64le-linux-multistage  | 35:21:39
 clang-ppc64le-linux-lnt | 35:14:20
 clang-cmake-x86_64-avx2-linux   | 17:47:28
 clang-cmake-x86_64-sde-avx512-linux | 17:33:29
 clang-cmake-aarch64-full| 16:30:59
 llvm-clang-x86_64-expensive-checks-win  | 14:45:12
 clang-cmake-aarch64-lld | 14:36:40
 clang-ppc64le-linux | 14:14:15
 lldb-x86_64-debian  | 13:56:45
 clang-cmake-aarch64-quick   | 13:33:25
 lldb-arm-ubuntu | 13:22:29
 lldb-aarch64-ubuntu | 13:18:19
 lldb-x64-windows-ninja  | 13:11:29
 clang-cmake-aarch64-global-isel | 12:55:36
 sanitizer-x86_64-linux-fast | 12:41:08
 llvm-clang-win-x-armv7l | 12:05:49
 sanitizer-x86_64-linux-bootstrap-ubsan  | 11:57:22
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx17  | 11:17:54
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx2a  | 11:15:06
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx11  | 11:14:43
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx14  | 11:08:58
 libcxx-libcxxabi-x86_64-linux-ubuntu-gcc5-cxx11 | 11:08:40
 libcxx-libcxxabi-x86_64-linux-ubuntu-ubsan  | 11:07:04
 libcxx-libcxxabi-libunwind-x86_64-linux-ubuntu  | 11:07:00
 libcxx-libcxxabi-x86_64-linux-ubuntu-tsan   | 11:01:24
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx03  | 10:59:52
 llvm-clang-win-x-aarch64| 10:45:04
 clang-x64-windows-msvc  | 08:19:50
 clang-cmake-armv8-lld   | 06:59:44
 lld-x86_64-win  | 06:55:56
 fuchsia-x86_64-linux| 06:23:14
 clang-with-lto-ubuntu   | 05:15:49
 clang-with-thin-lto-ubuntu  | 05:03:01
 sanitizer-x86_64-linux-bootstrap| 04:43:27
 clang-s390x-linux-multistage| 04:16:54
 sanitizer-x86_64-linux  | 03:22:20
 aosp-O3-polly-before-vectorizer-unprofitable| 03:17:15
 ppc64le-lld-multistage-test | 03:13:34
 flang-aarch64-ubuntu| 03:13:09
 lld-x86_64-freebsd  | 02:59:56
 llvm-clang-x86_64-win-fast  | 02:56:30
 sanitizer-x86_64-linux-bootstrap-msan   | 02:54:59
 lld-perf-testsuite  | 02:46:56
 lld-x86_64-darwin   | 02:41:28
 clang-ppc64le-rhel  | 02:24:21
 llvm-avr-linux  | 02:18:21
 lld-x86_64-ubuntu-fast  | 02:15:35
 sanitizer-x86_64-linux-android  | 02:11:03
 clang-cmake-armv7-global-isel   | 02:07:50
 clang-cmake-armv7-quick | 02:05:38
 clang-s390x-linux-lnt   | 02:05:23
 llvm-sphinx-docs| 02:03:31
 mlir-nvidia | 02:03:22
 polly-x86_64-linux-test-suite   | 01:56:17
 

Buildbot numbers for the week of 09/13/2020 - 09/19/2020

[Galina Kistanova via cfe-commits]

Hello everyone,

Below are some buildbot numbers for the week of 09/13/2020 - 09/19/2020.

Please see the same data in attached csv files:

The longest time each builder was red during the week;
"Status change ratio" by active builder (percent of builds that changed the
builder status from green to red or from red to green);
Count of commits by project;
Number of completed builds, failed builds and average build time for
successful builds per active builder;
Average waiting time for a revision to get build result per active builder
(response time).

Thanks

Galina


The longest time each builder was red during the week:
   buildername   | was_red
-+-
 ppc64le-lld-multistage-test | 82:03:54
 clang-with-lto-ubuntu   | 60:31:33
 lld-x86_64-darwin   | 60:30:44
 clang-with-thin-lto-ubuntu  | 57:42:47
 llvm-clang-x86_64-expensive-checks-ubuntu   | 57:06:41
 clang-s390x-linux-lnt   | 55:02:40
 lld-x86_64-win  | 53:15:05
 llvm-clang-x86_64-expensive-checks-win  | 52:47:17
 lld-perf-testsuite  | 48:59:59
 clang-x86_64-linux-abi-test | 48:54:27
 llvm-sphinx-docs| 46:32:42
 llvm-clang-win-x-aarch64| 39:54:36
 libcxx-libcxxabi-libunwind-armv7-linux-noexceptions | 24:18:22
 sanitizer-x86_64-linux-fuzzer   | 22:37:35
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx11  | 21:50:45
 clang-native-arm-lnt-perf   | 19:36:29
 aosp-O3-polly-before-vectorizer-unprofitable| 19:21:24
 lld-x86_64-freebsd  | 19:15:49
 llvm-clang-win-x-armv7l | 18:33:30
 clang-x64-windows-msvc  | 15:25:00
 sanitizer-x86_64-linux  | 13:14:10
 sanitizer-x86_64-linux-autoconf | 13:07:55
 llvm-avr-linux  | 13:01:33
 clang-cmake-aarch64-lld | 12:28:41
 sanitizer-windows   | 07:41:33
 clang-s390x-linux-multistage| 07:27:51
 lldb-x86_64-debian  | 07:10:32
 clang-cmake-aarch64-global-isel | 07:06:34
 clang-ppc64le-linux | 06:51:00
 lldb-arm-ubuntu | 06:45:42
 clang-cmake-aarch64-quick   | 06:45:03
 lldb-x64-windows-ninja  | 06:43:36
 lldb-aarch64-ubuntu | 06:41:37
 fuchsia-x86_64-linux| 06:40:21
 clang-s390x-linux   | 06:21:40
 clang-cmake-aarch64-full| 06:09:39
 libcxx-libcxxabi-libunwind-aarch64-linux| 05:30:21
 libcxx-libcxxabi-libunwind-armv8-linux  | 05:22:13
 ppc64le-mlir-rhel-clang | 05:01:37
 sanitizer-ppc64be-linux | 04:34:08
 sanitizer-x86_64-linux-fast | 04:17:11
 libcxx-libcxxabi-x86_64-linux-ubuntu-ubsan  | 04:16:27
 libcxx-libcxxabi-x86_64-linux-ubuntu-gcc-tot-latest-std | 04:09:28
 clang-ppc64le-rhel  | 04:06:29
 libcxx-libcxxabi-x86_64-linux-ubuntu-tsan   | 04:01:42
 lld-x86_64-ubuntu-fast  | 03:55:04
 clang-ppc64le-linux-multistage  | 03:49:18
 clang-cmake-armv8-lld   | 03:47:55
 sanitizer-x86_64-linux-bootstrap| 03:40:40
 polly-x86_64-linux  | 03:25:45
 sanitizer-x86_64-linux-bootstrap-msan   | 03:23:50
 sanitizer-x86_64-linux-bootstrap-ubsan  | 03:13:02
 clang-ppc64be-linux-multistage  | 03:10:43
 llvm-clang-x86_64-expensive-checks-debian   | 03:00:04
 clang-x86_64-debian-new-pass-manager-fast   | 02:54:21
 clang-ppc64le-linux-lnt | 02:50:01
 clang-x86_64-debian-fast| 02:45:46
 libcxx-libcxxabi-libunwind-x86_64-linux-ubuntu  | 02:43:57
 clang-cmake-armv7-lnt   | 02:36:19
 polly-x86_64-linux-test-suite   | 02:34:38
 flang-aarch64-ubuntu| 02:33:55
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx2a  | 02:28:46
 

Buildbot numbers for the week of 09/27/2020 - 10/03/2020

[Galina Kistanova via cfe-commits]

Hello everyone,

Below are some buildbot numbers for the last week of 09/27/2020 -
10/03/2020.

Please see the same data in attached csv files:

The longest time each builder was red during the week;
"Status change ratio" by active builder (percent of builds that changed the
builder status from green to red or from red to green);
Count of commits by project;
Number of completed builds, failed builds and average build time for
successful builds per active builder;
Average waiting time for a revision to get build result per active builder
(response time).

Thanks

Galina


The longest time each builder was red during the week:
   buildername   |  was_red
-+--
 clang-x64-windows-msvc  | 109:55:08
 clang-ppc64le-rhel  | 94:15:16
 libcxx-libcxxabi-x86_64-linux-ubuntu-gcc5-cxx11 | 76:58:22
 sanitizer-x86_64-linux  | 70:38:24
 clang-cmake-aarch64-lld | 60:12:19
 clang-cmake-aarch64-full| 59:32:56
 clang-ppc64le-linux | 58:54:05
 clang-cmake-aarch64-global-isel | 56:45:56
 clang-cmake-aarch64-quick   | 56:06:05
 lldb-x86_64-debian  | 53:36:26
 sanitizer-x86_64-linux-bootstrap| 25:41:38
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx11  | 20:41:34
 sanitizer-x86_64-linux-fast | 17:47:55
 clang-s390x-linux-multistage| 15:48:46
 clang-s390x-linux-lnt   | 12:37:42
 clang-sphinx-docs   | 12:20:25
 clang-ppc64be-linux-multistage  | 10:35:38
 clang-s390x-linux   | 10:28:52
 libcxx-libcxxabi-x86_64-linux-ubuntu-msan   | 10:27:20
 sanitizer-ppc64be-linux | 10:19:43
 clang-ppc64be-linux-lnt | 09:47:16
 lldb-x64-windows-ninja  | 09:32:47
 clang-cmake-armv8-lld   | 09:23:57
 clang-ppc64be-linux | 09:22:57
 aosp-O3-polly-before-vectorizer-unprofitable| 09:22:14
 sanitizer-x86_64-linux-bootstrap-ubsan  | 08:51:45
 sanitizer-x86_64-linux-bootstrap-msan   | 08:46:44
 sanitizer-ppc64le-linux | 08:39:28
 clang-ppc64le-linux-multistage  | 08:38:27
 sanitizer-x86_64-linux-autoconf | 08:37:51
 llvm-avr-linux  | 08:35:54
 sanitizer-windows   | 08:20:07
 sanitizer-x86_64-linux-android  | 08:15:19
 clang-with-lto-ubuntu   | 07:03:20
 libcxx-libcxxabi-x86_64-linux-ubuntu-asan   | 06:57:05
 lldb-aarch64-ubuntu | 05:59:27
 clang-with-thin-lto-ubuntu  | 03:56:21
 sanitizer-x86_64-linux-fuzzer   | 03:18:14
 lld-x86_64-win  | 03:04:03
 clang-cmake-x86_64-avx2-linux   | 02:57:58
 fuchsia-x86_64-linux| 02:39:46
 clang-cmake-armv7-quick | 02:38:38
 llvm-clang-win-x-aarch64| 02:35:32
 clang-ppc64le-linux-lnt | 02:34:53
 clang-cmake-x86_64-sde-avx512-linux | 02:33:37
 clang-x86_64-debian-new-pass-manager-fast   | 02:27:43
 clang-x86_64-debian-fast| 02:26:51
 ppc64le-lld-multistage-test | 02:24:12
 flang-aarch64-ubuntu| 02:07:17
 clang-cmake-armv7-global-isel   | 02:05:12
 clang-x86_64-linux-abi-test | 01:57:57
 flang-aarch64-ubuntu-gcc10  | 01:56:14
 llvm-clang-win-x-armv7l | 01:45:47
 lldb-arm-ubuntu | 01:33:26
 libcxx-libcxxabi-libunwind-x86_64-linux-ubuntu  | 01:32:07
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx2a  | 01:30:16
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx17  | 01:29:12
 libcxx-libcxxabi-x86_64-linux-ubuntu-tsan   | 01:29:03
 libcxx-libcxxabi-x86_64-linux-ubuntu-ubsan  | 01:27:21
 openmp-clang-x86_64-linux-debian| 01:21:13
 clang-cmake-armv7-lnt   | 01:10:18
 publish-sphinx-docs | 01:00:51
 openmp-gcc-x86_64-linux-debian  | 00:55:53
 lld-x86_64-ubuntu-fast  | 00:53:09
 mlir-nvidia | 00:42:20
 libc-x86_64-debian-dbg  | 00:36:00
 lld-x86_64-darwin   | 00:35:34
 lld-x86_64-freebsd  | 00:32:55
 llvm-clang-x86_64-expensive-checks-ubuntu   | 00:23:25
(69 rows)


"Status change ratio" by active builder (percent of builds that changed the
builder status 

Re: Upcoming upgrade of LLVM buildbot

[Galina Kistanova via cfe-commits]

Hello everyone,

Starting tomorrow we will be upgrading the staging and production LLVM
build bot.

To make the transition smooth we would not accept any change to zorg from
tomorrow 11:00 AM PDT till the production bot is up and running the new
version. Please feel free to talk to me if you will have a special
situation and if you would absolutely have to make changes. Thanks for your
patience and understanding.

If you are a bot owner, you do not need to do anything at this point,
unless I'll ask you to help.

Here is the plan.

* Tomorrow, on September 30th, 2020, at 11:00 AM PDT we will upgrade the
staging build bot to buildbot v2.8.4.

If you are an owner of one of the staged builders, you would not need to do
anything. The staging will go down for a short period of time, and then a
new version will come up and will accept connections from your bots.

We will be watching the staging and will be improving zorg for the next
week or so. Meaning that staging will be restarted more often than before,
and restarts will be done without further notices.

* Once the staging is reliable you may want to move your bot from
production to staging to make sure it will work as expected after the
upgrade. I will send a note when this could be done.

* After staging is good and we have about a week of running history, we
will upgrade the production bot. I will send a separate announcement for
this closer to the date.

Once the production is up and running, I will need your feedback about
blame e-mails delivery, IRC reporting issues, and anything you could spot
wrong with the new bot. I  hope the transition will go smoothly and we will
handle issues quickly if any would come up.

* After production is good and we have about a week of running history,
I'll ask the bot owners to upgrade buildbots on their side. Please do not
upgrade your buildbots unless I'll ask you to. We are trying to limit a
number of moving parts at this stage.

Thanks for your support and help. And please feel free to ask if you have
questions.

Galina


On Thu, Sep 10, 2020 at 9:35 PM Galina Kistanova 
wrote:

> 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 will upgrade the production bot.
>
> I will need some help with testing, and will be asking to move some of the
> builders temporarily to the staging. LLVM buildbot is a piece of critical
> infrastructure, so more eyes and hands in making sure it works properly the
> better.
>
> I'll be posting updates and ETA of particular changes in this thread.
>
> Please feel free to ask if you have any questions or concerns.
>
> Thanks
>
> Galina
>
>
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be updated and restarted tonight

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be updated and restarted after 6PM PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Buildbot numbers for the week of 09/06/2020 - 09/12/2020

[Galina Kistanova via cfe-commits]

Hello everyone,

Below are some buildbot numbers for the last week of 09/06/2020 -
09/12/2020.

Please see the same data in attached csv files:

The longest time each builder was red during the week;
"Status change ratio" by active builder (percent of builds that changed the
builder status from green to red or from red to green);
Count of commits by project;
Number of completed builds, failed builds and average build time for
successful builds per active builder;
Average waiting time for a revision to get build result per active builder
(response time).

Thanks

Galina


The longest time each builder was red during the week:
buildername|  was_red
---+--
 clang-s390x-linux-lnt | 105:54:48
 lld-x86_64-freebsd| 84:13:30
 clang-tools-sphinx-docs   | 49:58:55
 sanitizer-x86_64-linux| 34:41:03
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx17| 30:50:42
 clang-cmake-aarch64-full  | 26:07:12
 clang-ppc64be-linux-lnt   | 20:57:03
 clang-ppc64be-linux   | 20:55:24
 clang-s390x-linux | 20:25:08
 clang-ppc64be-linux-multistage| 19:24:58
 clang-s390x-linux-multistage  | 18:05:21
 llvm-clang-x86_64-expensive-checks-win| 13:12:42
 llvm-avr-linux| 13:07:03
 clang-cmake-aarch64-lld   | 12:52:16
 mlir-windows  | 12:14:01
 mlir-nvidia   | 12:05:48
 clang-ppc64le-linux   | 10:41:12
 clang-with-thin-lto-ubuntu| 07:20:19
 clang-with-lto-ubuntu | 07:13:38
 clang-x64-windows-msvc| 07:13:18
 sanitizer-x86_64-linux-bootstrap  | 06:36:15
 sanitizer-x86_64-linux-bootstrap-msan | 06:28:10
 sanitizer-x86_64-linux-fast   | 06:17:07
 libcxx-libcxxabi-libunwind-aarch64-linux  | 06:00:20
 libcxx-libcxxabi-libunwind-armv8-linux| 05:55:48
 clang-ppc64le-rhel| 05:51:52
 clang-ppc64le-linux-multistage| 05:44:41
 sanitizer-x86_64-linux-bootstrap-ubsan| 05:41:50
 ppc64le-lld-multistage-test   | 05:38:28
 clang-ppc64le-linux-lnt   | 05:35:50
 llvm-clang-x86_64-expensive-checks-debian | 05:20:11
 clang-x86_64-debian-new-pass-manager-fast | 05:20:03
 clang-x86_64-debian-fast  | 05:15:03
 lld-x86_64-darwin | 05:08:21
 lld-x86_64-win| 05:02:22
 llvm-clang-x86_64-expensive-checks-ubuntu | 05:01:00
 lld-x86_64-ubuntu-fast| 05:00:58
 sanitizer-ppc64be-linux   | 04:02:37
 sanitizer-ppc64le-linux   | 03:36:42
 clang-cmake-armv8-lld | 02:52:25
 polly-x86_64-linux| 02:38:19
 llvm-clang-win-x-aarch64  | 02:32:16
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx03| 02:16:28
 libcxx-libcxxabi-x86_64-linux-debian-noexceptions | 02:11:58
 libcxx-libcxxabi-libunwind-x86_64-linux-debian| 02:11:07
 libcxx-libcxxabi-x86_64-linux-debian  | 02:09:30
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx14| 02:08:30
 sanitizer-x86_64-linux-android| 02:08:01
 lldb-x64-windows-ninja| 01:55:08
 llvm-clang-win-x-armv7l   | 01:43:55
 fuchsia-x86_64-linux  | 01:34:13
 flang-aarch64-ubuntu  | 01:24:17
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx11| 01:22:45
 clang-x86_64-linux-abi-test   | 01:16:36
 clang-cmake-x86_64-avx2-linux | 01:14:01
 sanitizer-x86_64-linux-autoconf   | 01:12:34
 sanitizer-windows | 01:10:35
 openmp-clang-x86_64-linux-debian  | 01:10:28
 sanitizer-x86_64-linux-fuzzer | 01:07:52
 clang-cmake-armv7-global-isel | 01:06:25
 openmp-gcc-x86_64-linux-debian| 01:00:04
 llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast  | 00:52:45
 lldb-x86_64-debian| 00:51:13
 clang-cmake-armv7-quick   | 00:50:41
 lld-perf-testsuite| 00:49:27
 libc-x86_64-debian-dbg| 00:48:48
 lldb-arm-ubuntu   | 00:45:59
 polly-x86_64-linux-test-suite | 00:45:57
 

Buildbot numbers for the week of 08/30/2020 - 09/5/2020

[Galina Kistanova via cfe-commits]

Hello everyone,

Below are some buildbot numbers for the week of 08/30/2020 - 09/5/2020.

Please see the same data in attached csv files:

The longest time each builder was red during the week;
"Status change ratio" by active builder (percent of builds that changed the
builder status from green to red or from red to green);
Count of commits by project;
Number of completed builds, failed builds and average build time for
successful builds per active builder;
Average waiting time for a revision to get build result per active builder
(response time).

Thanks

Galina


The longest time each builder was red during the week:
   buildername   |  was_red
-+--
 flang-aarch64-ubuntu| 150:20:56
 lldb-x64-windows-ninja  | 51:58:36
 clang-ppc64le-rhel  | 33:00:42
 llvm-clang-x86_64-expensive-checks-ubuntu   | 24:36:49
 llvm-clang-x86_64-expensive-checks-debian   | 23:56:22
 llvm-clang-x86_64-expensive-checks-win  | 23:54:16
 libcxx-libcxxabi-x86_64-linux-ubuntu-gcc-tot-latest-std | 19:49:54
 sanitizer-windows   | 17:56:04
 sanitizer-ppc64le-linux | 17:55:56
 clang-ppc64le-linux | 14:03:57
 clang-cmake-aarch64-lld | 13:41:39
 clang-cmake-armv8-lld   | 10:37:59
 clang-with-lto-ubuntu   | 07:05:50
 clang-s390x-linux-multistage| 06:52:21
 sanitizer-x86_64-linux-bootstrap| 06:47:11
 polly-arm-linux | 06:44:19
 clang-with-thin-lto-ubuntu  | 06:05:34
 sanitizer-x86_64-linux-fast | 05:52:51
 sanitizer-x86_64-linux-bootstrap-msan   | 05:45:06
 clang-x64-windows-msvc  | 05:15:53
 llvm-clang-win-x-armv7l | 05:08:12
 sanitizer-x86_64-linux  | 04:52:00
 ppc64le-lld-multistage-test | 04:24:20
 clang-ppc64le-linux-multistage  | 04:24:10
 clang-ppc64le-linux-lnt | 04:03:43
 clang-cmake-aarch64-full| 03:49:59
 lld-x86_64-win  | 03:37:08
 clang-cmake-x86_64-sde-avx512-linux | 03:36:53
 sanitizer-x86_64-linux-bootstrap-ubsan  | 03:22:34
 aosp-O3-polly-before-vectorizer-unprofitable| 03:11:04
 clang-cmake-x86_64-avx2-linux   | 02:59:40
 libc-x86_64-debian-dbg  | 02:54:26
 openmp-clang-x86_64-linux-debian| 02:49:28
 fuchsia-x86_64-linux| 02:49:14
 clang-ppc64be-linux-multistage  | 02:45:19
 llvm-clang-win-x-aarch64| 02:40:36
 llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast  | 02:39:32
 lldb-x86_64-debian  | 02:30:50
 llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast| 02:18:27
 clang-cmake-armv7-global-isel   | 02:07:55
 llvm-avr-linux  | 02:00:44
 mlir-nvidia | 01:56:44
 ppc64le-mlir-rhel-clang | 01:56:21
 openmp-gcc-x86_64-linux-debian  | 01:53:31
 sanitizer-ppc64be-linux | 01:43:00
 lldb-aarch64-ubuntu | 01:41:39
 lldb-arm-ubuntu | 01:41:13
 clang-cmake-aarch64-quick   | 01:28:10
 clang-s390x-linux   | 01:12:02
 clang-ppc64be-linux-lnt | 01:07:31
 clang-ppc64be-linux | 01:00:28
 sanitizer-x86_64-linux-android  | 00:53:59
 clang-cmake-armv7-quick | 00:45:36
 polly-x86_64-linux-test-suite   | 00:42:50
 clang-x86_64-debian-new-pass-manager-fast   | 00:37:26
 lld-x86_64-darwin   | 00:35:04
 clang-x86_64-debian-fast| 00:34:13
 sanitizer-x86_64-linux-fuzzer   | 00:34:01
 lld-x86_64-ubuntu-fast  | 00:33:28
 lld-perf-testsuite  | 00:23:27
 sanitizer-x86_64-linux-autoconf | 00:21:54
 libc-x86_64-debian  | 00:21:27
 

Upcoming upgrade of LLVM buildbot

[Galina Kistanova via cfe-commits]

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 will upgrade the production bot.

I will need some help with testing, and will be asking to move some of the
builders temporarily to the staging. LLVM buildbot is a piece of critical
infrastructure, so more eyes and hands in making sure it works properly the
better.

I'll be posting updates and ETA of particular changes in this thread.

Please feel free to ask if you have any questions or concerns.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be updated and restarted soon

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be updated and restarted in an hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be updated and restarted soon

[Galina Kistanova via cfe-commits]

Hello everyone,

LLVM buildmaster will be updated and restarted in the nearest hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be updated and restarted tonight

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be updated and restarted after 6PM PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Buildbot numbers for the week of 08/16/2020 - 08/22/2020

[Galina Kistanova via cfe-commits]

Hello everyone,

Below are some buildbot numbers for the week of 08/16/2020 - 08/22/2020.

Please see the same data in attached csv files:

The longest time each builder was red during the week;
"Status change ratio" by active builder (percent of builds that changed the
builder status from green to red or from red to green);
Count of commits by project;
Number of completed builds, failed builds and average build time for
successful builds per active builder;
Average waiting time for a revision to get build result per active builder
(response time).

Thanks

Galina


The longest time each builder was red during the week:
   buildername|  was_red
--+--
 clang-s390x-linux-lnt| 149:47:46
 lld-sphinx-docs  | 124:29:22
 clang-sphinx-docs| 116:43:12
 sanitizer-x86_64-linux   | 73:40:40
 sanitizer-x86_64-linux-bootstrap-msan| 69:11:29
 sanitizer-x86_64-linux-fast  | 69:10:31
 lld-perf-testsuite   | 68:10:07
 clang-ppc64le-rhel   | 43:05:38
 llvm-clang-x86_64-expensive-checks-debian| 39:32:59
 clang-x86_64-debian-fast | 39:01:38
 openmp-clang-x86_64-linux-debian | 38:57:16
 clang-x86_64-debian-new-pass-manager-fast| 38:53:22
 openmp-gcc-x86_64-linux-debian   | 38:50:29
 clang-cmake-armv8-lld| 30:25:52
 clang-cmake-armv7-quick  | 30:05:43
 clang-cmake-armv7-global-isel| 29:58:00
 sanitizer-windows| 26:28:36
 clang-cmake-x86_64-sde-avx512-linux  | 23:20:24
 llvm-clang-win-x-armv7l  | 22:40:23
 llvm-avr-linux   | 20:12:22
 clang-ppc64le-linux-multistage   | 19:55:11
 flang-aarch64-ubuntu | 15:46:02
 ppc64le-lld-multistage-test  | 12:38:26
 llvm-clang-x86_64-expensive-checks-ubuntu| 12:22:11
 lldb-x64-windows-ninja   | 10:44:21
 clang-ppc64le-linux  | 10:34:20
 clang-s390x-linux-multistage | 10:00:50
 clang-x64-windows-msvc   | 09:13:51
 lld-x86_64-win   | 08:20:20
 lld-x86_64-darwin| 08:08:16
 llvm-clang-x86_64-expensive-checks-win   | 07:54:01
 lldb-arm-ubuntu  | 06:18:13
 lldb-x86_64-debian   | 06:04:32
 lldb-aarch64-ubuntu  | 05:59:54
 llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast | 05:55:01
 sanitizer-x86_64-linux-bootstrap | 05:25:08
 clang-s390x-linux| 05:23:25
 sanitizer-x86_64-linux-bootstrap-ubsan   | 05:02:19
 clang-ppc64be-linux-multistage   | 04:55:54
 lld-x86_64-ubuntu-fast   | 04:55:15
 clang-with-thin-lto-ubuntu   | 04:52:18
 clang-ppc64be-linux-lnt  | 04:45:43
 clang-ppc64be-linux  | 04:39:18
 llvm-clang-win-x-aarch64 | 04:38:02
 fuchsia-x86_64-linux | 04:34:42
 clang-cmake-aarch64-full | 04:28:00
 clang-cmake-aarch64-quick| 04:26:14
 clang-cmake-x86_64-avx2-linux| 04:23:18
 clang-cmake-aarch64-global-isel  | 04:19:36
 llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast   | 04:16:34
 llvm-clang-x86_64-win-fast   | 04:02:45
 mlir-windows | 04:00:18
 mlir-nvidia  | 03:04:19
 clang-ppc64le-linux-lnt  | 02:42:56
 libc-x86_64-debian-dbg   | 01:32:07
 clang-cmake-aarch64-lld  | 01:23:04
 llvm-sphinx-docs | 01:12:31
 clang-cmake-armv7-lnt| 01:04:11
 sanitizer-x86_64-linux-fuzzer| 00:48:19
 lldb-sphinx-docs | 00:46:38
 libc-x86_64-debian-dbg-asan  | 00:42:39
 clang-x86_64-linux-abi-test  | 00:37:19
 libc-x86_64-debian   | 00:34:29
 polly-x86_64-linux-test-suite| 00:34:03
 polly-x86_64-linux   | 00:32:25
 clang-aarch64-linux-build-cache  | 00:29:43
 sanitizer-x86_64-linux-android   | 00:28:09
 clang-armv7-linux-build-cache| 00:21:27
(68 rows)


"Status change ratio" by active builder (percent of builds that changed the
builder 

Buildbot numbers for the week of 08/23/2020 - 08/29/2020

[Galina Kistanova via cfe-commits]

Hello everyone,

Below are some buildbot numbers for the last week of 08/23/2020 -
08/29/2020.

Please see the same data in attached csv files:

The longest time each builder was red during the week;
"Status change ratio" by active builder (percent of builds that changed the
builder status from green to red or from red to green);
Count of commits by project;
Number of completed builds, failed builds and average build time for
successful builds per active builder;
Average waiting time for a revision to get build result per active builder
(response time).

Thanks

Galina


The longest time each builder was red during the week:
  buildername  |  was_red
---+--
 lld-perf-testsuite| 137:48:32
 llvm-clang-win-x-armv7l   | 79:44:24
 llvm-clang-win-x-aarch64  | 62:53:11
 libcxx-libcxxabi-libunwind-aarch64-linux  | 54:46:45
 libcxx-libcxxabi-libunwind-aarch64-linux-noexceptions | 49:33:13
 clang-ppc64le-rhel| 42:43:30
 clang-with-lto-ubuntu | 33:11:28
 libcxx-libcxxabi-libunwind-x86_64-linux-debian| 24:22:53
 clang-s390x-linux-multistage  | 24:21:11
 clang-x86_64-debian-new-pass-manager-fast | 22:31:14
 clang-s390x-linux | 19:24:51
 llvm-clang-x86_64-expensive-checks-debian | 18:21:50
 clang-x86_64-debian-fast  | 17:43:08
 lldb-x86_64-debian| 14:59:48
 clang-ppc64le-linux-lnt   | 13:33:02
 clang-cmake-x86_64-avx2-linux | 12:25:10
 mlir-nvidia   | 11:42:29
 clang-cmake-x86_64-sde-avx512-linux   | 11:40:21
 llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast| 11:38:37
 llvm-avr-linux| 11:28:59
 clang-cmake-aarch64-lld   | 11:24:58
 clang-ppc64le-linux   | 07:32:06
 llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast  | 07:19:28
 clang-ppc64be-linux   | 06:40:38
 fuchsia-x86_64-linux  | 06:19:20
 aosp-O3-polly-before-vectorizer-unprofitable  | 06:07:36
 clang-x64-windows-msvc| 06:02:55
 clang-ppc64be-linux-lnt   | 05:40:36
 clang-with-thin-lto-ubuntu| 05:22:35
 clang-cmake-armv8-lld | 05:05:20
 lld-x86_64-win| 05:03:46
 lldb-x64-windows-ninja| 04:48:10
 sanitizer-windows | 04:44:54
 sanitizer-x86_64-linux| 04:42:42
 lld-x86_64-freebsd| 04:40:45
 llvm-clang-x86_64-win-fast| 04:34:19
 mlir-windows  | 04:32:46
 llvm-clang-x86_64-expensive-checks-win| 04:32:14
 polly-x86_64-linux-test-suite | 03:56:38
 sanitizer-x86_64-linux-bootstrap-ubsan| 03:55:27
 lld-x86_64-darwin | 03:29:56
 ppc64le-lld-multistage-test   | 03:29:20
 sanitizer-x86_64-linux-fast   | 03:28:19
 sanitizer-x86_64-linux-bootstrap-msan | 03:23:10
 lld-x86_64-ubuntu-fast| 03:07:42
 sanitizer-x86_64-linux-bootstrap  | 03:03:11
 clang-ppc64be-linux-multistage| 02:40:12
 clang-cmake-aarch64-global-isel   | 02:13:32
 clang-cmake-aarch64-full  | 02:09:33
 clang-ppc64le-linux-multistage| 02:08:54
 llvm-clang-x86_64-expensive-checks-ubuntu | 01:49:50
 sanitizer-x86_64-linux-fuzzer | 01:48:25
 flang-aarch64-ubuntu  | 01:34:10
 lldb-aarch64-ubuntu   | 01:33:55
 lldb-arm-ubuntu   | 01:33:46
 clang-cmake-armv7-global-isel | 01:33:44
 clang-cmake-aarch64-quick | 01:30:53
 clang-cmake-armv7-quick   | 01:30:28
 sanitizer-ppc64be-linux   | 01:22:45
 libcxx-libcxxabi-x86_64-linux-ubuntu-tsan | 00:57:26
 libcxx-libcxxabi-libunwind-x86_64-linux-ubuntu| 00:48:35
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx03| 00:48:27
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx14| 00:43:24
 sanitizer-x86_64-linux-android| 00:35:31
 

Buildbot numbers for the week of 08/09/2020 - 08/15/2020

[Galina Kistanova via cfe-commits]

Hello everyone,

Below are some buildbot numbers for the week of 08/09/2020 - 08/15/2020.

Please see the same data in attached csv files:

The longest time each builder was red during the week;
"Status change ratio" by active builder (percent of builds that changed the
builder status from green to red or from red to green);
Count of commits by project;
Number of completed builds, failed builds and average build time for
successful builds per active builder;
Average waiting time for a revision to get build result per active builder
(response time).

Thanks

Galina


The longest time each builder was red during the week:
buildername|  was_red
---+--
 llvm-clang-win-x-armv7l   | 116:09:14
 clang-s390x-linux-multistage  | 108:18:29
 clang-x64-windows-msvc| 107:45:48
 clang-s390x-linux | 106:20:20
 ppc64le-lld-multistage-test   | 53:44:27
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx17| 38:17:45
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx2a| 38:13:06
 libcxx-libcxxabi-x86_64-linux-ubuntu-asan | 38:00:15
 libcxx-libcxxabi-x86_64-linux-ubuntu-msan | 37:53:05
 clang-with-lto-ubuntu | 23:55:26
 clang-ppc64le-rhel| 21:24:29
 clang-with-thin-lto-ubuntu| 20:56:51
 sanitizer-windows | 16:09:51
 flang-aarch64-ubuntu  | 16:05:02
 llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast  | 11:16:04
 sanitizer-x86_64-linux-fast   | 08:46:31
 sanitizer-x86_64-linux-bootstrap  | 08:45:55
 polly-x86_64-linux-test-suite | 08:35:39
 clang-ppc64le-linux   | 08:30:03
 sanitizer-ppc64be-linux   | 08:19:19
 clang-cmake-aarch64-lld   | 08:08:54
 sanitizer-x86_64-linux| 07:09:11
 aosp-O3-polly-before-vectorizer-unprofitable  | 06:29:46
 mlir-nvidia   | 06:18:39
 llvm-clang-x86_64-expensive-checks-debian | 05:50:24
 llvm-clang-x86_64-expensive-checks-ubuntu | 05:33:27
 sanitizer-x86_64-linux-android| 05:21:20
 sanitizer-x86_64-linux-bootstrap-ubsan| 04:21:50
 clang-cmake-x86_64-avx2-linux | 03:46:37
 llvm-avr-linux| 03:31:32
 llvm-clang-win-x-aarch64  | 03:26:19
 clang-ppc64le-linux-lnt   | 03:19:05
 clang-ppc64le-linux-multistage| 03:05:17
 clang-cmake-aarch64-full  | 03:03:31
 clang-cmake-aarch64-quick | 03:01:12
 openmp-gcc-x86_64-linux-debian| 02:55:39
 clang-ppc64be-linux-multistage| 02:51:14
 clang-cmake-armv8-lld | 02:48:36
 clang-cmake-armv7-global-isel | 02:38:03
 llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast| 02:36:44
 clang-cmake-x86_64-sde-avx512-linux   | 02:34:21
 fuchsia-x86_64-linux  | 02:32:15
 llvm-clang-x86_64-expensive-checks-win| 02:29:05
 clang-ppc64be-linux-lnt   | 02:28:33
 lld-x86_64-win| 02:25:23
 openmp-clang-x86_64-linux-debian  | 02:24:21
 lld-x86_64-ubuntu-fast| 02:16:11
 clang-x86_64-debian-fast  | 02:16:05
 clang-x86_64-debian-new-pass-manager-fast | 02:16:01
 lld-x86_64-darwin | 02:15:25
 clang-ppc64be-linux   | 02:14:58
 clang-cmake-armv7-quick   | 02:13:41
 sanitizer-x86_64-linux-bootstrap-msan | 02:13:37
 mlir-windows  | 02:04:03
 clang-cmake-aarch64-global-isel   | 02:02:53
 sanitizer-x86_64-linux-autoconf   | 01:52:41
 sanitizer-x86_64-linux-fuzzer | 01:25:31
 libcxx-libcxxabi-x86_64-linux-debian-noexceptions | 01:13:01
 lldb-x64-windows-ninja| 01:06:52
 clang-x86_64-linux-abi-test   | 00:47:31
 libc-x86_64-debian-dbg| 00:45:15
 lldb-x86_64-debian| 00:40:22
 clang-cmake-armv7-lnt | 00:36:36
 lldb-aarch64-ubuntu   | 00:34:40
 lldb-arm-ubuntu   | 00:32:14
 polly-x86_64-linux| 00:31:02
 llvm-clang-x86_64-win-fast| 00:26:28
 clang-armv7-linux-build-cache | 00:24:04
 

Buildbot numbers for the week of 08/02/2020 - 08/08/2020

[Galina Kistanova via cfe-commits]

Hello everyone,

Below are some buildbot numbers for the last week of 08/02/2020 -
08/08/2020.

Please see the same data in attached csv files:

The longest time each builder was red during the week;
"Status change ratio" by active builder (percent of builds that changed the
builder status from green to red or from red to green);
Count of commits by project;
Number of completed builds, failed builds and average build time for
successful builds per active builder;
Average waiting time for a revision to get build result per active builder
(response time).

Thanks

Galina


The longest time each builder was red during the week:
   buildername|  was_red
--+--
 clang-cmake-aarch64-lld  | 149:59:42
 sanitizer-x86_64-linux-android   | 113:14:14
 sanitizer-x86_64-linux   | 113:08:02
 llvm-sphinx-docs | 80:44:55
 clang-ppc64le-rhel   | 79:23:51
 clang-ppc64le-linux-multistage   | 78:58:39
 ppc64le-lld-multistage-test  | 78:32:55
 clang-cmake-aarch64-full | 66:57:52
 llvm-clang-win-x-armv7l  | 62:32:02
 llvm-clang-win-x-aarch64 | 61:46:15
 flang-aarch64-ubuntu-clang   | 61:17:55
 clang-cmake-aarch64-global-isel  | 60:49:47
 clang-cmake-armv7-global-isel| 60:30:33
 clang-cmake-armv7-quick  | 60:25:13
 clang-cmake-armv8-lld| 60:16:17
 flang-aarch64-ubuntu | 60:13:56
 clang-cmake-aarch64-quick| 60:07:38
 polly-arm-linux  | 44:29:16
 polly-x86_64-linux   | 44:17:09
 aosp-O3-polly-before-vectorizer-unprofitable | 41:16:39
 llvm-clang-x86_64-expensive-checks-win   | 30:59:47
 llvm-clang-x86_64-expensive-checks-ubuntu| 27:55:30
 llvm-clang-x86_64-expensive-checks-debian| 27:31:07
 lldb-arm-ubuntu  | 20:51:59
 lldb-aarch64-ubuntu  | 20:20:20
 lldb-x64-windows-ninja   | 19:39:12
 lldb-x86_64-debian   | 19:00:08
 mlir-windows | 13:57:41
 clang-ppc64le-linux  | 09:45:52
 sanitizer-x86_64-linux-bootstrap-ubsan   | 08:43:21
 lld-x86_64-darwin| 08:02:08
 clang-with-lto-ubuntu| 07:53:41
 sanitizer-x86_64-linux-fast  | 07:44:19
 clang-armv7-linux-build-cache| 07:10:38
 sanitizer-ppc64be-linux  | 05:31:04
 sanitizer-x86_64-linux-bootstrap-msan| 04:49:20
 sanitizer-x86_64-linux-autoconf  | 04:40:34
 sanitizer-x86_64-linux-bootstrap | 04:33:18
 clang-ppc64le-linux-lnt  | 04:23:07
 clang-ppc64be-linux-multistage   | 04:13:11
 mlir-nvidia  | 04:12:43
 lld-perf-testsuite   | 04:06:19
 clang-with-thin-lto-ubuntu   | 03:59:05
 fuchsia-x86_64-linux | 03:58:56
 clang-aarch64-linux-build-cache  | 03:51:21
 llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast   | 03:49:43
 lld-x86_64-win   | 03:44:24
 openmp-gcc-x86_64-linux-debian   | 03:41:37
 clang-native-arm-lnt-perf| 03:37:14
 clang-x86_64-debian-fast | 03:36:25
 clang-x86_64-debian-new-pass-manager-fast| 03:36:24
 openmp-clang-x86_64-linux-debian | 03:34:49
 llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast | 03:27:59
 clang-s390x-linux-multistage | 03:24:56
 clang-ppc64be-linux-lnt  | 02:26:56
 clang-cmake-x86_64-avx2-linux| 01:57:59
 llvm-avr-linux   | 01:53:01
 llvm-clang-x86_64-win-fast   | 01:36:18
 sanitizer-x86_64-linux-fuzzer| 01:35:52
 clang-s390x-linux| 01:18:45
 sanitizer-windows| 01:14:39
 clang-cmake-x86_64-sde-avx512-linux  | 01:06:06
 clang-ppc64be-linux  | 00:55:16
 lld-x86_64-ubuntu-fast   | 00:54:40
 clang-cmake-armv7-lnt| 00:42:31
 clang-x86_64-linux-abi-test  | 00:39:38
 polly-x86_64-linux-test-suite| 00:34:48
 publish-sphinx-docs  | 00:33:54
 libc-x86_64-debian   | 00:29:38
 libc-x86_64-debian-dbg

Buildbot numbers for the week of 07/26/2020 - 08/01/2020

[Galina Kistanova via cfe-commits]

Hello everyone,

Below are some buildbot numbers for the week of 07/26/2020 - 08/01/2020.

Please see the same data in attached csv files:

The longest time each builder was red during the week;
"Status change ratio" by active builder (percent of builds that changed the
builder status from green to red or from red to green);
Count of commits by project;
Number of completed builds, failed builds and average build time for
successful builds per active builder;
Average waiting time for a revision to get build result per active builder
(response time).

Thanks

Galina


The longest time each builder was red during the week:
  buildername  | was_red
---+-
 polly-x86_64-linux| 81:11:51
 aosp-O3-polly-before-vectorizer-unprofitable  | 80:28:05
 polly-arm-linux   | 79:10:10
 clang-s390x-linux-multistage  | 60:56:34
 clang-s390x-linux | 54:50:42
 clang-ppc64be-linux-multistage| 54:27:42
 clang-ppc64be-linux-lnt   | 52:41:39
 clang-ppc64be-linux   | 52:24:35
 clang-ppc64le-rhel| 43:57:24
 llvm-avr-linux| 40:46:49
 clang-cmake-aarch64-lld   | 33:45:15
 publish-sphinx-docs   | 23:28:17
 libcxx-libcxxabi-libunwind-aarch64-linux-noexceptions | 19:18:08
 libcxx-libcxxabi-libunwind-armv8-linux-noexceptions   | 19:14:52
 libcxx-libcxxabi-libunwind-x86_64-linux-debian| 17:56:02
 libcxx-libcxxabi-x86_64-linux-debian-noexceptions | 17:55:52
 libcxx-libcxxabi-x86_64-linux-debian  | 17:55:01
 libcxx-libcxxabi-singlethreaded-x86_64-linux-debian   | 17:54:29
 clang-cmake-aarch64-full  | 16:30:22
 libcxx-libcxxabi-libunwind-armv7-linux-noexceptions   | 16:26:18
 libcxx-libcxxabi-libunwind-armv7-linux| 16:26:06
 clang-with-lto-ubuntu | 14:57:27
 libcxx-libcxxabi-libunwind-armv8-linux| 13:39:23
 libcxx-libcxxabi-libunwind-aarch64-linux  | 13:25:19
 clang-cmake-armv8-lld | 13:00:06
 clang-with-thin-lto-ubuntu| 12:37:12
 fuchsia-x86_64-linux  | 12:28:21
 ppc64le-lld-multistage-test   | 12:20:14
 sanitizer-x86_64-linux-bootstrap  | 12:17:40
 lldb-x64-windows-ninja| 10:26:17
 lldb-arm-ubuntu   | 10:26:05
 lldb-aarch64-ubuntu   | 10:24:08
 lldb-x86_64-debian| 10:13:50
 clang-ppc64le-linux-multistage| 08:49:46
 lld-x86_64-win| 07:42:36
 llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast  | 07:25:37
 lld-x86_64-darwin | 07:24:17
 llvm-clang-x86_64-expensive-checks-win| 05:33:22
 llvm-clang-x86_64-expensive-checks-ubuntu | 05:16:24
 sanitizer-x86_64-linux| 03:57:39
 clang-cuda-t4 | 03:55:31
 sanitizer-ppc64be-linux   | 03:35:58
 clang-ppc64le-linux   | 03:17:56
 llvm-clang-x86_64-expensive-checks-debian | 02:54:46
 libc-x86_64-debian-dbg-asan   | 02:52:05
 sanitizer-x86_64-linux-fast   | 02:38:18
 clang-ppc64le-linux-lnt   | 02:17:51
 llvm-clang-win-x-armv7l   | 02:03:39
 sanitizer-x86_64-linux-bootstrap-ubsan| 02:02:59
 clang-cmake-x86_64-avx2-linux | 01:52:23
 sanitizer-x86_64-linux-fuzzer | 01:48:23
 mlir-windows  | 01:34:56
 clang-cmake-armv7-quick   | 01:29:33
 flang-aarch64-ubuntu  | 01:26:09
 flang-aarch64-ubuntu-clang| 01:22:34
 sanitizer-x86_64-linux-bootstrap-msan | 01:20:25
 clang-x86_64-debian-new-pass-manager-fast | 01:11:05
 llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast| 01:10:55
 clang-x86_64-debian-fast  | 01:10:42
 clang-cmake-armv7-global-isel | 01:09:38
 clang-x86_64-linux-abi-test   | 01:05:19
 openmp-gcc-x86_64-linux-debian| 01:04:02
 clang-cmake-aarch64-quick | 01:03:19
 mlir-nvidia   | 00:58:53
 

Buildbot numbers for the week of 07/19/2020 - 07/25/2020

[Galina Kistanova via cfe-commits]

Hello everyone,

Below are some buildbot numbers for the week of 07/19/2020 - 07/25/2020.

Please see the same data in attached csv files:

The longest time each builder was red during the week;
"Status change ratio" by active builder (percent of builds that changed the
builder status from green to red or from red to green);
Count of commits by project;
Number of completed builds, failed builds and average build time for
successful builds per active builder;
Average waiting time for a revision to get build result per active builder
(response time).

Thanks

Galina


The longest time each builder was red during the week:
   buildername   |  was_red
-+--
 polly-arm-linux | 108:46:13
 aosp-O3-polly-before-vectorizer-unprofitable| 107:14:37
 polly-x86_64-linux  | 106:44:58
 sanitizer-x86_64-linux-android  | 80:01:07
 clang-armv7-linux-build-cache   | 51:39:03
 clang-cmake-aarch64-lld | 49:08:27
 lldb-x64-windows-ninja  | 45:34:57
 clang-cmake-aarch64-full| 44:02:11
 libcxx-libcxxabi-x86_64-linux-debian| 33:34:26
 clang-ppc64le-rhel  | 32:53:02
 ppc64le-lld-multistage-test | 29:20:02
 clang-native-arm-lnt-perf   | 27:41:10
 clang-cmake-armv8-lld   | 26:15:16
 sanitizer-ppc64be-linux | 25:56:13
 sanitizer-windows   | 24:45:02
 flang-aarch64-ubuntu-clang  | 18:45:51
 llvm-avr-linux  | 17:48:39
 clang-ppc64le-linux-multistage  | 13:37:02
 lldb-arm-ubuntu | 11:50:01
 lldb-aarch64-ubuntu | 11:44:22
 sanitizer-x86_64-linux  | 09:08:54
 sanitizer-x86_64-linux-autoconf | 06:01:01
 clang-ppc64be-linux-multistage  | 05:31:43
 openmp-clang-x86_64-linux-debian| 05:23:02
 llvm-clang-win-x-armv7l | 04:59:39
 clang-cmake-aarch64-global-isel | 04:46:55
 clang-with-lto-ubuntu   | 04:40:39
 clang-cmake-aarch64-quick   | 04:38:40
 clang-ppc64le-linux-lnt | 04:35:27
 clang-s390x-linux   | 04:31:14
 clang-ppc64le-linux | 04:18:58
 clang-cmake-armv7-global-isel   | 04:17:17
 clang-cmake-armv7-lnt   | 04:14:00
 clang-s390x-linux-multistage| 04:12:48
 llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast| 04:07:37
 clang-ppc64be-linux-lnt | 04:07:26
 fuchsia-x86_64-linux| 04:04:57
 llvm-clang-win-x-aarch64| 04:03:39
 clang-ppc64be-linux | 04:00:12
 clang-cmake-armv7-quick | 03:58:08
 clang-x86_64-debian-new-pass-manager-fast   | 03:49:12
 clang-x86_64-debian-fast| 03:49:04
 llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast  | 03:45:50
 libc-x86_64-debian-dbg-asan | 03:42:16
 libc-x86_64-debian-dbg  | 03:41:48
 libc-x86_64-debian  | 03:41:27
 sanitizer-x86_64-linux-fast | 03:31:22
 clang-with-thin-lto-ubuntu  | 02:57:56
 sanitizer-x86_64-linux-fuzzer   | 02:49:31
 clang-x86_64-linux-abi-test | 02:45:03
 sanitizer-x86_64-linux-bootstrap| 02:44:38
 llvm-clang-x86_64-expensive-checks-win  | 02:43:37
 lld-x86_64-darwin   | 02:16:03
 sanitizer-x86_64-linux-bootstrap-msan   | 02:10:55
 lld-x86_64-win  | 02:07:04
 lldb-x86_64-debian  | 02:04:15
 clang-cmake-x86_64-avx2-linux   | 01:58:58
 sanitizer-x86_64-linux-bootstrap-ubsan  | 01:58:53
 clang-cmake-x86_64-sde-avx512-linux | 01:44:04
 lld-x86_64-ubuntu-fast  | 01:40:16
 llvm-clang-x86_64-expensive-checks-debian   | 01:38:13
 flang-aarch64-ubuntu| 01:37:45
 

LLVM buildmaster and LVM lab machines will be unavailable today at 6:00 pm PST

[Galina Kistanova via cfe-commits]

Hello everyone,


LLVM buildmaster and LVM lab machines will be unavailable today Wednesday,
August 5th at 6:00 pm PST due to Network maintenance.

The planned maintenance duration is 30 minutes.

Thank you for understanding.


Thanks


Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be restarted soon

[Galina Kistanova via cfe-commits]

Hello everyone,

LLVM buildmaster will be updated and restarted in the nearest hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be restarted soon

[Galina Kistanova via cfe-commits]

Hello everyone,

LLVM buildmaster will be updated and restarted in the nearest hour.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster is back to normal work

[Galina Kistanova via cfe-commits]

Hello everyone,

LLVM buildmaster is back to normal work, sorry for inconvenience.
Last night updates caused some distortions unfortunately.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM buildmaster will be updated and restarted tonight

[Galina Kistanova via cfe-commits]

Hello everyone,

LLVM buildmaster will be updated and restarted after 6PM PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Buildbot numbers for the week of 07/12/2020 - 07/18/2020

[Galina Kistanova via cfe-commits]

Hello everyone,

Below are some buildbot numbers for the last week of 07/12/2020 -
07/18/2020.

Please see the same data in attached csv files:

The longest time each builder was red during the week;
"Status change ratio" by active builder (percent of builds that changed the
builder status from green to red or from red to green);
Count of commits by project;
Number of completed builds, failed builds and average build time for
successful builds per active builder;
Average waiting time for a revision to get build result per active builder
(response time).

Thanks

Galina


The longest time each builder was red during the week:
   buildername| was_red
--+-
 sanitizer-x86_64-linux   | 75:51:01
 clang-s390x-linux-lnt| 64:53:02
 clang-cmake-aarch64-lld  | 40:26:36
 clang-cmake-aarch64-full | 40:17:00
 sanitizer-x86_64-linux-bootstrap | 37:51:22
 clang-with-thin-lto-ubuntu   | 37:35:16
 sanitizer-x86_64-linux-bootstrap-ubsan   | 37:20:48
 clang-with-lto-ubuntu| 35:59:42
 sanitizer-x86_64-linux-bootstrap-msan| 34:58:20
 fuchsia-x86_64-linux | 34:38:49
 clang-x86_64-debian-new-pass-manager-fast| 31:45:03
 clang-ppc64be-linux-lnt  | 20:47:08
 clang-ppc64be-linux  | 20:29:33
 clang-s390x-linux| 20:28:41
 clang-ppc64be-linux-multistage   | 20:25:08
 sanitizer-windows| 19:54:14
 llvm-avr-linux   | 19:25:45
 clang-s390x-linux-multistage | 17:50:24
 sanitizer-x86_64-linux-android   | 08:54:01
 clang-x64-windows-msvc   | 07:41:40
 clang-ppc64le-linux-multistage   | 06:47:19
 sanitizer-x86_64-linux-fast  | 06:25:10
 clang-ppc64le-linux-lnt  | 06:13:33
 lldb-x64-windows-ninja   | 06:10:38
 clang-ppc64le-linux  | 05:53:00
 sanitizer-ppc64be-linux  | 05:51:59
 clang-cmake-armv8-lld| 05:03:42
 clang-native-arm-lnt-perf| 03:56:23
 llvm-clang-x86_64-expensive-checks-ubuntu| 03:54:32
 llvm-clang-x86_64-expensive-checks-win   | 03:52:36
 llvm-clang-x86_64-expensive-checks-debian| 03:38:01
 llvm-clang-win-x-armv7l  | 03:18:47
 llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast | 03:07:52
 lld-x86_64-win   | 02:46:34
 sanitizer-x86_64-linux-fuzzer| 02:43:41
 mlir-windows | 02:32:56
 llvm-clang-win-x-aarch64 | 02:30:30
 clang-ppc64le-rhel   | 02:25:32
 openmp-clang-x86_64-linux-debian | 02:25:31
 llvm-clang-x86_64-win-fast   | 02:19:24
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx17   | 02:09:40
 ppc64le-lld-multistage-test  | 02:07:43
 libcxx-libcxxabi-x86_64-linux-ubuntu-asan| 02:05:12
 libcxx-libcxxabi-x86_64-linux-ubuntu-ubsan   | 02:05:11
 clang-cmake-aarch64-global-isel  | 02:04:35
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx2a   | 02:04:18
 libcxx-libcxxabi-x86_64-linux-ubuntu-msan| 02:01:22
 clang-cmake-x86_64-avx2-linux| 01:59:43
 clang-cmake-armv7-quick  | 01:46:31
 lld-x86_64-ubuntu-fast   | 01:46:20
 clang-cmake-aarch64-quick| 01:40:58
 clang-cmake-x86_64-sde-avx512-linux  | 01:39:59
 llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast   | 01:38:02
 clang-x86_64-debian-fast | 01:35:30
 clang-cmake-armv7-global-isel| 01:32:40
 openmp-gcc-x86_64-linux-debian   | 01:31:17
 clang-armv7-linux-build-cache| 01:24:34
 llvm-sphinx-docs | 01:22:16
 flang-aarch64-ubuntu | 01:21:12
 lld-x86_64-darwin| 01:20:36
 mlir-nvidia  | 01:20:23
 clang-cmake-armv7-lnt| 01:19:58
 lldb-arm-ubuntu  | 01:11:04
 lldb-aarch64-ubuntu  | 01:08:17
 libc-x86_64-debian-dbg   | 01:04:41
 sanitizer-x86_64-linux-autoconf  | 01:04:12
 publish-sphinx-docs  | 01:03:56
 libc-x86_64-debian-dbg-asan  | 01:02:37
 clang-x86_64-linux-abi-test  | 00:59:22
 libc-x86_64-debian 

Buildbot numbers for the week of 07/5/2020 - 07/11/2020

[Galina Kistanova via cfe-commits]

Hello everyone,

Below are some buildbot numbers for the week of 07/5/2020 - 07/11/2020.

Please see the same data in attached csv files:

The longest time each builder was red during the week;
"Status change ratio" by active builder (percent of builds that changed the
builder status from green to red or from red to green);
Count of commits by project;
Number of completed builds, failed builds and average build time for
successful builds per active builder;
Average waiting time for a revision to get build result per active builder
(response time).

Thanks

Galina


The longest time each builder was red during the week:
   buildername   |  was_red
-+--
 clang-cmake-aarch64-lld | 153:30:07
 libcxx-libcxxabi-x86_64-linux-ubuntu-gcc5-cxx11 | 122:32:08
 llvm-sphinx-docs| 110:37:57
 llvm-clang-x86_64-expensive-checks-win  | 60:10:24
 aosp-O3-polly-before-vectorizer-unprofitable| 57:15:01
 polly-arm-linux | 53:32:33
 polly-x86_64-linux  | 51:00:58
 clang-cmake-aarch64-full| 34:36:56
 ppc64le-lld-multistage-test | 33:11:21
 clang-ppc64le-linux-lnt | 31:51:42
 llvm-clang-x86_64-expensive-checks-ubuntu   | 31:26:43
 llvm-clang-x86_64-expensive-checks-debian   | 31:26:20
 sanitizer-ppc64be-linux | 29:34:38
 clang-ppc64le-linux-multistage  | 29:07:07
 clang-ppc64be-linux | 28:09:45
 libcxx-libcxxabi-libunwind-armv7-linux  | 25:49:12
 libcxx-libcxxabi-libunwind-armv7-linux-noexceptions | 25:49:01
 clang-ppc64le-linux | 25:44:30
 llvm-clang-win-x-armv7l | 25:07:57
 clang-ppc64be-linux-lnt | 25:02:58
 llvm-clang-win-x-aarch64| 23:27:56
 libcxx-libcxxabi-libunwind-armv8-linux  | 17:24:00
 libcxx-libcxxabi-libunwind-armv8-linux-noexceptions | 17:05:24
 fuchsia-x86_64-linux| 16:52:25
 libcxx-libcxxabi-x86_64-linux-ubuntu-32bit  | 14:46:40
 libcxx-libcxxabi-x86_64-linux-ubuntu-gcc-tot-latest-std | 14:46:12
 mlir-windows| 14:35:36
 clang-s390x-linux-lnt   | 13:25:12
 lldb-x64-windows-ninja  | 12:43:01
 sanitizer-x86_64-linux  | 10:36:26
 libc-x86_64-debian-dbg  | 09:49:27
 llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast  | 07:41:12
 llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast| 06:47:19
 clang-x64-windows-msvc  | 06:35:30
 clang-with-lto-ubuntu   | 06:25:30
 libcxx-libcxxabi-libunwind-aarch64-linux| 05:30:01
 clang-ppc64le-rhel  | 05:28:01
 clang-with-thin-lto-ubuntu  | 05:27:09
 clang-cmake-armv8-lld   | 04:49:39
 lldb-arm-ubuntu | 03:38:27
 lld-x86_64-win  | 03:16:22
 clang-s390x-linux   | 02:48:34
 clang-x86_64-debian-fast| 02:11:52
 clang-cmake-aarch64-global-isel | 02:04:29
 clang-cmake-aarch64-quick   | 01:53:33
 sanitizer-x86_64-linux-bootstrap| 01:52:52
 flang-aarch64-ubuntu| 01:45:23
 sanitizer-x86_64-linux-bootstrap-msan   | 01:42:58
 clang-cmake-armv7-global-isel   | 01:36:33
 llvm-avr-linux  | 01:33:45
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx11  | 01:32:15
 sanitizer-x86_64-linux-fast | 01:29:56
 libcxx-libcxxabi-x86_64-linux-ubuntu-ubsan  | 01:28:44
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx2a  | 01:28:11
 sanitizer-x86_64-linux-android  | 01:28:04
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx17  | 01:27:59
 libcxx-libcxxabi-x86_64-linux-ubuntu-asan   | 01:27:44
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx14  | 01:25:06
 clang-cmake-armv7-quick | 01:20:23
 lld-x86_64-darwin   | 01:20:02
 clang-x86_64-debian-new-pass-manager-fast   | 01:18:40
 libcxx-libcxxabi-libunwind-x86_64-linux-ubuntu  | 01:17:48
 

Buildbot numbers for the week of 06/28/2020 - 07/04/2020

[Galina Kistanova via cfe-commits]

Hello everyone,

Below are some buildbot numbers for the last week of 06/28/2020 -
07/04/2020.

Please see the same data in attached csv files:

The longest time each builder was red during the week;
"Status change ratio" by active builder (percent of builds that changed the
builder status from green to red or from red to green);
Count of commits by project;
Number of completed builds, failed builds and average build time for
successful builds per active builder;
Average waiting time for a revision to get build result per active builder
(response time).

Thanks

Galina


The longest time each builder was red during the week:
   buildername| was_red
--+-
 clang-s390x-linux-multistage | 81:56:32
 clang-s390x-linux| 80:24:20
 clang-s390x-linux-lnt| 80:20:51
 llvm-clang-win-x-aarch64 | 69:41:19
 clang-cmake-aarch64-lld  | 60:26:11
 llvm-sphinx-docs | 56:14:14
 openmp-gcc-x86_64-linux-debian   | 50:07:25
 lldb-arm-ubuntu  | 49:51:53
 fuchsia-x86_64-linux | 32:37:12
 clang-x86_64-debian-new-pass-manager-fast| 32:32:17
 sanitizer-x86_64-linux-bootstrap | 27:16:04
 sanitizer-x86_64-linux-fast  | 25:36:45
 lldb-x64-windows-ninja   | 23:03:03
 clang-cmake-aarch64-full | 22:50:43
 sanitizer-x86_64-linux-android   | 19:28:03
 polly-arm-linux  | 18:18:56
 aosp-O3-polly-before-vectorizer-unprofitable | 16:57:06
 clang-ppc64le-linux-multistage   | 15:05:33
 sanitizer-x86_64-linux   | 11:40:01
 clang-with-lto-ubuntu| 08:54:10
 clang-cmake-armv8-lld| 07:51:15
 clang-with-thin-lto-ubuntu   | 07:40:48
 llvm-clang-win-x-armv7l  | 06:33:40
 clang-cmake-armv7-global-isel| 06:20:07
 clang-ppc64be-linux-multistage   | 06:10:47
 clang-cmake-aarch64-global-isel  | 06:09:00
 clang-cmake-armv7-quick  | 06:07:43
 llvm-avr-linux   | 06:07:15
 llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast | 06:02:56
 clang-x64-windows-msvc   | 06:02:15
 clang-ppc64be-linux  | 06:02:06
 clang-cmake-x86_64-sde-avx512-linux  | 05:59:56
 llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast   | 05:59:54
 clang-ppc64le-rhel   | 05:58:46
 lld-x86_64-win   | 05:55:14
 flang-aarch64-ubuntu-clang   | 05:52:53
 clang-ppc64be-linux-lnt  | 05:49:22
 ppc64le-lld-multistage-test  | 05:45:38
 flang-aarch64-ubuntu | 05:43:05
 clang-cmake-aarch64-quick| 05:24:04
 sanitizer-x86_64-linux-bootstrap-msan| 05:18:10
 polly-x86_64-linux   | 05:11:52
 sanitizer-x86_64-linux-bootstrap-ubsan   | 04:41:18
 lld-x86_64-darwin| 04:36:23
 lld-x86_64-ubuntu-fast   | 04:10:41
 clang-ppc64le-linux-lnt  | 04:08:42
 sanitizer-ppc64be-linux  | 03:54:01
 clang-cmake-x86_64-avx2-linux| 03:49:53
 mlir-nvidia  | 03:28:53
 clang-x86_64-debian-fast | 03:01:37
 mlir-windows | 02:59:58
 clang-armv7-linux-build-cache| 02:46:28
 llvm-clang-x86_64-expensive-checks-ubuntu| 02:37:36
 sanitizer-x86_64-linux-fuzzer| 02:10:42
 llvm-clang-x86_64-expensive-checks-win   | 01:37:53
 clang-ppc64le-linux  | 01:30:19
 sanitizer-x86_64-linux-autoconf  | 01:09:18
 publish-sphinx-docs  | 01:07:47
 clang-cmake-armv7-lnt| 00:58:40
 clang-x86_64-linux-abi-test  | 00:49:06
 libc-x86_64-debian-dbg   | 00:40:25
 sanitizer-windows| 00:35:07
 llvm-clang-x86_64-expensive-checks-debian| 00:33:48
 lldb-aarch64-ubuntu  | 00:32:34
 llvm-clang-x86_64-win-fast   | 00:23:43
 openmp-clang-x86_64-linux-debian | 00:19:03
 lldb-x86_64-debian   | 00:15:16
(67 rows)


"Status change ratio" by active builder (percent of builds that changed the
builder status from greed to red or from red to green):
  

Buildbot numbers for the week of 06/21/2020 - 06/27/2020

[Galina Kistanova via cfe-commits]

Hello everyone,

Below are some buildbot numbers for the week of 06/21/2020 - 06/27/2020.

Please see the same data in attached csv files:

The longest time each builder was red during the week;
"Status change ratio" by active builder (percent of builds that changed the
builder status from green to red or from red to green);
Count of commits by project;
Number of completed builds, failed builds and average build time for
successful builds per active builder;
Average waiting time for a revision to get build result per active builder
(response time).

Thanks

Galina


The longest time each builder was red during the week:
   buildername| was_red
--+-
 publish-sphinx-docs  | 68:49:52
 ppc64le-lld-multistage-test  | 55:55:54
 clang-ppc64le-rhel   | 55:18:23
 clang-tools-sphinx-docs  | 51:02:34
 llvm-clang-win-x-armv7l  | 45:10:32
 clang-cmake-aarch64-lld  | 32:12:04
 llvm-clang-win-x-aarch64 | 28:46:30
 fuchsia-x86_64-linux | 22:19:45
 llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast | 22:07:12
 clang-x86_64-debian-new-pass-manager-fast| 22:00:02
 llvm-clang-x86_64-win-fast   | 21:22:05
 clang-x64-windows-msvc   | 21:13:41
 sanitizer-x86_64-linux-fast  | 20:15:48
 sanitizer-x86_64-linux-bootstrap-ubsan   | 20:06:52
 llvm-clang-x86_64-expensive-checks-ubuntu| 20:05:54
 llvm-clang-x86_64-expensive-checks-debian| 20:05:54
 llvm-clang-x86_64-expensive-checks-win   | 19:41:41
 sanitizer-x86_64-linux-bootstrap | 19:38:41
 clang-cmake-aarch64-full | 15:48:36
 aosp-O3-polly-before-vectorizer-unprofitable | 07:16:36
 lldb-x64-windows-ninja   | 07:08:00
 libc-x86_64-debian-dbg   | 07:04:21
 polly-x86_64-linux   | 06:22:52
 polly-arm-linux  | 05:52:11
 lld-x86_64-darwin| 05:35:39
 libc-x86_64-debian   | 05:24:19
 libc-x86_64-debian-dbg-asan  | 05:22:59
 clang-cmake-aarch64-quick| 05:15:34
 sanitizer-x86_64-linux-fuzzer| 05:12:29
 clang-ppc64le-linux-multistage   | 05:02:42
 llvm-avr-linux   | 04:41:41
 sanitizer-x86_64-linux-bootstrap-msan| 04:41:11
 clang-cmake-aarch64-global-isel  | 04:39:28
 clang-ppc64be-linux-lnt  | 04:21:05
 sanitizer-x86_64-linux-autoconf  | 04:13:49
 clang-s390x-linux-lnt| 03:53:46
 lldb-x86_64-debian   | 03:50:00
 clang-ppc64le-linux-lnt  | 03:40:27
 clang-x86_64-linux-abi-test  | 03:36:43
 sanitizer-windows| 03:27:49
 clang-cmake-armv8-lld| 03:23:13
 clang-s390x-linux| 03:22:57
 sanitizer-x86_64-linux-android   | 03:19:40
 clang-ppc64le-linux  | 03:13:01
 sanitizer-x86_64-linux   | 03:11:56
 clang-ppc64be-linux  | 03:07:56
 clang-ppc64be-linux-multistage   | 02:55:08
 sanitizer-ppc64be-linux  | 02:38:30
 clang-cmake-x86_64-sde-avx512-linux  | 02:30:49
 clang-cmake-x86_64-avx2-linux| 02:29:16
 clang-with-thin-lto-ubuntu   | 02:29:12
 clang-armv7-linux-build-cache| 02:27:44
 clang-s390x-linux-multistage | 02:26:52
 lldb-arm-ubuntu  | 02:20:06
 clang-cmake-armv7-global-isel| 02:02:04
 flang-aarch64-ubuntu | 01:53:50
 llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast   | 01:49:54
 openmp-clang-x86_64-linux-debian | 01:43:54
 lldb-aarch64-ubuntu  | 01:36:00
 clang-cmake-armv7-quick  | 01:35:20
 lld-perf-testsuite   | 01:32:57
 lld-x86_64-win   | 01:23:29
 mlir-nvidia  | 01:09:01
 flang-aarch64-ubuntu-clang   | 00:58:25
 lld-x86_64-ubuntu-fast   | 00:56:28
 mlir-windows | 00:53:19
 clang-x86_64-debian-fast | 00:48:25
(67 rows)


"Status change ratio" by active builder (percent of builds that changed the
builder status from greed to red or from red to green):
   

LLVM buildmaster will be updated and restarted tonight

[Galina Kistanova via cfe-commits]

 Hello everyone,

LLVM buildmaster will be updated and restarted after 6PM PST today.

Thanks

Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

LLVM Lab network works today at 6:30 PM PST

[Galina Kistanova via cfe-commits]

Hello everyone,


LLVM Lab will be unavailable for a short time at about 6:30 PM PST due
network maintenance.

Thank you for understanding.


Thanks


Galina
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Buildbot numbers for the week of 06/14/2020 - 06/20/2020

[Galina Kistanova via cfe-commits]

Hello everyone,

Below are some buildbot numbers for the last week of 06/14/2020 -
06/20/2020.

Please see the same data in attached csv files:

The longest time each builder was red during the week;
"Status change ratio" by active builder (percent of builds that changed the
builder status from green to red or from red to green);
Count of commits by project;
Number of completed builds, failed builds and average build time for
successful builds per active builder;
Average waiting time for a revision to get build result per active builder
(response time).

Thanks

Galina


The longest time each builder was red during the week:
   buildername   |  was_red
-+--
 llvm-clang-win-x-armv7l | 139:09:35
 lld-x86_64-freebsd  | 109:33:39
 mlir-nvidia | 96:23:08
 lldb-aarch64-ubuntu | 62:38:08
 libcxx-libcxxabi-libunwind-aarch64-linux| 58:02:39
 libcxx-libcxxabi-libunwind-armv7-linux-noexceptions | 48:08:45
 sanitizer-x86_64-linux  | 41:50:09
 libcxx-libcxxabi-libunwind-armv8-linux-noexceptions | 41:15:51
 libcxx-libcxxabi-x86_64-linux-debian-noexceptions   | 40:32:36
 libcxx-libcxxabi-libunwind-aarch64-linux-noexceptions   | 39:20:33
 clang-x64-windows-msvc  | 28:57:51
 llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast| 26:51:32
 libcxx-libcxxabi-libunwind-armv8-linux  | 14:10:40
 llvm-clang-win-x-aarch64| 13:07:44
 clang-ppc64le-linux-multistage  | 12:50:05
 sanitizer-x86_64-linux-fast | 12:29:31
 sanitizer-x86_64-linux-bootstrap-ubsan  | 11:14:41
 ppc64le-lld-multistage-test | 09:41:16
 clang-ppc64le-linux-lnt | 09:25:03
 lldb-x64-windows-ninja  | 09:20:27
 clang-cmake-thumbv7-full-sh | 08:40:11
 clang-ppc64be-linux-multistage  | 08:37:09
 clang-s390x-linux-lnt   | 07:56:57
 clang-ppc64be-linux-lnt | 07:38:35
 clang-cmake-armv7-full  | 07:35:32
 clang-ppc64be-linux | 07:26:42
 lld-x86_64-darwin   | 07:23:31
 lld-x86_64-win  | 07:12:53
 clang-ppc64le-rhel  | 07:09:26
 fuchsia-x86_64-linux| 07:02:39
 clang-cmake-armv7-lnt   | 06:43:15
 clang-cmake-aarch64-quick   | 06:38:22
 clang-s390x-linux-multistage| 06:31:27
 clang-cmake-aarch64-global-isel | 06:22:09
 clang-ppc64le-linux | 06:08:04
 libcxx-libcxxabi-x86_64-linux-ubuntu-msan   | 05:57:49
 libcxx-libcxxabi-x86_64-linux-ubuntu-ubsan  | 05:57:28
 clang-s390x-linux   | 05:57:21
 libcxx-libcxxabi-x86_64-linux-ubuntu-tsan   | 05:57:19
 libcxx-libcxxabi-x86_64-linux-debian| 05:56:19
 libcxx-libcxxabi-singlethreaded-x86_64-linux-debian | 05:55:47
 libcxx-libcxxabi-x86_64-linux-ubuntu-asan   | 05:55:20
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx11  | 05:54:50
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx2a  | 05:54:28
 libcxx-libcxxabi-x86_64-linux-ubuntu-32bit  | 05:53:53
 clang-cmake-aarch64-lld | 05:53:53
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx03  | 05:53:39
 libcxx-libcxxabi-libunwind-x86_64-linux-debian  | 05:53:04
 clang-cmake-armv7-global-isel   | 05:52:05
 libcxx-libcxxabi-x86_64-linux-ubuntu-gcc-tot-latest-std | 05:51:46
 libcxx-libcxxabi-libunwind-x86_64-linux-ubuntu  | 05:51:44
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx17  | 05:46:03
 libcxx-libcxxabi-x86_64-linux-ubuntu-cxx14  | 05:42:43
 clang-cmake-armv7-quick | 05:41:26
 clang-cmake-armv8-lld   | 05:00:27
 flang-aarch64-ubuntu| 04:58:42
 clang-cmake-aarch64-full| 04:51:41
 sanitizer-ppc64le-linux | 04:48:07
 clang-with-thin-lto-ubuntu  | 03:28:45
 aosp-O3-polly-before-vectorizer-unprofitable| 03:27:28
 clang-cmake-armv7-selfhost  | 03:25:47
 sanitizer-ppc64be-linux | 03:22:10
 

Buildbot numbers for the week of 06/7/2020 - 06/13/2020

[Galina Kistanova via cfe-commits]

Hello everyone,

Below are some buildbot numbers for the week of 06/7/2020 - 06/13/2020.

Please see the same data in attached csv files:

The longest time each builder was red during the week;
"Status change ratio" by active builder (percent of builds that changed the
builder status from green to red or from red to green);
Count of commits by project;
Number of completed builds, failed builds and average build time for
successful builds per active builder;
Average waiting time for a revision to get build result per active builder
(response time).

Thanks

Galina


The longest time each builder was red during the week:
 buildername | was_red
-+-
 sanitizer-x86_64-linux-android  | 97:09:18
 clang-cmake-thumbv7-full-sh | 86:10:53
 clang-cmake-armv7-full  | 63:59:05
 llvm-clang-win-x-armv7l | 63:20:01
 sanitizer-ppc64le-linux | 47:55:21
 clang-ppc64le-linux-lnt | 47:41:34
 clang-ppc64be-linux-lnt | 47:04:18
 clang-ppc64le-rhel  | 46:46:40
 clang-cmake-armv8-lld   | 41:12:19
 clang-cmake-armv7-selfhost  | 39:19:22
 clang-cmake-aarch64-global-isel | 39:14:51
 clang-cmake-armv7-global-isel   | 39:08:37
 clang-cmake-aarch64-lld | 38:59:24
 clang-cmake-aarch64-quick   | 38:16:32
 clang-cmake-aarch64-full| 37:56:25
 clang-ppc64be-linux-multistage  | 37:48:06
 clang-cmake-armv7-quick | 36:21:06
 sanitizer-x86_64-linux  | 36:19:46
 sanitizer-windows   | 34:31:26
 libcxx-libcxxabi-libunwind-aarch64-linux| 29:45:57
 flang-aarch64-ubuntu| 24:51:02
 lldb-x64-windows-ninja  | 24:23:45
 clang-x64-windows-msvc  | 24:19:53
 sanitizer-x86_64-linux-bootstrap| 23:33:08
 sanitizer-x86_64-linux-bootstrap-ubsan  | 23:03:53
 sanitizer-x86_64-linux-bootstrap-msan   | 22:15:04
 libcxx-libcxxabi-libunwind-armv7-linux  | 16:43:02
 sanitizer-x86_64-linux-fast | 16:42:18
 clang-with-lto-ubuntu   | 16:12:09
 clang-s390x-linux-multistage| 15:14:48
 clang-with-thin-lto-ubuntu  | 14:59:56
 clang-ppc64le-linux-multistage  | 14:17:26
 llvm-avr-linux  | 14:11:20
 clang-s390x-linux   | 14:10:42
 clang-s390x-linux-lnt   | 14:10:31
 clang-ppc64be-linux | 13:51:58
 sanitizer-ppc64be-linux | 13:46:01
 llvm-clang-x86_64-expensive-checks-win  | 12:17:34
 fuchsia-x86_64-linux| 12:03:48
 libcxx-libcxxabi-libunwind-armv7-linux-noexceptions | 11:48:36
 ppc64le-lld-multistage-test | 10:40:02
 flang-aarch64-ubuntu-clang  | 08:55:47
 clang-x86_64-debian-new-pass-manager-fast   | 06:59:08
 mlir-nvidia | 06:56:01
 clang-x86_64-debian-fast| 06:53:01
 lld-x86_64-ubuntu-fast  | 06:39:02
 ml-opt-dev-x86-64   | 05:59:25
 llvm-clang-x86_64-expensive-checks-ubuntu   | 05:55:18
 libcxx-libcxxabi-libunwind-armv8-linux-noexceptions | 05:30:34
 lld-x86_64-win  | 05:12:23
 lld-x86_64-darwin   | 04:53:16
 clang-ppc64le-linux | 04:42:12
 llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast| 04:11:04
 libc-x86_64-debian-dbg  | 04:10:47
 libc-x86_64-debian  | 03:29:58
 aosp-O3-polly-before-vectorizer-unprofitable| 03:25:49
 libcxx-libcxxabi-x86_64-linux-ubuntu-asan   | 02:55:56
 clang-cmake-x86_64-avx2-linux   | 02:52:19
 mlir-windows| 02:51:03
 llvm-clang-win-x-aarch64| 02:42:32
 llvm-clang-x86_64-expensive-checks-debian   | 02:41:05
 llvm-clang-x86_64-win-fast  | 02:39:01
 ml-opt-rel-x86-64   | 02:35:30
 clang-cmake-x86_64-sde-avx512-linux | 02:34:34
 llvm-clang-lld-x86_64-scei-ps4-ubuntu-fast  | 02:29:56
 sanitizer-x86_64-linux-fuzzer   | 02:24:46
 lldb-x86_64-debian