I think that's a great idea; I was planning to do it but life's been in my way recently, so please do go ahead!
Just so my mental notes are written down here, I was pondering whether it's worth trying to combine the new patch with the existing riscv64 patch somehow (an environment variable of arches to skip for tsan tests, perhaps?) because the patch ordering/interaction is probably going to be heinous otherwise, but I don't feel strongly about it if you want to do the work in a different way. 👍 We can technically also exclude tests directly via a (singular combined) test name regex on the upstream test runner, but that's a whole different kind of painful, especially if this need grows over time and given the conditional nature of it. ❤️, - Tianon On Mon, Feb 9, 2026, 01:45 Dr. Tobias Quathamer <[email protected]> wrote: > Hi Tianon, > > I'm wondering if it would be sensible to disable the failing test on > s390 for now -- like you've already said in the github issue. With that > workaround, the golang compiler could migrate to testing, fixing a lot > of CVEs. > > What do you think? > > Regards, > Tobias >
