Donating an experimental accelerated GCC Buildbot worker
Yossi Eliaz
yossi.eliaz@incredibuild.com
Mon Aug 17 14:26:13 GMT 2026
Hi Frank and Nir,
I wanted to follow up on this and see how we can move forward. What is your
availability this week or early next week for a brief 15-minute call?
Best regards,
Yossi
On Thu, Jul 9, 2026 at 9:41 AM Nir Stern <nir.stern@incredibuild.com> wrote:
> Thanks for the intro, Yossi and nice to meet you, Frank.
> We'll be in touch once we have an update.
>
> Nir.
>
> On Wed, Jul 8, 2026 at 6:35 PM Yossi Eliaz <yossi.eliaz@incredibuild.com>
> wrote:
>
>> Hi Frank,
>>
>> Thank you for the positive feedback and for sharing the details about the
>> existing builders and the Bunsen metadata collection. That sounds great.
>>
>> I am loop in our VP of Product, Nir Stern, to help further explore this
>> collaboration. It will take some time and effort on our end, but we are
>> committed to making this happen.
>>
>> Best regards,
>> Yossi
>>
>> On Wed, Jul 8, 2026 at 18:33 Frank Ch. Eigler <fche@elastic.org> wrote:
>>
>>> Hi -
>>>
>>> > I am Yossi from Incredibuild. We would like to donate experimental
>>> > x86_64 Linux workers to the existing Sourceware Buildbot setup for
>>> GCC.
>>>
>>> Awesome!
>>>
>>> > [...]
>>> > We can start with a non-voting, experimental worker that we will
>>> > maintain on our side.
>>>
>>> That's fine.
>>>
>>> > A primary target could be a full GCC bootstrap testsuite run:
>>> > make bootstrap
>>> > make -k check
>>>
>>> Looking at master/master.cfg from https://sourceware.org/git/builder.git
>>> ,
>>> it seems like "gcc_full_build_factory_gen", as used by the "gcc-full-*"
>>> or "gcc-fullest-*" builders are in a similar category. The more
>>> builders the better, but especially cool if they bring some variation
>>> in terms of architecture or operating system.
>>>
>>> > Before connecting the infrastructure, we will share a short
>>> technical
>>> > report detailing the exact host, distro, GCC revision, configure
>>> flags,
>>> > wall-time numbers, and test-result diffs compared to a normal
>>> baseline.
>>>
>>> Nice. It turns out that the way our buildbots are driven from the
>>> sourceware master, much of this sort of metadata is automatically
>>> collected and saved into a bunsen instance for later recall &
>>> analysis (including via an MCP server). That way the info is up
>>> to date even with changes on your end.
>>>
>>>
>>> - FChE
>>> IRONSCALES couldn't recognize this email as this is the first time you
>>> received an email from this sender fche @ elastic.org
>>>
>>> Hi -
>>>
>>> > I am Yossi from Incredibuild. We would like to donate experimental
>>> > x86_64 Linux workers to the existing Sourceware Buildbot setup for GCC.
>>>
>>> Awesome!
>>>
>>> > [...]
>>> > We can start with a non-voting, experimental worker that we will
>>> > maintain on our side.
>>>
>>> That's fine.
>>>
>>> > A primary target could be a full GCC bootstrap testsuite run:
>>> > make bootstrap
>>> > make -k check
>>>
>>> Looking at master/master.cfg from https://sourceware.org/git/builder.git
>>> ,
>>> it seems like "gcc_full_build_factory_gen", as used by the "gcc-full-*"
>>> or "gcc-fullest-*" builders are in a similar category. The more
>>> builders the better, but especially cool if they bring some variation
>>> in terms of architecture or operating system.
>>>
>>> > Before connecting the infrastructure, we will share a short technical
>>> > report detailing the exact host, distro, GCC revision, configure flags,
>>> > wall-time numbers, and test-result diffs compared to a normal baseline.
>>>
>>> Nice. It turns out that the way our buildbots are driven from the
>>> sourceware master, much of this sort of metadata is automatically
>>> collected and saved into a bunsen instance for later recall &
>>> analysis (including via an MCP server). That way the info is up
>>> to date even with changes on your end.
>>>
>>>
>>> - FChE
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://sourceware.org/pipermail/buildbot/attachments/20260817/c7d7ab73/attachment.htm>
More information about the Buildbot
mailing list