I was thinking about this, and I believe it would require a change to the mtt client to avoid it. I’m working on a new Python-based version of it, and I’ll make sure to deal with this there.
In the interim, I’ll have to defer to some old, gray Perl guru to update the current client > On Oct 22, 2015, at 9:23 AM, Howard Pritchard <hpprit...@gmail.com> wrote: > > Hi Folks, > > I don't seem to have gotten subscribed yet to mtt-users mail list so > forwarding to the dev team. > > Howard > > ---------- Forwarded message ---------- > From: Howard Pritchard <hpprit...@gmail.com <mailto:hpprit...@gmail.com>> > Date: 2015-10-22 10:18 GMT-06:00 > Subject: mtt-submit, etc. > To: mtt-us...@open-mpi.org <mailto:mtt-us...@open-mpi.org> > > > HI Folks, > > I have the following issue with a cluster I would like to use for submitting > MTT results > for Open MPI, namely, that the nodes on which I have to submit batch jobs to > run > the tests don't have external internet connectivity, so if my mtt ini file > has a IU database reporter > section, the run dies in the "ping the mtt server" test. > > What I have right now is a two-stage process where I checkout and > compile/build > Open MPI and the tests on a front end which does have access to the mtt > server. > This part works and gets reported back to IU database. > > I can run the tests using mtt, but have to disable all the mtt server > reporter stuff. > > I thought I could use mtt-submit to submit some kind of mttdatabase debug file > back to IU once the batch job has completed, but I can't figure out a way > to generate this file without enable the mtt server reporter section in the > ini file, > and so back to the ping failure issue. > > Would anyone have suggestions on how to work around this problem? > > Thanks, > > Howard > > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2015/10/18244.php
