Reid Kleckner via llvm-dev
2019-Jul-31 18:53 UTC
[llvm-dev] buildbot failure in LLVM on sanitizer-x86_64-linux-gn
On Wed, Jul 31, 2019 at 11:37 AM Vitaly Buka via llvm-dev < llvm-dev at lists.llvm.org> wrote:> I have no idea how. > Are there particular problems? Now it should be quite. > Console has a bunch of stale builders which are even less useful. >LLVM has a silent build master that does not send email. When Nico added the gn build, apparently we promised not to set up builders that send email. I searched for info about the silent buildmaster in the zorg repository, but I found nothing. I added Galina, maybe she can say more about how to set that up and where its config is managed. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190731/f01ca262/attachment.html>
Nico Weber via llvm-dev
2019-Jul-31 18:59 UTC
[llvm-dev] buildbot failure in LLVM on sanitizer-x86_64-linux-gn
It already doesn't send email. Just the bot showing up on http://lab.llvm.org:8011/console suggests more support than there is for this build config though (namely, none). And if someone lands something and watches http://lab.llvm.org:8011/console then that bot turning red might be confusing. If there's no way to hide bots onhttp://lab.llvm.org:8011/console then that bot should live on a different master. On Wed, Jul 31, 2019 at 2:53 PM Reid Kleckner <rnk at google.com> wrote:> On Wed, Jul 31, 2019 at 11:37 AM Vitaly Buka via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> I have no idea how. >> Are there particular problems? Now it should be quite. >> Console has a bunch of stale builders which are even less useful. >> > > LLVM has a silent build master that does not send email. When Nico added > the gn build, apparently we promised not to set up builders that send > email. I searched for info about the silent buildmaster in the zorg > repository, but I found nothing. I added Galina, maybe she can say more > about how to set that up and where its config is managed. >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190731/9ce8fabe/attachment.html>
Vitaly Buka via llvm-dev
2019-Jul-31 19:19 UTC
[llvm-dev] buildbot failure in LLVM on sanitizer-x86_64-linux-gn
I would expect that the value of being able to check the patch, without need to setup local GN build is higher than the cost of possible confusion. I know how to make it always gray on http://lab.llvm.org:8011/console and red/green on http://lab.llvm.org:8014/console. Easy to do but I don't see the benefits of that. And I would not be able to maintain bot on non-llvm master. In order of my preferences I am ready to do the following: 1. Leave as-is 2. Move to 8014 3. Shutdown the bot Any thoughts? On Wed, Jul 31, 2019 at 11:59 AM Nico Weber <thakis at chromium.org> wrote:> It already doesn't send email. Just the bot showing up on > http://lab.llvm.org:8011/console suggests more support than there is for > this build config though (namely, none). And if someone lands something and > watches http://lab.llvm.org:8011/console then that bot turning red might > be confusing. > > If there's no way to hide bots onhttp://lab.llvm.org:8011/console then > that bot should live on a different master. > > On Wed, Jul 31, 2019 at 2:53 PM Reid Kleckner <rnk at google.com> wrote: > >> On Wed, Jul 31, 2019 at 11:37 AM Vitaly Buka via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >> >>> I have no idea how. >>> Are there particular problems? Now it should be quite. >>> Console has a bunch of stale builders which are even less useful. >>> >> >> LLVM has a silent build master that does not send email. When Nico added >> the gn build, apparently we promised not to set up builders that send >> email. I searched for info about the silent buildmaster in the zorg >> repository, but I found nothing. I added Galina, maybe she can say more >> about how to set that up and where its config is managed. >> >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190731/f268617a/attachment.html>