Re: test-lock failure on NetBSD 10

2024-06-27 Thread Collin Funk
Bruno Haible writes: > Hope you can debug it. I can't — when I give 8 CPUs to my NetBSD VM, > I can't log in to the console any more because every keystroke is repeated > 3 or 4 times. I'll try to come up with a fix sometime tomorrow or this weekend. Upon first glace I see that NetBSD uses the f

Re: test-lock failure on NetBSD 10

2024-06-27 Thread Bruno Haible
Collin Funk wrote: > $ time ./gltests/test-pthread-once2 > Starting test_once ... OK > > real 8m6.167s > user 56m55.342s > sys 7m44.460s > > $ time ./gltests/test-call_once2 > Starting test_once ...Alarm clock > > real 10m4.626s > user 71m5.161s > sys 9m31.302s So, there is definitely a

Re: test-lock failure on NetBSD 10

2024-06-27 Thread Collin Funk
Collin Funk writes: >> Then, you might see whether setting ENABLE_DEBUGGING to 1 in the test's >> code reveals a pattern... > > Thanks for the advice. I'll do some experimenting and let you know what > I find. >> $ time ./test-pthread-once1 $ time ./gltests/test-pthread-once1 real0m0.00

Re: test-lock failure on NetBSD 10

2024-06-27 Thread Collin Funk
Bruno Haible writes: > Collin Funk wrote: >> I created the virtual machine with 8 cores and 8 GB memory. > > Ah, this explains why I never saw this: I create most of my VMs with 1 CPU > (so that I can run a dozen of them in parallel). Haha. I use a different strategy I guess. One virtual machine

Re: test-lock failure on NetBSD 10

2024-06-27 Thread Bruno Haible
Collin Funk wrote: > > * tell how many threads your machine supports? > > I created the virtual machine with 8 cores and 8 GB memory. Ah, this explains why I never saw this: I create most of my VMs with 1 CPU (so that I can run a dozen of them in parallel). > > test-pthread-mutex > > $ time .