As mentioned in the Debian bug [1], the 'make check' in liburcu is more akin to a benchmark and memtest-like conformance test, rather than actual unit tests. It can take many hours to run on a typical desktop, and even longer on build VMs, which is why they were disabled in the Debian package.
I opened [2] with upstream to have them move those out of the 'make check'.
As mentioned in the Debian bug [1], the 'make check' in liburcu is more akin to a benchmark and memtest-like conformance test, rather than actual unit tests. It can take many hours to run on a typical desktop, and even longer on build VMs, which is why they were disabled in the Debian package.
I opened [2] with upstream to have them move those out of the 'make check'.
[1] http:// bugs.debian. org/cgi- bin/bugreport. cgi?bug= 718409 /bugs.lttng. org/issues/ 611
[2] https:/