I'm not an MTT developer, but I'll answer #1...
MTT only looks at the return codes from the test programs that are ran. This
is all well and good, but the problem is that some Intel tests return a
meaningful value, and some don't. A while ago I went through and fixed all
the c tests so that
Hi everyone,
This may be a silly question, but I am new to configuring MTT so I'll ask.
Here at IU on our cluster Thor, we are running the trunk both with threads
enabled and with threads disabled. How should these builds be differentiated
for the reporter?
Thanks,
Tim
On Saturday 23 June 2007 10:58:13 am Jeff Squyres wrote:
> If you are running the MPI 2 C++ tests for OMPI testing, note that I
> just split it into 2 executables. So if you currently have this in
> your .ini file:
>
> simple_pass:tests = src/mpi2c++_test
>
> You need to change it to this:
>
so resolve these referential integrity problems.
-Ethan
On Sun, Jul/01/2007 09:37:17PM, Tim Prins wrote:
Hi Folks,
For a while now we have been getting errors when MTT tries to submit its test
results to the database. The weird thing is that it only happens on our 1.2
runs, not our trunk runs.
Here is the
Hi,
With the new version of MTT, the textfile report file format changed to a more
human readable format. Since we here at IU use a script to parse this, it
presents a bit of a problem. I can update our script, but was wondering how
stable this new output format is.
If it will not be very
a *directly* to your Perl wrappers?
> Your wrapper would do no parsing then. E.g.,
>
> open(FILE, "< $file");
> undef $/;
> $mtt_results = ;
>
> -Ethan
>
> On Mon, Jul/09/2007 06:07:51PM, Tim Prins wrote:
> > Hi,
> >
> > With the new vers
bletextfile_" params
>
> Let me know if you run into any other issues with this.
>
> -Ethan
>
> On Tue, Jul/10/2007 02:27:27PM, Tim Prins wrote:
> > Hmm, the INI file reporter does not seem to work for me. For the test
> > results I only get the information about the last test r
All,
First, I have to say the new faster reporter is very nice.
However, I am running into some difficulty with trial runs. Here is what
I did:
1. went to www.open-mpi.org/mtt/reporter.php
2. Clicked preferences, toggled show trial runs
3. typed 'IU' into org
4. Press summary
So far so
Hi folks,
Another question. I am working on trying to get the performance stuff to work,
using the jms branch. The tests all ran ok, but when they were submitted, all
of the tests (imb, netpipe, osu, and skampi) are in the database labeled as
being from the skampi suite.
You can see this
It installed and the tests built and made it into the database:
http://www.open-mpi.org/mtt/reporter.php?do_redir=293
Tim
Jeff Squyres wrote:
Did you get a correct MPI install section for mpich2?
On Aug 28, 2007, at 9:05 AM, Tim Prins wrote:
Hi all,
I am working with the jms branch
Hi,
BigRed has not gotten its test results into the database for a while.
This is running the ompi-core-testers branch. We run by passing the
results through the mtt-relay.
The mtt-output file has lines like:
*** WARNING: MTTDatabase did not get a serial; phases will be isolated
from each
Here is the smallest one. Let me know if you need anything else.
Tim
Jeff Squyres wrote:
Can you send any one of those mtt database files? We'll need to
figure out if this is a client or a server problem. :-(
On Sep 5, 2007, at 7:40 AM, Tim Prins wrote:
Hi,
BigRed has not gotten its
Hi,
I was doing a search and hit advanced, entered '32' into the bitness
field, and pressed submit. I got back the following error:
postgres: ERROR: operator does not exist: bit ~* "unknown" LINE 70:
(bitness ~* '32') ^ HINT: No operator matches the given name and
argument type(s). You may
13 matches
Mail list logo
