Yes, if it's in the 3.0.x nightly snapshot tarball, it will be in the v3.0.1
release.
> On Mar 10, 2018, at 7:52 PM, Alan Wild wrote:
>
> I can report that that openmpi-v3.0.x-201803060306-c79e33b.tar.gz doesn’t
> show the problem.
>
> I also reran all of the osu benchmarks and performance
I can report that that openmpi-v3.0.x-201803060306-c79e33b.tar.gz doesn’t
show the problem.
I also reran all of the osu benchmarks and performance was general in-line
with my 3.0.0 and 3.0.1rc3 builds.
Any chance of the fix making the 3.0.1 release (or a minimal recommend
patch I can apply to 3.0
Specifically, Nathan is referring to:
https://www.open-mpi.org/nightly/v3.0.x/
> On Mar 9, 2018, at 12:51 PM, Nathan Hjelm wrote:
>
> Fixed in master and I'm the 3.0.x branch. Try the nightly tarball.
>
> On Mar 9, 2018, at 10:01 AM, Alan Wild wrote:
>
>> I’ve been running the OSU micr
Fixed in master and I'm the 3.0.x branch. Try the nightly tarball.
> On Mar 9, 2018, at 10:01 AM, Alan Wild wrote:
>
> I’ve been running the OSU micro benchmarks (
> http://mvapich.cse.ohio-state.edu/benchmarks/ ). on my various MPI
> installations. One test that has been consistently faili
