Hi, another update:
On Wed, Jun 11, 2025 at 09:24:24PM +0200, Michael Banck wrote: > So it seems the low-resolution timer is the only functional issue right > now. I upgraded my VM to current Debian unstable, but unfortunately that > did not increase the timer resolution is hoped, maybe some more pieces > in glibc are missing, I checked in on that[1]. In any case, they are > actively working on this. I got it working, I had to rebuild gnumach with --enable-apic in order to get HPET. With that, the regular build-farm checks (check/ installcheck in contrib, src/test/regress and src/test/isolation) pass without patches to testsuite timings. > However, there is another caveat: > > Running "make check" manually only sometimes hangs the VM (without any > output anywhere), while running it via the buildfarm client reliably > makes it hang each time, so I added --tests=test_setup as a work-around > to test the other stages. I have not found a reason for this yet, I will > try to get a serial console working for the VM next, maybe that will > show some helpful info. This was due to the build-farm running on HEAD with a config including debug_parallel_query=on, which adds a lot of strain on the machine I guess? As this is a single-node VM, I guess it overloaded it regularly. I reported that and I think this is something that needs to be addressed, but people are working on similar issues right now[1]. Is removing the debug_parallel_query=on configuration for HEAD a valid mode of operation for a buildfarm animal? I ran the tests 10 times in a row without issues today. Michael [1] https://lists.debian.org/debian-hurd/2025/05/msg00031.html https://lists.debian.org/debian-hurd/2025/05/msg00031.html
