Closed bmwiedemann closed 5 years ago
Hi,
Indeed, the test was broken with CORES=1. I just pushed a fix, can you confirm it now works for you ?
Thanks !
With commit fd55609ca74c610285abe519babdf71f5a31e195 the test passes now.
However, it is not obvious if the changed value of line 7 also applied to line 4's local_lock[CORES / 2]
A quick test with gcc -E
shows that it does, but would have been nice to have it more obvious.
You're right, I'll move it before line 4
For reference: fa63a9517403f74d89f874744f889c5478d5d607
looks good. Will there be a new release before 2020 or should I consider to add the patch to our package?
I can't tell for sure, but given the low number of commits done since last release, if I were you I wouldn't expect a new release before 2020.
Thank you. I submitted the fix as a patch to openSUSE.
While working on reproducible builds for openSUSE, I found that the
ck_hclh
test gets stuck forever on 1-CPU (KVM) buildsSteps to reproduce on openSUSE or Debian:
Version: ck-0.6.0 ; same problem with 0.7.0