upported through the 19.05 release cycle.
Levi Morrison
On 6/7/19 2:23 AM, Andrés Marín Díaz wrote:
Good morning, thank you very much to all for helping us find the problem.
I join Levi's proposal to reverse the change.
Is there any way to temporarily patch the slurm code 19.05 while
analyzing
ink?) but since it's only just landed...
Levi Morrison
Brigham Young University
[1]:
https://github.com/open-mpi/ompi/commit/7dad74032e30259506da7fa582dd8c4351e6e0a1
[2]:
https://github.com/SchedMD/slurm/commit/d78af893e4a60e933a2319b0c36a0e40c7dd1b02
This enormous amount of breakage for such a minor "gain" seems unwise. I
think this [change][2] should be backed out and converted to a warning
message to allow time for the OpenMPI changes to be backported,
released, and adopted.
Levi Morrison
Brigham Young University
[1]:
https://gith
