-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
linux-libnuma test failing in SLES 12 build root #213
Comments
When I try again with debugging information turned on I get a different error before linux-libnuma (moved to #214).
|
get_last_cpu_location is a completely different function, I am ignoring it here.
then rebuild the test with make -C tests linux-libnuma, and run it manually with tests/linux-libnuma, and report the output. Also please send the file foo.xml generated by lstopo foo.xml so that we know what your machine looks like. |
When I run it again it fails earlier, at hwloc_bitmap_isequal(set, set2). So the additional printf doesn't help. |
Do you have NUMA enabled in your kernel? (grep CONFIG_NUMA /boot/config-*) Otherwise:
|
The host system has
The chroot doesn't have a /boot/config-* file. With /proc mounted it's getting past the first assert. The first printf you suggested is giving:
|
Your lstopo output and the printf says there is a single core ad hyperthread in the chroot, while libnuma says there are two of them. Is the chroot somehow restricted to a single core and hyperthread while the machine actually has two of them? |
I am going to ignore/close this issue since it looks like libnuma doesn't properly report things in that chroot, and I don't think we care about libnuma<->hwloc interoperability regression checks in such an build environment anyway. |
In a SLES 12 build root the linux-libnuma make check test is failing with this output:
linux-libnuma: linux-libnuma.c:70: main: Assertion `numa_bitmask_equal(bitmask, numa_all_nodes_ptr)' failed.
./wrapper.sh: line 14: 25529 Aborted (core dumped) "$@"
This is using hwloc 1.11.4.
The text was updated successfully, but these errors were encountered: