You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by Eric Erhardt <Er...@microsoft.com.INVALID> on 2019/07/11 13:34:02 UTC
RE: New CI system: Ursabot
My apologies if this is already covered in the docs, but I couldn't find it.
How do I re-run a single leg in the Ursabot tests? The 'AMD64 Debian 9 Rust 1.35' failed on my PR, and I wanted to try re-running just that leg, but the only option I found was to re-run all Ursabot legs.
Eric
-----Original Message-----
From: Krisztián Szűcs <sz...@gmail.com>
Sent: Friday, June 14, 2019 9:48 AM
To: dev@arrow.apache.org
Subject: New CI system: Ursabot
Hello All,
We're developing a buildbot application to utilize Ursa Labs’
physical machines called Ursabot. Buildbot [1] is used by major open source projects, like CPython and WebKit [2].
The source code is hosted at [3], the web interface is accessible at [4]. The repository contains a short guide about the goals, implementation and the interfaces we can drive ursabot. The most notable way to trigger ursabot builds is via sending github comments mentioning @ursabot machine account, for more see [5].
Currently we have builders for the C++ implementation and the Python bindings on AMD64 and ARM64 architectures.
It is quite easy to attach workers to the buildmaster [7], so We can scale our build cluster to test and run on-demand builds (like benchmarks, packaging tasks) on more platforms.
Yesterday we've enabled the github status push reporter to improve the visibility of ursabot, although we were testing the builders in the last couple of weeks. I hope no one has a hard objection against this new CI. Arrow has already started to outgrow Travis-CI and Appveyor's capacity and we're trying to make the build system quicker and more robust.
Please don't hesitate to ask any questions!
Thanks, Krisztian
[1]: https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbuildbot.net%2F&data=02%7C01%7CEric.Erhardt%40microsoft.com%7C7df1445a86f747c3db9608d6f0d75462%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636961204963990536&sdata=CX7t5kh2wLH%2BHYZq%2BwMG3cGIeg1ZHx%2BDHnGqlyRw81g%3D&reserved=0
[2]: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbuildbot%2Fbuildbot%2Fwiki%2FSuccessStories&data=02%7C01%7CEric.Erhardt%40microsoft.com%7C7df1445a86f747c3db9608d6f0d75462%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636961204963990536&sdata=vxbos9e%2BrJi7ZBIoqjUNbyj2Xmlfpj9JxsFbDc1CXrI%3D&reserved=0
[3]: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fursa-labs%2Fursabot&data=02%7C01%7CEric.Erhardt%40microsoft.com%7C7df1445a86f747c3db9608d6f0d75462%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636961204963990536&sdata=77aMN03BotaAVZM4LhI1ER4lkEqVrYb%2B848yvELq%2BEk%3D&reserved=0
[4]: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.ursalabs.org&data=02%7C01%7CEric.Erhardt%40microsoft.com%7C7df1445a86f747c3db9608d6f0d75462%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636961204963990536&sdata=JKLOOems6daX9OQGfZwsjxuvdYXxuM9Pj3r7BR869fg%3D&reserved=0
[5]: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fursa-labs%2Fursabot%23driving-ursabot&data=02%7C01%7CEric.Erhardt%40microsoft.com%7C7df1445a86f747c3db9608d6f0d75462%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636961204964000528&sdata=x5oOrTOeedkfmvP9K9R4FYZZnR3jD1A7Q%2F5Qu8EC7M8%3D&reserved=0
[7]: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fursa-labs%2Fursabot%2Fblob%2Fmaster%2Fdefault.yaml%23L115&data=02%7C01%7CEric.Erhardt%40microsoft.com%7C7df1445a86f747c3db9608d6f0d75462%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636961204964000528&sdata=FoqVfr4RPDmhEXxXWOK%2BUchzwm5mTv8tsN4nSrjKggQ%3D&reserved=0
Re: New CI system: Ursabot
Posted by Krisztián Szűcs <sz...@gmail.com>.
Hi Eric!
On Thu, Jul 11, 2019 at 3:34 PM Eric Erhardt
<Er...@microsoft.com.invalid> wrote:
> My apologies if this is already covered in the docs, but I couldn't find
> it.
>
> How do I re-run a single leg in the Ursabot tests? The 'AMD64 Debian 9
> Rust 1.35' failed on my PR, and I wanted to try re-running just that leg,
> but the only option I found was to re-run all Ursabot legs.
>
Currently you can't restart a single builder, just the whole buildset.
There is a ticket about supporting @ursabot build <buildername>
command and another ticker to provide control access for apache
members. Once the latter one is set up, I can also grant access
for contributors outside of apache.
BTW I think you can safely ignore the rust failure because it uses
the nightly toolchain.
>
> Eric
>
> -----Original Message-----
> From: Krisztián Szűcs <sz...@gmail.com>
> Sent: Friday, June 14, 2019 9:48 AM
> To: dev@arrow.apache.org
> Subject: New CI system: Ursabot
>
> Hello All,
>
> We're developing a buildbot application to utilize Ursa Labs’
> physical machines called Ursabot. Buildbot [1] is used by major open
> source projects, like CPython and WebKit [2].
>
> The source code is hosted at [3], the web interface is accessible at [4].
> The repository contains a short guide about the goals, implementation and
> the interfaces we can drive ursabot. The most notable way to trigger
> ursabot builds is via sending github comments mentioning @ursabot machine
> account, for more see [5].
>
> Currently we have builders for the C++ implementation and the Python
> bindings on AMD64 and ARM64 architectures.
> It is quite easy to attach workers to the buildmaster [7], so We can scale
> our build cluster to test and run on-demand builds (like benchmarks,
> packaging tasks) on more platforms.
>
> Yesterday we've enabled the github status push reporter to improve the
> visibility of ursabot, although we were testing the builders in the last
> couple of weeks. I hope no one has a hard objection against this new CI.
> Arrow has already started to outgrow Travis-CI and Appveyor's capacity and
> we're trying to make the build system quicker and more robust.
>
> Please don't hesitate to ask any questions!
>
> Thanks, Krisztian
>
> [1]:
> https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbuildbot.net%2F&data=02%7C01%7CEric.Erhardt%40microsoft.com%7C7df1445a86f747c3db9608d6f0d75462%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636961204963990536&sdata=CX7t5kh2wLH%2BHYZq%2BwMG3cGIeg1ZHx%2BDHnGqlyRw81g%3D&reserved=0
> [2]:
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbuildbot%2Fbuildbot%2Fwiki%2FSuccessStories&data=02%7C01%7CEric.Erhardt%40microsoft.com%7C7df1445a86f747c3db9608d6f0d75462%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636961204963990536&sdata=vxbos9e%2BrJi7ZBIoqjUNbyj2Xmlfpj9JxsFbDc1CXrI%3D&reserved=0
> [3]:
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fursa-labs%2Fursabot&data=02%7C01%7CEric.Erhardt%40microsoft.com%7C7df1445a86f747c3db9608d6f0d75462%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636961204963990536&sdata=77aMN03BotaAVZM4LhI1ER4lkEqVrYb%2B848yvELq%2BEk%3D&reserved=0
> [4]:
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.ursalabs.org&data=02%7C01%7CEric.Erhardt%40microsoft.com%7C7df1445a86f747c3db9608d6f0d75462%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636961204963990536&sdata=JKLOOems6daX9OQGfZwsjxuvdYXxuM9Pj3r7BR869fg%3D&reserved=0
> [5]:
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fursa-labs%2Fursabot%23driving-ursabot&data=02%7C01%7CEric.Erhardt%40microsoft.com%7C7df1445a86f747c3db9608d6f0d75462%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636961204964000528&sdata=x5oOrTOeedkfmvP9K9R4FYZZnR3jD1A7Q%2F5Qu8EC7M8%3D&reserved=0
> [7]:
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fursa-labs%2Fursabot%2Fblob%2Fmaster%2Fdefault.yaml%23L115&data=02%7C01%7CEric.Erhardt%40microsoft.com%7C7df1445a86f747c3db9608d6f0d75462%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636961204964000528&sdata=FoqVfr4RPDmhEXxXWOK%2BUchzwm5mTv8tsN4nSrjKggQ%3D&reserved=0
>