Hi,

On irc Simon requested a python black formatting step for the gdb
buildbot. And I saw Tom just fixed the last few formatting issues. So
I added a "gdb black step" to the gdb-fedora-x86_64 builder (it seems
fine to just run this on one builder instead on all - 19 now! - gdb
builders).

It currently succeeds:
https://builder.sourceware.org/buildbot/#/builders/74/builds/721/steps/5/logs/stdio

And it will sent email if it detects a python file under gdb that it
would reformat.

Note that it will also run for a user try branch, so if you don't have
black locally installed, but want to know if the buildbot would flag
some new python code you can submit a job:

- git checkout -b python-frob
- hack, hack, hack... OK, looks good to submit
- git commit -a -m "Awesome python hack"
- git push origin python-frob:users/mark/try-python-frob
- ... wait for the emails to come in or watch buildbot logs ...

If there are any other jobs that would be beneficial to run on the gdb
sources please let us know, On irc I suggested running ARI
(A.R. Index), but it seem ARI isn't super popular. Also it wouldn't
really be clear what "success" means for an ARI run, or how to report
the results in a useful way.

Cheers,

Mark

BTW. For those coming (virtually) to Cauldron Frank and I will run a little
BoF to discuss how to make these things better and/or more useful.
https://gcc.gnu.org/wiki/cauldron2022

Title: BoF - Sourceware GNU Toolchain Infrastructure and beyond

Presenters: Mark Wielaard and Frank Eigler

Abstract: The Sourceware infrastructure is continually improving. Just
like our other services, such as bugzilla, mailinglists and git repos,
we like to provide zero maintenance infrastructure for tracking and
automation of patches, testing and analyzing testresults. This BoF is
for everybody who likes to discuss (and wants to help with) automating
the infrastructure to make contributing to our projects more fun and
more productive.

Topics to discuss include the shared buildbot [1]. Whether we need
more/other arches/distro support. Which builders are most beneficial
to projects. How buildbot should report issues. Whether to use the
buildbot to automate other tasks like updating documentation,
websites, generate release tars or updating bugzilla. How to use git
user try branches. Taking advantage of the Bunsen [2] testrun cluster
analysis, per-testrun testcase search/browse engines, search
operators, testsuite summary (vs detail) grids. Patch tracking using
patchwork [3] integrated with buildbot and the CICD trybot [4]. How to
use the sourcehut mirror [5]. And anything else that would make you
more productive and happy contributing.

[1] https://builder.sourceware.org/
[2] https://builder.sourceware.org/testruns/
[3] https://patchwork.sourceware.org/
[4] https://sourceware.org/glibc/wiki/CICDDesign.
[5] https://sr.ht/~sourceware/