've been asking around. Its been suggested the route described in this URL
> can be taken,
>
> http://python-future.org/imports.html <http://python-future.org/imports.html>
>
>
>
> 2016-05-09 10:47 GMT-06:00 Ralph Castain <mailto:r...@open-mpi.org>>:
&
ve a friendly error message at run time if you
> accidentally run with Python 3.x?
>
>
> > On May 9, 2016, at 12:37 PM, Ralph Castain wrote:
> >
> > Hi folks
> >
> > As we look at the Python client, there is an issue with the supported
> Python version. Ther
Hi folks
As we look at the Python client, there is an issue with the supported
Python version. There was a significant break in the user-level API between
Python 2.x and Python 3. Some of the issues are described here:
https://docs.python.org/2/glossary.html#term-2to3
Noah and I have chatted abo
brary
>>> for the MTT Reporter. We could just remove that feature from the release
>>> since the new reporter will do something different.
>>>
>>> Releasing where we are now should be pretty straight forward if folks just
>>> want to posted a versioned
Hey folks
I'm working on the Python client and it is coming along pretty well. The
code is completely separate from the Perl-based client and doesn't interact
with it, so I would like to push it into the repo on an on-going basis so
others can look at it and comment as I go rather than hold it unt
Hey folks
There is interest in packaging MTT in the OpenHPC distribution. However, we
don't actually have "releases" of MTT. Any objection to actually
tagging/releasing versions?
Ralph
We can happily provide the requested password as soon as the contributor
agreement is received. The ompi-tests repo is “private” as we are not allowed
to distribute some of those contributions.
I’ve copied Geoff here as the person at IBM who is pursuing that agreement.
Ralph
> On Jul 13, 2015,
Jaison Mulerikkal, PhD
> New Zealand eScience Infrastructure
> The University of Auckland
> e: j.mulerik...@auckland.ac.nz
> p: +64 9 923 2194 (internal ext: 82194)
> w: www.jaison.me
>
>
>
>
>
> On 11/06/2014, at 11:19 am, Ralph Castain wrote:
>
>>
gt; So I guess my questions are:
>
> 1. Do you really want/need access to our SVN repo, or do you just want/need a
> list of the test suites that you can download from the internet yourself?
>
> 2. Do you intend to test nightly Open MPI tarballs?
>
> Thanks for your patience i
3 2194 (internal ext: 82194)w: www.jaison.me
On 29/05/2014, at 5:04 pm, Ralph Castain <r...@open-mpi.org> wrote:On May 28, 2014, at 8:29 PM, Jaison Mulerikkal <j.mulerik...@auckland.ac.nz> wrote:Hi Ralph,Hello - and welcome!Thanks for your previous clarification.At our organisation (ww
On May 28, 2014, at 10:23 PM, Gilles Gouaillardet
wrote:
> Jaison,
>
> please note the ompi-tests repo is password protected
> (this is for legal reasons, there is nothing confidential here)
>
> if you do not already have access to this repo, please ask for it
> (just send an email to this ma
ng as soon as you are ready.
Ralph
>
> Jaison Mulerikkal, PhD
> New Zealand eScience Infrastructure
> The University of Auckland
> e: j.mulerik...@auckland.ac.nz
> p: +64 9 923 2194 (internal ext: 82194)
> w: www.jaison.me
>
>
>
>
>
> On 23/05/2014,
I do it all the time myself - the ini file contains this:
#==
# MPI get phase
#==
#--
[MPI g
We only allow developers to have access to the ompi-test repository (it has
some non-publicly distributed tests in it), so you would need to get your
organization to sign the appropriate agreement:
http://www.open-mpi.org/community/contribute/corporate.php
Once we have that, getting the account
etenv("MTT_VERSION_FILE_SUFFIX").txt
#--
Note the "snapshot_version_file" entry where the version gets stored
>
> By removing/changing workspace dir this info will be lost. And next mtt
> execution may submit old results again.
>
> - Original M
You have two options:
1. After each mtt execution, run a "cleanup" script that simply does "rm -rf
"
2. give the mtt scratch location a different name for each execution. However,
be careful as you will fill your disk this way - so perhaps run a cleanup
script every N times that whacks the old
I don't see anything obviously wrong - the text output should tell you how many
tests it found. Does it say that it didn't find anything?
On Dec 21, 2013, at 11:38 PM, caohaijun wrote:
> Now I have a INI file as the following attached, and with which I can
> successfully run the first several
I always do it within MTT - here is the relevant block in the MTT .ini file:
#==
# MPI get phase
#==
[MPI get: ompi-nightly-trunk]
mpi_details = Open MPI
module
Yeah, I'll contact Michael on the Intel email system.
On Jul 31, 2013, at 1:37 PM, "Jeff Squyres (jsquyres)"
wrote:
> Michael --
>
> Ping Ralph Castain (at Intel); he's got the Intel organization MTT password.
>
>
> On Jul 31, 2013, at 2:11 PM, "J
Okay, I'm happy to do so for now - we can deal with the access issue down the
road someday.
Thx!
On Aug 16, 2012, at 3:10 PM, Jeff Squyres wrote:
> You can set "trial=1" in your .ini file so that your results aren't shown by
> default.
>
>
> On Aug 16, 20
Yo Jeff (or whomever answers the call)
Please issue a database access credential for Greenplum - I'll be starting to
run nightly tests on the 1.7 series using the rsh/ssh launcher so someone tests
it :-)
Minuscule cluster (4-nodes), but better than nothing.
Ralph
21 matches
Mail list logo
