Re: [MTT users] [MTT svn] svn:mtt r196 - in trunk: lib/MTT lib/MTT/Reporter server

2006-07-14 Thread Ethan Mallove
Here's the log which was not added to the repository because I accidentally typed "c" at the "a)bort, c)ontinue, e)dit" svn commit prompt. - Show user where the perfbase HTTP POST is going in host:port/dir format. - env_proxy => 1 is unreliable. Look for the proxy in the user's env and

Re: [MTT users] perfbase.php not slurping test run data

2006-07-19 Thread Ethan Mallove
I would do. > > > >>-----Original Message- >>From: mtt-users-boun...@open-mpi.org >>[mailto:mtt-users-boun...@open-mpi.org] On Behalf Of Ethan Mallove >>Sent: Tuesday, July 18, 2006 6:33 PM >>To: mtt-us...@open-mpi.org >>Subject: [MTT users

Re: [MTT users] perfbase.php not slurping test run data

2006-07-19 Thread Ethan Mallove
nce="multiple". For these fields I've set retrigger=yes (which should > be > the default) to force an update to occur if the row exists - no luck. > > I'm not sure if this is a problem in the exp_*.xml files or the inp_*.xml > files?. > > Also, how was it determin

[MTT users] nightly results format

2006-07-20 Thread Ethan Mallove
Here's a draft for a nightly test results email format. One will receive reports through mtt-resu...@open-mpi.org. Note: The following is a faux-report. Just pretend there is nothing non-sensical about the data. This might be better sent as an attachment, or a link to a webpage as lots of email

Re: [MTT users] Timeouts for specific tests

2006-09-20 Thread Ethan Mallove
Not sure if this will work, but here goes (correct me if I'm wrong, Jeff). Try appending the following to the intel section of your ini (put the names of the tests you expect to take 5 min, in a file named 'supposed_to_take_5_min' next to your other test lists): simple_timeout:tests =

Re: [MTT users] Post run result submission

2006-09-26 Thread Ethan Mallove
On Tue, Sep/26/2006 02:01:41PM, Josh Hursey wrote: > I'm setting up MTT on BigRed at IU, and due to some visibility > requirements of the compute nodes I segment the MTT operations. > Currently I have a perl script that does all the svn and wget > interactions from the login node, then

Re: [MTT users] Post run result submission

2006-09-26 Thread Ethan Mallove
the whole "disconnected > scenario" stuff at a lower priority. :-( > > > On 9/26/06 3:51 PM, "Ethan Mallove" <ethan.mall...@sun.com> wrote: > > > I have an unpretty solution that maybe could serve as a > > stopgap between now and when we imple

[MTT users] Multiple scratch dirs needed?

2006-10-04 Thread Ethan Mallove
I do not have an instance of the string 'sparc' in my ini file, yet I see the following in the --debug output. It looks like it's running with every MPI Install that it can find in my scratch dir. Do I need separate scratch trees for the two different hardware platforms? >> Running with

[MTT users] Missing data

2006-10-10 Thread Ethan Mallove
I'm missing some data. I see the following in my --debug output: ... Build was a success Evaluating: require MTT::Reporter::MTTDatabase Evaluating: $ret = ::Reporter::MTTDatabase::Submit(@args) MTTDatabase reporter Submitting to MTTDatabase... MTTDatabase submit complete Writing to MTTDatabase

Re: [MTT users] Tests build, but do not run

2006-10-11 Thread Ethan Mallove
un phases all > have the same base phase name (e.g., [test get: intel], [test build: intel], > [test run: intel]). You just have to link up names correctly with the > corresponding "back pointer" field names. > > Having said all that, does this make your problem easier? I'm not entirely

Re: [MTT users] Tests build, but do not run

2006-10-13 Thread Ethan Mallove
On Thu, Oct/12/2006 03:01:53PM, Jeff Squyres wrote: > On Oct 11, 2006, at 11:34 AM, Ethan Mallove wrote: > > >So if I do put the four combinations of platform/bitness in > >a single ini file, I then have to do some ugly ini param > >overriding to line up the sections,

Re: [MTT users] MTT reporter module settings

2006-10-18 Thread Ethan Mallove
Hi Jim, On Wed, Oct/18/2006 12:02:24PM, James W. Barker wrote: > Ethan, > > Do you know the correct values for the elements of the reporter > module of the MTT .ini file? These are the values I currently have > set in my .ini file. > > [Reporter: IU database] > module = MTTDatabase > >

Re: [MTT users] Bproc support in MTT

2006-10-18 Thread Ethan Mallove
MTT > understands SLURM, Torque, and LoadLeveler. If you're running under > Bproc, we can easily add support for it into MTT (I'll need some > information from you since I don't have any BProc systems myself). > > Jeff went on to say: > > Ethan Mallove is the engineer at S

Re: [MTT users] Bproc support in MTT

2006-10-20 Thread Ethan Mallove
If you're running under > >> Bproc, we can easily add support for it into MTT (I'll need some > >> information from you since I don't have any BProc systems myself). > >> > >> Jeff went on to say: > >> > >> Ethan Mallove is the engineer at Sun who is hea

Re: [MTT users] MTT reporter module settings

2006-10-20 Thread Ethan Mallove
Ah, remove that trunk workspace, and checkout the release branch: $ svn co https://svn.open-mpi.org/svn/mtt/branches/ompi-core-testers The trunk is out of service at the moment, while we're implementing MTT 2.0 stuff in it. -Ethan On Fri, Oct/20/2006 03:53:24PM, James W. Barker wrote: >

Re: [MTT users] Discussion on teleconf yesterday?

2006-10-27 Thread Ethan Mallove
On Fri, Oct/27/2006 10:31:44AM, Josh Hursey wrote: > > On Oct 27, 2006, at 7:39 AM, Jeff Squyres wrote: > > > On Oct 25, 2006, at 10:37 AM, Josh Hursey wrote: > > > >> The discussion started with the bug characteristics of v1.2 versus > >> the trunk. > > > > Gotcha. > > > >> It seemed from the

Re: [MTT users] Discussion on teleconf yesterday? (raw SQL)

2006-10-31 Thread Ethan Mallove
FYI - in the open-mpi.org/mtt, you can check the "SQL" checkbox to see the raw SQL queries. Here's the "Odin" query showing the SQL: http://tinyurl.com/yd7oob You can modify and play around with those on the live database, e.g.: $ echo "... some SQL ... " | psql -d mtt -U iu I also like the

[MTT users] funclet and EvaluateString

2006-11-02 Thread Ethan Mallove
I need to compile a testsuite like this: shell_build_command = ("configure --with-lib-mpi=", _prefix(), "gmake") But MTT errors out with: Building Shell Evaluating: ("configure --with-lib-mpi=", _prefix(), "gmake") Got name: test_prefix Got args: _do: $ret =

Re: [MTT users] make distclean option?

2006-11-07 Thread Ethan Mallove
Here's a workaround that might work. Put something like this your INI file: [Test build: foo] test_get = foo module = Shell shell_build_command = make [Test build: foo clean] test_get = foo module = Shell shell_build_command = make distclean Then do: $ client/mtt --no-section clean ... In a

[MTT users] New MTT home page

2006-11-10 Thread Ethan Mallove
Folks, The MTT home page has been updated to display a number of quick links divided up by date range, organization, and testing phase (MPI installation, test build, and test run). The custom and summary reports are linked from there. http://www.open-mpi.org/mtt/ -- -Ethan

[MTT users] 1.2b1r12528 results DELETE

2006-11-10 Thread Ethan Mallove
When trying to DELETE some Test Runs for 1.2b1r12528 - I accidentally whacked 3,500 Test Runs. If you have the mttdatabase_debug files somewhere I can put them back in the database. My apologies. -- -Ethan

Re: [MTT users] New MTT home page

2006-11-10 Thread Ethan Mallove
t;, > but without the entries that had zero failures. > > If it wouldn't be too much trouble, could you also add a "Past 48 > Hours" section, > but this is lower priority than adding a "Failed Test Runs" column. > > Thanks! > > On 11/10/06, Ethan Mallove

Re: [MTT users] [MTT bugs] [MTT] #132: Print BIG WARNING in client if MTTDatabase fails to submit properly

2006-11-11 Thread Ethan Mallove
On Fri, Nov/10/2006 11:11:39PM, MTT wrote: > #132: Print BIG WARNING in client if MTTDatabase fails to submit properly > --+- > Reporter: jsquyres | Owner: emallove > Type: defect | Status: new

Re: [MTT users] Corrupted MTT database or incorrucet query

2006-11-13 Thread Ethan Mallove
I can infer that you have an MPI Install section labeled "odin 64 bit gcc". A few questions: * What is the mpi_get for that section (or how does that parameter get filled in by your automated scripts)? * Do you start with a fresh scratch tree every run? * Could you email me your

[MTT users] "Cherry picking" feature

2007-01-11 Thread Ethan Mallove
Folks, I forgot to mention on Tuesday's teleconference, a useful feature in Performance mode. If you click Performance, above the graphs is a summary with a far left column containing checkboxes. Those checkboxes allow you to ''cherry pick'' which rows to plot in the below graphs. So you can

Re: [MTT users] reserved key words ?

2007-01-12 Thread Ethan Mallove
So you must have MPI install sections that look a little like: [MPI install: foo debug non-threaded] [MPI install: foo debug threaded] [MPI install: foo release non-threaded] [MPI install: foo release threaded] ? Don't you want to search on ''configure arguments''? That can be done right now,

[MTT users] MTT 2.0 switchover status

2007-01-18 Thread Ethan Mallove
We are a little behind schedule in getting ''everyone'' switched over to the MTT trunk, so we are pushing the date for switching back to the ompi-core-testers branch to Monday, January 22. https://svn.open-mpi.org/trac/mtt/wiki/News-03-Jan-2007#SchedulefortheMTT2.0rollout -Ethan

Re: [MTT users] Minor bug found in MTT 2 client side.

2007-01-19 Thread Ethan Mallove
On Fri, Jan/19/2007 08:55:26AM, Tim Mattox wrote: > Hi All, > > On 1/18/07, Jeff Squyres wrote: > > On Jan 18, 2007, at 10:37 PM, Tim Mattox wrote: > [snip description of a newline bug] > > > Fixed -- none have newlines now, so they'll all be in the one-line > > output

Re: [MTT users] Minor bug found in MTT 2 client side.

2007-01-19 Thread Ethan Mallove
Tim, I wonder if reporter.php can help out some here. IIRC, a major advantage of your parsing scripts was to see results of individual MTT invocations, and characteristics of invocations that reporter.php wasn't able to show. reporter.php now keeps track of results ''by invocation'' much more

Re: [MTT users] [devel-core] first steps with MTT

2007-01-23 Thread Ethan Mallove
Hi Andreas, mtt-us...@open-mpi.org is where you want to send MTT-related stuff. On Tue, Jan/23/2007 09:12:59AM, Andreas Kn?pfer wrote: > Hello everyone, > > After our first experiments with MTT I'd like to ask a > couple of questions. I guess, if I put them here the > answers will go to the

[MTT users] Deadline to go back to "testers" branch

2007-01-24 Thread Ethan Mallove
Folks, The new branch has been cut. Please switch back to the ompi-core-testers branch by Friday. The SVN URL is https://svn.open-mpi.org/svn/mtt/branches/ompi-core-testers. The MTT 2.0 server-side scripts are located (again) at http://www.open-mpi.org/mtt, which means you need to update the

Re: [MTT users] script to resubmit results

2007-03-01 Thread Ethan Mallove
I just added a client/mtt-submit script to the mtt/trunk SVN repository which will help you. You'll need to use it like this: $ client/mtt-submit -f '/directory/where/results/are/*.txt' -g -u cisco -p /directory/where/results/are/ is specified in your INI file as mttdatabase_debug_filename.

[MTT users] MTT server error (user: ibm)

2007-03-09 Thread Ethan Mallove
Camille, Your results today were borked somehow. What options did you give to client/mtt? *Something* happened with the --trial option. I patched the MTT client, though I've never seen this error before. Unfortunately, you would need to re-run your tests (after doing "svn up") to submit them

Re: [MTT users] New version of MTT

2007-05-10 Thread Ethan Mallove
Folks, MTT version 2.1 is live! Please do an "svn up" at your earliest convenience. As always, report any issues you encounter to this mailing list. Thanks, Ethan On Wed, May/09/2007 09:09:46PM, Jeff Squyres wrote: > All -- > > We are just about to release MTT version 2.1. Woo hoo! > >

Re: [MTT users] mtt test build for IMB-MPI1 fails,

2007-05-21 Thread Ethan Mallove
Just a guess, but could this could be the source of confusion? https://svn.open-mpi.org/svn/ompi-tests/trunk/PMB-2.2 https://svn.open-mpi.org/svn/ompi-tests/trunk/IMB_2.3 Should PMB be removed from ompi-tests? I mean, would there ever be a reason to use PMB 2.2 instead of IMB 2.3? -Ethan On

[MTT users] Failure tracking (RE: #70: Show "new" failures)

2007-05-21 Thread Ethan Mallove
I have something to help filter out (in reporter.php) old known OMPI failures, though this feature is still in an embryonic stage. E.g., here's a link that shows *all* of Sun's recent Test Run failures. http://www.open-mpi.org/~emallove/mtt_/reporter.php?do_redir=199 If I don't care to sift

Re: [MTT users] Failure tracking (RE: #70: Show "new" failures)

2007-05-22 Thread Ethan Mallove
to magically populate the "failure" table by itself. > > On May 21, 2007, at 3:42 PM, Ethan Mallove wrote: > > > I have something to help filter out (in reporter.php) old > > known OMPI failures, though this feature is still in an > > embryonic stage. >

[MTT users] funclet and quoting

2007-06-11 Thread Ethan Mallove
-- Question 1: -- I have the below "exec" and "btls" params in my INI, but I keep running into quoting issues. I'm trying to get an if-else effect by putting the else block in as the third

Re: [MTT users] funclet and quoting

2007-06-12 Thread Ethan Mallove
On Tue, Jun/12/2007 08:07:20AM, Jeff Squyres wrote: > On Jun 11, 2007, at 6:02 PM, Ethan Mallove wrote: > > > btls = ("("("hostname")", "v440-2|v20z-2")", \ > >"("self,sm,tcp")",

Re: [MTT users] funclet and quoting

2007-06-12 Thread Ethan Mallove
On Tue, Jun/12/2007 04:53:21PM, Jeff Squyres wrote: > On Jun 12, 2007, at 10:50 AM, Ethan Mallove wrote: > > >>> eval $btls = MTT::Functions::if(MTT::Functions::regexp > >>> (MTT::Functions::shell("hostname"), "v440-2|v20z-2"), > >&g

Re: [MTT users] Differentiating builds in the reporter

2007-06-15 Thread Ethan Mallove
On Fri, Jun/15/2007 10:01:24AM, Jeff Squyres wrote: > On Jun 14, 2007, at 10:45 PM, Tim Prins wrote: > > > 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? > >

[MTT users] INI trick for single-node testing

2007-06-21 Thread Ethan Mallove
Hi, I have a way to toggle single-node testing at the command line. E.g., it looks like this: $ client/mtt run_on_single_node=1 ... $ client/mtt run_on_single_node=0 ... I just needed the below INI mojo to get this going. Added a "run_on_single_node" boolean to my [MTT] section. ("ompinfo"

[MTT users] max_np on multi-processor nodes

2007-06-27 Thread Ethan Mallove
env_max_procs uses this order of precedence to get a "max_np". 1. Various resource managers 2. If a global hostfile was specified 3. If a global hostlist was specified 4. If a global max_np was specified Shouldn't 4 be at the top of the list? I'm doing single node testing, but the fact

Re: [MTT users] Database insert errors

2007-07-02 Thread Ethan Mallove
Hi Tim, I see some of these FOREIGN KEY constraint errors every night. There's a system of speedy and archive tables to keep short-term queries fast, but it has bugs. There are rows in the archive tables that should be mirrored in the speedy tables, but this is not always the case. We (well,

Re: [MTT users] Perl Wrap Error

2007-07-06 Thread Ethan Mallove
On Fri, Jul/06/2007 01:22:06PM, Joshua Hursey wrote: > Anyone seen the following error from MTT before? It looks like it is in the > reporter stage. > > <-> > shell$ /spin/home/jjhursey/testing/mtt//client/mtt --mpi-install --scratch >

Re: [MTT users] Database insert errors

2007-07-09 Thread Ethan Mallove
I don't think so, because I see the same errors from sites using the latest MTT version. -Ethan On Mon, Jul/09/2007 09:07:20AM, Tim Prins wrote: > Could these errors have to do with the fact that we are running MTT > v2.0.1, and not the latest version? > > Thanks, > > Tim

Re: [MTT users] Textfile Reporter

2007-07-10 Thread Ethan Mallove
.pm (working copy) > @@ -505,6 +505,8 @@ > my $report = { > phase => "MPI Install", > > +mpi_install_section_name => $config->{simple_section_name}, > + > bitness => $config->{bitness}, >

[MTT users] WriteINI() calls in MPI/Install and Test/Build

2007-08-10 Thread Ethan Mallove
Do we still need to write out an INI file after each MPI Install and Test Build? I thought we're using .dump files instead? (I noticed this because it seemed to be taking a few minutes to write the INI file after building the intel tests.) -Ethan

Re: [MTT users] WriteINI() calls in MPI/Install and Test/Build

2007-08-10 Thread Ethan Mallove
On Fri, Aug/10/2007 01:02:16PM, Jeff Squyres wrote: > On Aug 10, 2007, at 10:14 AM, Ethan Mallove wrote: > > > Do we still need to write out an INI file after each MPI > > Install and Test Build? I thought we're using .dump > > files instead? (I noticed this because it

Re: [MTT users] [MTT] #245: Support multiplicative effect for other INI params

2007-09-04 Thread Ethan Mallove
So we will get a multiplicative effect on the following INI parameters? * setenv * unsetenv * env_module Any other parameters? -Ethan On Fri, Aug/31/2007 10:18:30PM, MTT wrote: > #245: Support multiplicative effect for other INI params >

Re: [MTT users] [MTT] #245: Support multiplicative effect for other INI params

2007-09-04 Thread Ethan Mallove
res wrote: > I think we'll get it for everything because of the new @foo@ syntax. > > I don't think you'll want to use that effect everywhere, but it's now > *possible* to do so. > > > On Sep 4, 2007, at 9:57 AM, Ethan Mallove wrote: > > > So we will get a multipl

[MTT users] Associating "description" with a single phase

2007-09-04 Thread Ethan Mallove
reporter.php has a search field for "description", but which phase is that for? MPI Install, Test build, or Test run? A scenario is that Sun will have a home-grown "funclet_files" funclet set the "description" in the Install phase (e.g., a label identifying which ISO is being tested). It would be

Re: [MTT users] [MTT] #245: Support multiplicative effect for other INI params

2007-09-04 Thread Ethan Mallove
On Tue, Sep/04/2007 12:47:29PM, Jeff Squyres wrote: > On Sep 4, 2007, at 10:57 AM, Ethan Mallove wrote: > > > So if I have the following line in my [Test build: intel] > > section, MTT will now build and run the Intel tests *twice*? > > Once with compiler-A

[MTT users] OSU parsing module issue?

2007-09-17 Thread Ethan Mallove
Jeff, Here is a run of "osu" test results that did not seem to register any latency_bandwidth data: http://www.open-mpi.org/mtt/index.php?do_redir=340 Below is the mttdatabase debug file. Could the Analyze/OSU.pm module is getting flummoxed by the warnings that precede the actual performance

Re: [MTT users] OSU parsing module issue?

2007-09-17 Thread Ethan Mallove
The warnings emitted before the performance data *were* the problem. Fixed in r1027. -Ethan On Mon, Sep/17/2007 04:06:26PM, Ethan Mallove wrote: > Jeff, > > Here is a run of "osu" test results that did not seem > to register any latency_bandwidth data: > >

Re: [MTT users] Problem with reporter: selecting bitness

2007-09-20 Thread Ethan Mallove
This is a bug. Ticket to come. A workaround is to select "Show" from the Show/Hide menu next to the Bitness textfield when searching on Bitness. Thanks, Ethan On Thu, Sep/20/2007 08:52:59AM, Tim Prins wrote: > Hi, > > I was doing a search and hit advanced, entered '32' into the bitness >

Re: [MTT users] Capturing stderr using ()

2007-09-25 Thread Ethan Mallove
This issue was resolved by backslash-escaping the '&'. So this works: alreadyinstalled_version = ("tcsh -c '@alreadyinstalled_dir@/bin/mpinfo -V |\& cut -d\" \" -f6-8'") -Ethan On Mon, Sep/17/2007 12:12:48PM, Ethan Mallove wrote: > I am stuck trying to

Re: [MTT users] Sandia account info/request

2007-09-26 Thread Ethan Mallove
Done! -Ethan On Wed, Sep/26/2007 11:25:30AM, Ron Brightwell wrote: > Greetings: > > Does Sandia have an MTT account yet? If not, can we have one? > > [I'm following the instructions on MTT for the collective bakeoff...] > > Thanks, > > -Ron > > >

[MTT users] "Passed" result on a run-time linker error

2007-09-27 Thread Ethan Mallove
Some trivial tests outputted the following: ld.so.1: orterun: fatal: libopen-pal.so.0: open failed: No such file or directory See here: http://www.open-mpi.org/mtt/index.php?do_redir=394 How could these tests result in "pass"? I attached an mttdatabase debug file. -Ethan $VAR1 = {

Re: [MTT users] Problems running MTT with already installed MPICH-MX

2007-09-28 Thread Ethan Mallove
Hi Jelena, Change this line: alreadyinstalled_dir = /usr/local/mpich-mx/bin To this: alreadyinstalled_dir = /usr/local/mpich-mx Does that work? -Ethan On Thu, Sep/27/2007 10:46:55PM, Jelena Pjesivac-Grbovic wrote: > Hello, > > I am trying to test the MPICH-MX using MTT on our clusters

Re: [MTT users] Problems running MTT with already installed MPICH-MX

2007-09-28 Thread Ethan Mallove
ough. Maybe an Install/Analyze/Generic.pm or something ...? -Ethan > On 9/28/07, Ethan Mallove <ethan.mall...@sun.com> wrote: > > Hi Jelena, > > > > Change this line: > > > > alreadyinstalled_dir = /usr/local/mpich-mx/bin > > > > To this: > > >

[MTT users] Private-MTT setup HOWTOs

2007-10-03 Thread Ethan Mallove
Gil, Josh created a few HOWTO pages that should help you get your internal Mellanox MTT server setup: https://svn.open-mpi.org/trac/mtt/wiki/HTTPServer https://svn.open-mpi.org/trac/mtt/wiki/ServerMaintenance https://svn.open-mpi.org/trac/mtt/wiki/Database Josh, another item Gil and I

Re: [MTT users] Private-MTT setup HOWTOs

2007-10-03 Thread Ethan Mallove
On Wed, Oct/03/2007 09:06:16AM, Jeff Squyres wrote: > On Oct 3, 2007, at 8:50 AM, Ethan Mallove wrote: > > > Josh, another item Gil and I talked about was moving a > > subset of test results from the internal Mellanox database > > into the general Open MPI dat

Re: [MTT users] "Passed" result on a run-time linker error

2007-10-10 Thread Ethan Mallove
... $ ./foo ld.so.1: foo: fatal: libbar.so: open failed: No such file or directory Killed $ echo $? 137 -Ethan > On Sep 27, 2007, at 4:22 PM, Ethan Mallove wrote: > > > Some trivial tests outputted the following: > > > > ld.so.1: orterun: fatal: l

Re: [MTT users] unable to pull tests

2007-11-14 Thread Ethan Mallove
Do you have access to the ompi-tests repository? What happens if you do this command outside of MTT? $ svn export https://svn.open-mpi.org/svn/ompi-tests/trunk/onesided You could also try using "http", instead of "https" in your svn_url. -Ethan On Wed, Nov/14/2007 02:04:27PM, Karol Mroz

Re: [MTT users] MTT database access

2007-12-14 Thread Ethan Mallove
Hi Karol, I added three accounts: * ubc * kmroz * penoff OMPI MTT users use their organization name (e.g., "ubc" for you folks), though your local UNIX username is recorded in the results as well to help you sort through whose results belong to who. Cheers, Ethan On Fri, Dec/14/2007

Re: [MTT users] MTT database access

2007-12-14 Thread Ethan Mallove
I thought maybe there was a reason Karol wanted separate accounts that I hadn't thought of. Karol, which accounts do you plan on using? -Ethan On Fri, Dec/14/2007 08:04:37PM, Jeff Squyres wrote: > Do we really need all 3 database accounts for ubc? > > > On Dec 14, 2007, at 5:

Re: [MTT users] MTT database access

2007-12-17 Thread Ethan Mallove
; > Thanks, and sorry for the confusion. > > Ethan Mallove wrote: > > I thought maybe there was a reason Karol wanted separate > > accounts that I hadn't thought of. Karol, which accounts do > > you plan on using? > > > > -Ethan > > > > > >

Re: [MTT users] SVN URLs

2007-12-20 Thread Ethan Mallove
On Thu, Dec/20/2007 06:34:27AM, Jeff Squyres wrote: > FYI: per my post to the OMPI devel list, I discovered the > "svnsync" command yesterday. svnsync allows you to > mirror an entire SVN repository in a read-only fashion; I > mirrored the ompi-tests repository locally at Cisco. A > one-line

Re: [MTT users] SVN URLs

2007-12-20 Thread Ethan Mallove
On Thu, Dec/20/2007 11:51:30AM, Jeff Squyres wrote: > On Dec 20, 2007, at 11:38 AM, Ethan Mallove wrote: > > >> FYI: per my post to the OMPI devel list, I discovered the > >> "svnsync" command yesterday. svnsync allows you to > >> mirror an entir

Re: [MTT users] mtt multiple mpi install and non open mpi instal issues

2008-01-07 Thread Ethan Mallove
Thanks Oleg! It looks like Jeff already applied the multilib.patch. The other one looks good to me. -Ethan On Mon, Jan/07/2008 07:23:55PM, Oleg Kats wrote: >Hello All > >Here is list of issues that we figure out during ourMTT usage: > > > >1. Installation of multiple MPIs

Re: [MTT users] mtt reports arrive without subject.

2008-01-10 Thread Ethan Mallove
Hi Pasha, I confess that I don't use the Email reporter. I think the email_subject is out-of-date. Try this: email_subject = MPI test results: _section() I'm unsure about the empty email body, but have an idea. What does this output for you? $ which Mail mailx mail rmail mutt elm I'm

Re: [MTT users] hostlist enhancement

2008-01-10 Thread Ethan Mallove
Works for me. -Ethan On Thu, Jan/10/2008 08:48:20AM, Jeff Squyres wrote: > Mellanox told me that the MTT () funclet is returning a > comma-delimited list of hosts (and _hosts()). That is fine for > Open MPI, but it is not for MVAPICH -- MVAPICH requires a space-delimited > list of hosts for

Re: [MTT users] mtt reports arrive without subject.

2008-01-10 Thread Ethan Mallove
On Thu, Jan/10/2008 06:27:03PM, Pavel Shamis (Pasha) wrote: > Ethan Mallove wrote: > > Hi Pasha, > > > > I confess that I don't use the Email reporter. I think the > > email_subject is out-of-date. Try this: > > > > email_subject = MPI test results: _secti

Re: [MTT users] questions on MTT setup instructions.

2008-01-23 Thread Ethan Mallove
On Wed, Jan/23/2008 03:36:26PM, Jennis Pruett wrote: > >To followup on this, I think I got it right by just using: > >perl Makefile.PL LIB=/usr/projects/hpctools/jennyp/mtt >PREFIX=/usr/projects/hpctools/jennyp/mtt >setenv PERLIB /usr/projects/hpctools/jennyp/mtt > >I then

Re: [MTT users] question on MTT setup instructions.

2008-01-23 Thread Ethan Mallove
Hi Jennis, FWIW, I run MTT using an MTT source code checkout. (This is admittedly not the Right Way to distribute software, but it works.) Try this: $ svn checkout https://svn.open-mpi.org/svn/mtt/branches/ompi-core-testers $ cd ompi-core-testers $ client/mtt --file

Re: [MTT users] Reporter problems

2008-01-30 Thread Ethan Mallove
I don't remember a "past 24 hour" summary taking "24 seconds". Are we seeing a slow down due to an accumulation of results? I thought the week-long table partitions would prevent this type of effect? -Ethan On Wed, Jan/30/2008 11:00:46AM, Josh Hursey wrote: > This maintenance is complete. The

Re: [MTT users] Reporter problems

2008-01-31 Thread Ethan Mallove
008 03:14:20PM, Josh Hursey wrote: > I'm seeing between 12 and 20 seconds on a fairly idle machine. We can > likely do better. I'll dig into it this week[end] and see what I can do. > > 12 - 20 isn't too bad though considering the amount of data that query > is returning. :) >

[MTT users] Good MPI collectives bakeoff permalinks

2008-02-26 Thread Ethan Mallove
Does anyone have some permalinks they gathered from the collectives bakeoff? I'm specifically interested in MVAPICH and OMPI comparisons. -Ethan

[MTT users] NetPIPE timeouts

2008-02-27 Thread Ethan Mallove
Folks, We were seeing NetPIPE runs timing around 45sec the other day, so I set the timeout value to -1 (which is infinity), and last night a v1.2 NetPIPE run took 3 hrs! It looks like the test got stuck: 0: burl-ct-v440-2 1: burl-ct-v440-2 2: burl-ct-v440-2 3: burl-ct-v440-2 Now

Re: [MTT users] Good MPI collectives bakeoff permalinks

2008-02-29 Thread Ethan Mallove
e text searches during that time period. > > > On Feb 26, 2008, at 11:45 AM, Ethan Mallove wrote: > > > Does anyone have some permalinks they gathered from the > > collectives bakeoff? I'm specifically interested in MVAPICH > >

Re: [MTT users] Good MPI collectives bakeoff permalinks

2008-02-29 Thread Ethan Mallove
ww.open-mpi.org/mtt/index.php?do_redir=426 > > MX_RCACHE=2 > BigRed for 4 nodes all benchmarks: > http://www.open-mpi.org/mtt/index.php?do_redir=431 > > Reran with MX_RCACHE=2 > http://www.open-mpi.org/mtt/index.php?do_redir=433 > > On Fri, Feb 29, 2008 at 12:12 PM, Ethan Ma

Re: [MTT users] Stop OMPI MTT test run failures mail

2008-03-28 Thread Ethan Mallove
I turned off the "test run failures" email (see r1172). -Ethan On Sat, Mar/15/2008 08:19:40AM, Jeff Squyres wrote: > Do we still need the OMPI MTT test run failure e-mail twice a day? > > Personally, I look at the "summary" mail and click through the graph > to see the run failures. Having a

Re: [MTT users] Introduce myself.

2008-04-07 Thread Ethan Mallove
Check this page out to get started using MTT: https://svn.open-mpi.org/trac/mtt/wiki/MTTOverview -Ethan On Sat, Apr/05/2008 10:02:49PM, Davi Vercillo C. Garcia wrote: > Hi all, > > My name is Davi Vercillo and I'm from Brazil. I'm starting right now > to study MPI and I'll use the

[MTT users] New "split graphs" feature in MTT Reporter

2008-04-14 Thread Ethan Mallove
Folks, I added another graphing preference that might make the performance graphs easier to grok. If you click the [Preferences] link now, there's a "Split graphs" option that allows you to split graphs by Halves, Thirds, or Quarters. Here's an example of some performance graphs split into

[MTT users] LD_LIBRARY_PATH setting in Run.pm masks a wrapper compiler issue

2008-05-05 Thread Ethan Mallove
Line 386 of MTT/Test/Run.pm sets LD_LIBRARY_PATH. This appears to have masked a problem in my wrapper compiler (missing -R/foo/lib flags). if ($mpi_install->{libdir}) { if (exists($ENV{LD_LIBRARY_PATH})) { $ENV{LD_LIBRARY_PATH} = "$mpi_install->{libdir}:" .

Re: [MTT users] MTT server side problem

2008-05-06 Thread Ethan Mallove
regular mtt-resu...@open-mpi.org email alerts and some out-of-date DB monitoring junk. You can ignore that stuff. Josh, are there some nightly (DB pruning/cleaning/vacuuming?) cron jobs that Pasha should be running? -Ethan > > Thanks. > > Ethan Mallove wrote: > > Hi Pasha, > &

Re: [MTT users] MTT server side problem

2008-05-06 Thread Ethan Mallove
nightly (DB > > pruning/cleaning/vacuuming?) cron jobs that Pasha should be > > running? > > > > -Ethan > > > > > >> Thanks. > >> > >> Ethan Mallove wrote: > >> > >>> Hi Pasha, > >>> > >>> I

Re: [MTT users] MTT server side problem

2008-05-07 Thread Ethan Mallove
t; Josh > > > > On May 7, 2008, at 4:49 AM, Pavel Shamis (Pasha) wrote: > > > >> Hi, > >> I upgraded the server side (the mtt is still running , so don't know > >> if the problem was resolved) > >> During upgrade I had some problem with the submit/in

Re: [MTT users] MTT fail to require MTT::Test::Specify::Simple

2008-05-12 Thread Ethan Mallove
It is odd that a "require" failed like this in the Test Run phase. I would have expected an earlier "require" to fail (e.g., in the MPI Install phase). I've never run MTT as root before. Does root have read-access to Specify/Simple.pm? If not, can you do the below command in the top-level MTT

Re: [MTT users] MTT fail to require MTT::Test::Specify::Simple

2008-05-13 Thread Ethan Mallove
| POST_EPOCH: passed | >| | t_win: FAILED 1 | >| start_timestamp | Tue May 13 04:54:59 2008 | >| test_name | t_win | >| variant | 2 | > >Wen Hao Wang (**) > >Software Engineer > IBM China Software Development Laboratory >Em

Re: [MTT users] MTT fail to require MTT::Test::Specify::Simple

2008-05-13 Thread Ethan Mallove
> Ethan -- are you referring to the sample INI file on the core-testers > > branch? Yes. I just comitted the fix. -Ethan > > > > > > On May 13, 2008, at 9:59 AM, Ethan Mallove wrote: > > > > > Are you running on the ompi-core-testers branch? I thin

Re: [MTT users] Can not find my testing results in OMPI MTT DB

2008-05-21 Thread Ethan Mallove
t;> >> Pasha >> >> Jeff Squyres wrote: >> >>> FWIW: I think we have at least one open ticket on this issue (break up >>> submits so that we don't overflow PHP and/or apache). https://svn.open-mpi.org/trac/mtt/ticket/221 -Ethan >>> >>

Re: [MTT users] Help

2008-06-10 Thread Ethan Mallove
I'm CC-ing the list, since this is a good question :-) On Tue, Jun/10/2008 11:48:04AM, Phuong Nguyen wrote: > Ethan, > Is there anyway that I could specify the SVN user/password in the INI > file or pass them in command line of "mtt"? > This should work. E.g., $ client/mtt ... svn_username=

Re: [MTT users] Can not find my testing results in OMPI MTT DB

2008-07-08 Thread Ethan Mallove
a serial; phases will be >isolated from each other in the reports > MTTDatabase client submit complete > > And I can not find these results in DB. > Is it any progress with this issue ? > > > Regards. > Pasha > > Ethan Mallove wrote: >> On Wed, May/21/20

Re: [MTT users] Can not find my testing results in OMPI MTT DB

2008-07-08 Thread Ethan Mallove
abase client trying proxy: / Default (none) >>> MTTDatabase proxy successful / not 500 >>> MTTDatabase response is a success >>> MTTDatabase client got response: >>> *** WARNING: MTTDatabase client did not get a serial; phases will be >>> isolated from ea

[MTT users] Wiki page on INI includes (include_files and include_section)

2008-07-22 Thread Ethan Mallove
IU folks, Word on the street is that you guys are creating an INI file on-the-fly. You might find the "include_files" and "include_section" INI parameters useful: https://svn.open-mpi.org/trac/mtt/wiki/INI%20Includes Maybe I should've brought this up eight months ago when the feature was

Re: [MTT users] Patch to add --local-scratch option

2008-09-16 Thread Ethan Mallove
Nice! A few thoughts ... What happens if one uses --local-scratch, but leaves out the --scratch option? In this case, I think MTT should assume --scratch is the same as --local-scratch. Could the "local" in --local-scratch ever be misleading? Couldn't a user ever use a mounted filesystem that's

Re: [MTT users] Patch to add --local-scratch option

2008-09-16 Thread Ethan Mallove
On Tue, Sep/16/2008 12:07:31PM, Ethan Mallove wrote: > Nice! A few thoughts ... > > What happens if one uses --local-scratch, but leaves out the > --scratch option? In this case, I think MTT should assume > --scratch is the same as --local-scratch. > > Could the "loca

Re: [MTT users] Patch to add --local-scratch option

2008-09-19 Thread Ethan Mallove
On Thu, Sep/18/2008 05:35:13PM, Jeff Squyres wrote: > On Sep 18, 2008, at 10:45 AM, Ethan Mallove wrote: > >>> Ah, yeah, ok, now I see why you wouldl call it --mpi-install-scratch, so >>> that it matches the MTT ini section name. Sure, that works for me. >> >>

  1   2   >