If lstopo fails there, run "hwloc-gather-topology foo" and send foo.tar.bz2
As a workaround for ARMCI, you may try setting
HWLOC_COMPONENTS=no_os,stop in the environment so that hwloc behaves as
if the operating system had no topology support.
Brice
Le 14/09/2018 à 06:11, Jeff Hammond a écrit
All of the job failures have this warning so I am inclined to think they
are related. I don't know what I should expect from lstopo on inside of
AWS, but I guess I'll try it.
I was using the hwloc shipped with the mpich-3.3b1. Talk to the MPICH team
if you want them to upgrade :-)
Jeff
On Thu,
This is actually just a warning. Usually it causes the topology to be
wrong (like a missing object), but it shouldn't prevent the program from
working. Are you sure your programs are failing because of hwloc? Do you
have a way to run lstopo on that node?
By the way, you shouldn't use hwloc 2.0.0rc
I am running ARMCI-MPI over MPICH in a Travis CI Linux instance and
topology is causing it to fail. I do not care about topology in a
virtualized environment. How do I fix this?
* hwloc 2.0.0rc2-git has encountered what
