Skip to content
This repository was archived by the owner on Sep 30, 2022. It is now read-only.

Conversation

@edgargabriel
Copy link
Member

fixes two of the items reported by @dalcini

@bosilca you already were involved in the creation of one of the patches, would you mind quiickly reviewing this?

@mellanox-github
Copy link

Test PASSed.
See http://bgate.mellanox.com/jenkins/job/gh-ompi-release-pr/1625/ for details.

@hppritcha
Copy link
Member

Milestone for this PR?

@edgargabriel
Copy link
Member Author

edgargabriel commented May 8, 2016

bot:milestone:v2.0.0
bot:label:bug

@ompiteam-bot
Copy link

OMPIBot error: Milestone "v2.00" does not exist.

@edgargabriel
Copy link
Member Author

bot:milestone:v2.0.0

@ompiteam-bot ompiteam-bot added this to the v2.0.0 milestone May 8, 2016
@Di0gen
Copy link

Di0gen commented May 9, 2016

bot:retest

@mellanox-github
Copy link

Test FAILed.
See http://bgate.mellanox.com/jenkins/job/gh-ompi-release-pr/1626/ for details.

@lanl-ompi
Copy link
Contributor

Test FAILed.

@jsquyres
Copy link
Member

jsquyres commented May 9, 2016

@jladd-mlnx @Di0gen This is another PR with a failed UCX configure test -- looks like some kind of local error.

@jladd-mlnx
Copy link
Member

@jsquyres I've disabled the UCX check.

@jladd-mlnx
Copy link
Member

bot:retest

@mellanox-github
Copy link

Test FAILed.
See http://bgate.mellanox.com/jenkins/job/gh-ompi-release-pr/1635/ for details.

@Di0gen
Copy link

Di0gen commented May 10, 2016

bot:retest

@mellanox-github
Copy link

Test FAILed.
See http://bgate.mellanox.com/jenkins/job/gh-ompi-release-pr/1637/ for details.

@jsquyres
Copy link
Member

Now the mindist test is failing.

@Di0gen Is there a way to get Jenkins to report each failure -- i.e., export the results into the Jenkins-native format so that it can just show which tests passed / failed (vs. an all-or-nothing result for the entire thing)?

@bosilca
Copy link
Member

bosilca commented May 10, 2016

👍

@jsquyres jsquyres merged commit 0bbceef into open-mpi:v2.x May 10, 2016
@opoplawski
Copy link
Contributor

I'm not sure this completely fixes the behavior of preallocate. mpi4py test still fails a little later:

    def testPreallocate(self):
        ## MPICH2 1.0.x emits a nesting level warning
        ## when preallocating zero size.
        name, ver = MPI.get_vendor()
        if not (name == 'MPICH2' and ver  < (1,1,0)):
            self.FILE.Preallocate(0)
        size = self.FILE.Get_size()
        self.assertEqual(size, 0)
        self.FILE.Preallocate(1)
        size = self.FILE.Get_size()
        self.assertEqual(size, 1)
        self.FILE.Preallocate(100)
        size = self.FILE.Get_size()
        self.assertEqual(size, 100)
        self.FILE.Preallocate(10)
        size = self.FILE.Get_size()
        self.assertEqual(size, 100)

fails at the final assert:

FAIL: testPreallocate (test_file.TestFileSelf)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test/test_file.py", line 49, in testPreallocate
    self.assertEqual(size, 100)
AssertionError: 10 != 100

So it looks like the size is going down instead of being unchanged. Apparently the standard reads:

If size is larger than the current file size, the file size increases to size. If size is less than or equal to the current file size, the file size is unchanged.

See also https://bitbucket.org/mpi4py/mpi4py/issues/40/test-failures-with-openmpi-200rc2

@edgargabriel
Copy link
Member Author

I did already reopen the other ticket, will look into this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants