Re: Dedicated hurd-amd64 build/test lab: staged results and delivery preferences
jbranso--- via Bug reports for the GNU Hurd <[email protected]> Sat, 25 Jul 2026 21:39:13 +0000
| Newsgroups | gmane.os.hurd.bugs |
|---|---|
| Message-ID | <[email protected]> |
July 25, 2026 at 3:51 PM, "Federico Bonino" <[email protected] mailto= :[email protected]?to=3D%22Federico%20Bonino%22%20%3Cbuzondefede%40gm= ail.com%3E > wrote: >=20 >=20Hello GNU Hurd team, >=20 >=20As a long-time subscriber to help-hurd mail list, I have followed the= project's steady progress with deep respect and am very happy to finally= have the opportunity to contribute directly toward accelerating GNU Hurd= . >=20 >=20I run a small, dedicated hardware-backed build and testing lab focuse= d on the Debian hurd-amd64 port gap. The lab pairs a dedicated compute ho= st with an iterating coding agent that performs the repetitive legwork --= scraping build failures, running native=C2=A0builds, triaging failures, = and isolating minimal reproducers -- under my direct (human) accountabili= ty :) What hareware are you using? Are you testing this on read hardware? =20 >=20Inspired by Brent Baccala's work highlighted in your Q1-2026 news upd= ate -- debugging x86_64 SMP issues alongside an AI assistant -- I adopted= the same collaborative model here. The agent accelerates the time-consum= ing build triage, failure analysis, and reproducer minimization, while I = remain fully accountable for every finding and patch. Everything is human= -curated and reviewed before reaching the list, ensuring zero noise=C2=A0= and maximum signal for the maintainers. >=20 >=20The guiding principle is to maximize merged value while consuming as = little maintainer review bandwidth as possible. To that end, the lab has = built and staged a bank of verified results, datasets, and minimal reprod= ucers: >=20 >=201. Debian hurd-amd64 Portability Bank (For Debian BTS / Upstream): > =C2=A0- 14 package portability fixes built green on native Hurd (e.g. m= sc-generator,=C2=A0pgstat, postgresql-18-age, barvinok, modsecurity-apach= e, iptux). > =C2=A0- 3 of these have been verified against full Debian integration s= uites (autopkgtest PASS). > =C2=A0- Fixes focus on clean, upstream-acceptable #if defined(__GNU__) = guard widening or=C2=A0dynamic memory allocation replacing hardcoded PATH= _MAX limits. >=20 >=202. GNU Mach SMP Storage-Initialization Hang Differential (Kernel / Ma= ch): > =C2=A0- A clean, reproducible 4-configuration matrix on gnumach-image-1= -amd64-smp showing=C2=A0a storage-initialization hang during rumpdisk PCI= /IRQ setup on both PIIX3 and=C2=A0q35/AHCI controllers (where UP kernels = progress further). > =C2=A0- Recorded with exact environment specs, GRUB entry paths, and sc= reendumps. >=20 >=203. GHC Interface & Dynamic File Corruption Dataset (Subsystem Researc= h): > =C2=A0- A measured dataset across shipped corrupt Haskell packages (.dy= n_hi interface=C2=A0files and .dynstr string tables) and a standalone ELF= /.hi detector script. > =C2=A0- Empirical statistical analysis showing that 16-byte zero runs i= n shipped binaries=C2=A0cluster heavily at 4 KiB page ends (offset mod 40= 96 =3D 4080), providing concrete=C2=A0data supporting the page-boundary w= rite-back hypothesis discussed on this list. >=20 >=20The lab and its compute resources are fully at the maintainers' dispo= sal, strictly on the terms preferred by the team. >=20 >=20Before submitting individual patches or reports, a few quick question= s: > - First and foremost: Do you agree with this collaborative model, and d= o you welcome=C2=A0this lab's assistance in triaging build failures and i= solating reproducers for GNU Hurd? Sure! Sounds awesome! > - If so, **which channel and format do you prefer** for receiving these= deliverables?=C2=A0(e.g., individual Debian BTS bug reports tagged 'hurd= ' for package fixes, email=C2=A0threads on bug-hurd for core kernel/Mach = issues, or git format-patch emails?) > - What delivery cadence works best for your review capacity? These other questions are probably better answered by the hurd developers= , but you may always give us updates in the irc channel! > The workflow can be easily tailored to whatever best fits the maintaine= rs' needs. >=20 >=20Thank you for your incredible work on GNU Hurd! >=20 >=20Best regards, > Federico Bonino > Fede654 https://github.com/fede654 >