Hi Kilian, Thanks for your reply. Indeed, passing '--hpx:ignore-batch-env --hpx:localities=[N]' gets rid of the warning messages. Great! You mention this only works when using a single locality per node, but it seems to work in my case with 8 localities on a single node as well. Or do I misunderstand you maybe?
OTF2 still has issues writing the trace, unfortunately. The same error messages are printed: [OTF2] src/otf2_archive_int.c:1108: error: Unknown error code: Couldn't create directories on root. I noticed they are printed 7 times, so it seems one process is able to write its trace, while the other 7 are not. This confirms John's remark that "Ranks 1-N-1 try to create the otf files and clobber each other". Kor On 9/3/21 3:55 PM, Kilian Werner wrote: > Hi Kor, > > regarding the SLURM error there is a workaround that I was taught in > this issue: https://github.com/STEllAR-GROUP/hpx/issues/4297 > > ./application --hpx:ignore-batch-env --hpx:localities=[N] > > Where [N] is the number of nodes you use (works only for one locality > per node). This should get rid of the "every locality thinks its rank 0" > problem. Please let me know if it works and the two issues were indeed > related. > > Kind regards, > > Kilian _______________________________________________ hpx-users mailing list [email protected] https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
