A test of Friday night's trunk tarball is failing in the same manner.
So, the CMR isn't the issue - the problem was never (fully?) fixed in trunk.
On Fri, Feb 7, 2014 at 9:06 PM, Paul Hargrove <phhargrove_at_[hidden]> wrote:
> I tested the 1.7 tarball tonight.
> Jeff had indicated (
> http://www.open-mpi.org/community/lists/devel/2014/01/13785.php) that the
> problem I had reported w/ opal_path_nfs() and EPERM had been fixed in the
> Trac ticket #4125 indicated the fix was CMRed to v1.7
> However, I still see the problem:
> Failure : Mismatch: input "/users/course13/.gvfs", expected:0 got:1
> Failure : Mismatch: input "/users/steineju/.gvfs", expected:0 got:1
> SUPPORT: OMPI Test failed: opal_path_nfs() (2 of 20 failed)
> FAIL: opal_path_nfs
> I don't currently know if the problem was every fixed on the trunk, but
> should know by morning.
> Paul H. Hargrove PHHargrove_at_[hidden]
> Future Technologies Group
> Computer and Data Sciences Department Tel: +1-510-495-2352
> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
Paul H. Hargrove PHHargrove_at_[hidden]
Future Technologies Group
Computer and Data Sciences Department Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900