Le 01/10/2018 à 19:22, Marco Atzeri a écrit : > >> Unfortunately that test script isn't easy to debug in the v2.x branch. >> If that OpenProcess is where things fail, I assume that the line that >> fails is "lstopo --ps". On MinGW, that code is ignored because /proc >> doesn't exist. Does /proc exist on Cygwin? If so, we should just disable >> that test line on Windows. > > /proc exists but windows calls of course are not aware of it. > The failing message in German is coming from the Windows layer, > as my Cygwin enviroment is in English.
Actually the error message comes from lstopo itself. We list PIDs from /proc and then pass them to OpenProcess, which likely fails for administrator processes. And we abort() instead of returning an error. I guess things could work but we'd need to setup a cygwin here for testing, so it'll take some time. > >>> >>> ############################################################ >>> >>> And all the : >>> >>> FAIL: Intel-Skylake-2xXeon6140.output >>> FAIL: Intel-Broadwell-2xXeon-E5-2650Lv4.output >>> FAIL: Intel-Haswell-2xXeon-E5-2680v3.output >>> FAIL: Intel-IvyBridge-12xXeon-E5-4620v2.output >>> FAIL: Intel-SandyBridge-2xXeon-E5-2650.output >>> FAIL: Intel-Westmere-2xXeon-X5650.output >>> FAIL: Intel-Nehalem-2xXeon-X5550.output >>> FAIL: Intel-Penryn-4xXeon-X7460.output >>> FAIL: Intel-Core-2xXeon-E5345.output >>> FAIL: Intel-KnightsLanding-XeonPhi-7210.output >>> FAIL: Intel-KnightsCorner-XeonPhi-SE10P.output >>> FAIL: AMD-17h-Zen-2xEpyc-7451.output >>> FAIL: AMD-15h-Piledriver-4xOpteron-6348.output >>> FAIL: AMD-15h-Bulldozer-4xOpteron-6272.output >>> FAIL: AMD-K10-MagnyCours-2xOpteron-6164HE.output >>> FAIL: AMD-K10-Istanbul-8xOpteron-8439SE.output >>> FAIL: AMD-K8-SantaRosa-2xOpteron-2218.output >>> FAIL: AMD-K8-SledgeHammer-2xOpteron-250.output >>> FAIL: Zhaoxin-CentaurHauls-ZXD-4600.output >>> FAIL: Zhaoxin-Shanghai-KaiSheng-ZXC+-FC1081.output >>> ########################################################### >>> >>> But it is not clear to me how these tests should pass. >>> >>> The Laptop has a Quad Core I5 >> >> These tests use a tarball of the output of the cpuid instruction to >> emulate calling cpuid on those platforms. >> Go to tests/hwloc/xml, unpack one of the tarballs, and run >> "/path/to/utils/lstopo/lstopo -i <path/to/the/extracted/subdir>", you >> should get more information about what's failing when reading these >> dumped cpuid outputs. >> If it doesn't work tests/hwloc/xml/Intel-Skylake-2xXeon6140.output.log >> will show the difference between the expected and obtained topology when >> exported to XML. > > I saw the difference, and as my machine is different from > everyone on the list none of the tests can pass. Your own machine doesn't matter. None is these tests look at your CPU or topology. *All* of them on all x86 machines. CPUID are emulated by reading files, nothing is read from your local machine topology. There's just something wrong here that prevents these emulating CPUID files from being read. "lstopo -i ..." will tell you. Brice _______________________________________________ hwloc-devel mailing list hwloc-devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/hwloc-devel
