Sourceware - Building Together, Fri 11, 15:00 UTC

Sourceware - Building Together, Fri 11, 15:00 UTC

[Mark Wielaard]

[-- Attachment #1: Type: text/plain, Size: 2520 bytes --]

Hi all,

Tomorrow is the second Friday of the month, so it is time for the
Sourceware Open Office again!

Friday September 11, from 15:00 UTC to 16:00 UTC
On #overseers on irc.libera.chat

$ date -d "Fri Sep 10 15:00 UTC 2026"

Discussion topics about various CI builder buildbots/patchwork/etc:

- Rainer would like to extend the Solaris (amd64 and sparcv9)
  buildbot workers to gdb
  https://inbox.sourceware.org/ydd4iglf9yj.fsf@CeBiTec.Uni-Bielefeld.DE

- DJ would like to run the patchwork CI/CD curator in a Sourceware VM
  https://sourceware.org/glibc/wiki/CICDDesign
  https://gitlab.com/djdelorie/glibc-cicd
  This is also a good opportunity to discuss putting patchwork as a
  whole in its own isolated VM. And to see if we can use some of the
  builder servers/VM to use the curator to do CI builds.
  https://sourceware.org/sourceware-wiki/servers-and-services-2026/

- Should we look into bugspray? A public-inbox bugzilla integrator:
  https://git.kernel.org/pub/scm/utils/bugspray

- An update on funding https://sourceware.org/financials.html

- Builders/CI talk at Cauldron with tips and tricks for having all
  our automated processes (buildbots, try-bots, pre/post-commit-CI/CD,
  snapshots, forgejo runners, patchwork's curator, etc.) working smoothly,
  even in the face of the AI scraperbot attacks, and how to add your own.
https://conf.gnu-tools-cauldron.org/prg26/talk/review/YZDVBNFDPSSZERNAYRYDCS8XWF3BURZC
  The FSF (GNU Toolchain projects fiscal sponsor) and SFC
  (Sourceware fiscal sponsor) will also attend to answer any
  questions on how we are running the community infrastructure
  together with our other partners.

Sourceware relies on cooperation among a broad diversity of core
toolchain and developer tool projects, hackers, organizations,
ideas, and communication styles. The monthly Sourceware Open Office
meetings are one way of coming together as a community and discuss
our shared development infrastructure. For other ways to participate
see https://sourceware.org/mission.html#organization

Keep Sourceware worry-free, friendly and independent by donating
https://sourceware.org/donate.html support our fiscal sponser SFC
https://sfconservancy.org/sustainer and/or support OSUOSL for
hosting Free Software projects https://osuosl.org/donate/

Do you or your company want to sponsor Sourceware financially, donate
hardware or services, then see the Sourceware sponsorship program at
https://sourceware.org/sponsor.html

[-- Attachment #2: so.ics --]
[-- Type: text/calendar, Size: 244 bytes --]

BEGIN:VCALENDAR
VERSION:2.0
CALSCALE:GREGORIAN
BEGIN:VEVENT
DTSTART:20260612T150000Z
DURATION:PT1H
SUMMARY:Sourceware Open Office
LOCATION:#overseers on irc.libera.chat
RRULE:FREQ=MONTHLY;INTERVAL=1;BYDAY=FR;BYSETPOS=2
END:VEVENT
END:VCALENDAR

Re: Sourceware - Building Together, Fri 11, 15:00 UTC

[Zack Weinberg via Gdb]

On Thu, Sep 10, 2026, at 7:58 AM, Mark Wielaard wrote:
> Hi all,
>
> Tomorrow is the second Friday of the month, so it is time for the
> Sourceware Open Office again!

I recognize that this is a meeting about a whole bunch of things and not
just the argument presently taking place on libc-alpha, but I have to
ask that the *topic* of that argument be declared off-topic for this
meeting.  The glibc project is currently trying to dig out from a
catastrophic process failure and we really, really need everyone even
peripherally involved to agree to stick *exclusively* to libc-alpha when
discussing anything related to the question of whether glibc should move
any or all of its hosting off of sourceware.

Thanks for your consideration.
zw

Re: Sourceware - Building Together, Fri 11, 15:00 UTC

[Mark Wielaard]

Hi Zack,

On Thu, 2026-09-10 at 17:45 -0400, Zack Weinberg wrote:
> On Thu, Sep 10, 2026, at 7:58 AM, Mark Wielaard wrote:
> > Tomorrow is the second Friday of the month, so it is time for the
> > Sourceware Open Office again!
> 
> I recognize that this is a meeting about a whole bunch of things and not
> just the argument presently taking place on libc-alpha, but I have to
> ask that the *topic* of that argument be declared off-topic for this
> meeting.  The glibc project is currently trying to dig out from a
> catastrophic process failure and we really, really need everyone even
> peripherally involved to agree to stick *exclusively* to libc-alpha when
> discussing anything related to the question of whether glibc should move
> any or all of its hosting off of sourceware.

No worries. glibc does that every 9 months or so. We really have no
intention to discuss any of that. I really appreciate you trying to
resolve that issue. But it has been going on for so long that most
people just want to get back to work.

The monthly Sourceware Open Office meeting is for simple technical
coordination. In this case about setting up some buildbots (for GDB),
hooking up the patchwork CI/CD curator (and maybe some of the
buildbots). Investigate bugspray, a public-inbox bugzilla integrator. A
quick update on fundraising progress. And discussion of what people to
like hear about for the builders/CI talk at Cauldron since we are
working on those issues anyway. Also it is a great time to ask about
any infrastructure issues you might experience where it helps to have
direct insight into real time logs.

There is also no requirement to attend unless you really could use some
direct admin help.

So see you in #overseers on irc.libera.chat at date -d "Fri Sep 10
15:00 UTC 2026". Or not if you have better things to do with your time.

Cheers,

Mark

Re: Sourceware - Building Together, Fri 11, 15:00 UTC

[Mark Wielaard]

Hi,

On Thu, Sep 10, 2026 at 01:58:41PM +0200, Mark Wielaard wrote:
> Discussion topics about various CI builder buildbots/patchwork/etc:

For those that couldn't attend. Some notes on the topics discussed.

- The sware-gg-bot in #overseers that grants unlimited https access
  has been moved to #sourceware-goodguys. The 429 error page has been
  updated if you still happen to see those.

    Joining the <code>#overseers-goodguys</code> channel directly from
    your host, without a "cloak", should automatically but temporarily
    remediate.

- Claudio fixed the syncing of the gcc-wwwdocs repo (the bot was not
  allowed to push to the gcc- wwwdocs repo)
  Also forge-stage has been updated to the latest forgejo release.

> - Rainer would like to extend the Solaris (amd64 and sparcv9)
>   buildbot workers to gdb
>   https://inbox.sourceware.org/ydd4iglf9yj.fsf@CeBiTec.Uni-Bielefeld.DE

This would reuse the workers already setup for binutils.
And the tricky 32bit-only case if off the table.
Also disabling sim and no targets=all. Only PATH differs.

make check-gdb is clean on solaris? It really only matters for the
reporting, if we have a clear/clean "green" list we can immediately
sent out warning emails Most other builders use a curated list of
tests to run that are known to not fail.  See
https://sourceware.org/cgit/builder/tree/builder/master.cfg#n3752

We'll integrate it with the full make check-gdb list, but disable fail
email reporting for now. Then we'll review the results and see whether
or not to configure the mail reporter.

- A buildbot related question for gcc folks.  A vendor of build
services (incredibuild) has offered free buildbot/build services to
the sourceware fleet, and has an interest in supporting the gcc
project specifically.  They'd welcome suggestions as to architecture,
configuration, target sorts of triplets we should configure for them.
(We would not be running any of their software on sourceware or
nearby; they'd be running build/tests on their own hw/sw as a
community donor).  Please let fche and/or buildbot@sourceware.org know
of any suggestions or concerns.

Richard suggested looking into glibc's scripts/build-many-glibcs.py

> - DJ would like to run the patchwork CI/CD curator in a Sourceware VM
>   https://sourceware.org/glibc/wiki/CICDDesign
>   https://gitlab.com/djdelorie/glibc-cicd
>   This is also a good opportunity to discuss putting patchwork as a
>   whole in its own isolated VM. And to see if we can use some of the
>   builder servers/VM to use the curator to do CI builds.
>   https://sourceware.org/sourceware-wiki/servers-and-services-2026/

Agreed on https://patchwork.sourceware.org/cicd/curator.cgi as
canonical URL. This must be stable because runners will connect to it.
It can be a simple single-url proxy from an apache server to a hidden
internal curator instance. The curator is one python script that runs
four or so processes and talks to mariadb.  It can run anywhere.

mjw would like to take this oppertunity to create a new patchwork VM
and stuff everything in there. We already reserved space for it 4
vcores, 12GB mem, 30GB disk (double checked that is enough).

But some pushback to that and some discussion about whether to run in
containers instead and the maintenance cost of each option. In the end
decided it really is three separate tasks. That shouldn't be handled
in one big bang. So for now we'll simply would be to have it isolated
as separate user on vm01 (possibly in its own container). After that
works we can see about additional steps and/or a separate VM.

For the trybots (buildbots) it is suggesting that they run on
"corporate branded" hardware as advertisement for other companies to
donate more hardware (or run their own). There is a collection of
those here https://builder.sourceware.org/#thanks:~:text=Thanks

> - Should we look into bugspray? A public-inbox bugzilla integrator:
>   https://git.kernel.org/pub/scm/utils/bugspray

Yes, but time ran out.

> - An update on funding https://sourceware.org/financials.html

Numbers for Augustus, $400+ private donations that month, still have
to see how much of that is recurring. The first Supply Chain Defender
corporate sponsor Open Source Security, Inc. $5000 has been fully
processed. Others still in progress, vacations, purchase orders, other
processes take a lot of time.

> - Builders/CI talk at Cauldron with tips and tricks for having all
>   our automated processes (buildbots, try-bots, pre/post-commit-CI/CD,
>   snapshots, forgejo runners, patchwork's curator, etc.) working smoothly,
>   even in the face of the AI scraperbot attacks, and how to add your own.
> https://conf.gnu-tools-cauldron.org/prg26/talk/review/YZDVBNFDPSSZERNAYRYDCS8XWF3BURZC
>   The FSF (GNU Toolchain projects fiscal sponsor) and SFC
>   (Sourceware fiscal sponsor) will also attend to answer any
>   questions on how we are running the community infrastructure
>   together with our other partners.

All the above give some good input into what might be interesting to
talk about.