Re: a pthread_cond_timedwait bug

> * tests/virtualbox.h: New file. This produces compiler warnings on non-Linux platforms. Fixed through: 2024-06-30 Bruno Haible tests: Avoid warning "is_running_under_virtualbox defined but not used". * tests/virtualbox.h (is_running_under_virtualbox): Mark as possibly

Re: a pthread_cond_timedwait bug

I wrote: > I turned to the VirtualBox settings, more precisely to the > "Paravirtualization" > acceleration setting. Result: > Default, KVM -> test fails occasionally (about 1 in 3 > times) > None, Legacy, Minimal, Hyper-V -> test succeeds (no failure in 20 runs) The test-p

Re: a pthread_cond_timedwait bug

Hi Bruno, Bruno Haible writes: > The suspicion thus moved to the hypervisor. I tried a couple of VMs under > QEMU (with '-smp 8' for 8 CPUs, and on x86_64 with '-enable-kvm'), and > there the test succeeds. Unrelated to the test, but you might like 'virt-manager' for setting up KVM virtual mach

Re: a pthread_cond_timedwait bug

I wrote: > Even though the futex was supposed to time out at 1719588805.808799 > it terminated only at 1719588806.863658 > which is more than 1 second too late. > > It seems that this is the same bug as > . Wrong

a pthread_cond_timedwait bug

While testing a 'pthread-rwlock' testdir on various VMs with 8 CPUs, there was also a failure of 'test-pthread-cond' on Debian 10. It's reproducible: On that Debian 10.7 VM (glibc 2.28, Linux 4.19.0) with 8 CPUs, 'test-pthread-cond' with a probability of ca. 20%..30% aborts. Stack trace: test-pt