Re: [MTT users] Why is this loop_spawn test result marked FAIL?

from Test::Analyze::Correctness. Somehow $pass came > out to be 0, so it fell into the "fail" path...? > > > On Apr 14, 2010, at 10:51 AM, Ethan Mallove wrote: > > > This loop_spawn test appears to have passed, though it's marked > > as FAIL: > > > >

Re: [MTT users] [MTT bugs] [MTT] #212: Genericnetworklockingserver *REVIEW NEEDED*

I can do the below stuff in a seperate commit. -Ethan On Fri, Mar/05/2010 09:26:21PM, Jeff Squyres wrote: > On Mar 5, 2010, at 2:05 PM, Ethan Mallove wrote: > > > The check is there now. Ready for review. > > Did you mean to include these parts? > > --- lib/MTT/Mess

Re: [MTT users] [MTT bugs] [MTT] #212: Generic networklockingserver *REVIEW NEEDED*

On Fri, Feb/19/2010 12:00:55PM, Ethan Mallove wrote: > On Thu, Feb/18/2010 04:13:15PM, Jeff Squyres wrote: > > On Feb 18, 2010, at 10:48 AM, Ethan Mallove wrote: > > > > > To ensure there is never a collision between $a->{k} and $b->{k}, the > > > user ca

Re: [MTT users] [MTT bugs] [MTT] #212: Generic network locking server *REVIEW NEEDED*

This apparently got lost in the shuffle a few months ago. The fix allows one to kick off all of their MPI Installs and Test Builds in parallel. Give it a try when you have a chance. -Ethan > On Sat, Nov/07/2009 04:15:42PM, Jeff Squyres wrote: > > On Nov 6, 2009, at 5:18 PM, Etha

Re: [MTT users] MTT:Error while executing ompi-core-perf-testing.ini

Hi Vishal, The debug output shows that your MTT run aborted because you do not have a username/passwd for the open-mpi.org/mtt/submit URL. To skip the IU Database part, try running with --no-section iu.database, e.g., # cat ompi-core-perf-testing.ini | ../client/mtt --no-section iu.database

Re: [MTT users] MTT trivial tests failstocomplete

e the next developer.ini change that I should be making ? > > The complete output and the developer.ini attached. Oops. () should be (). "svn up" and try again. -Ethan > > Thanks! > > Venkat > > -Original Message- > From: mtt-users-boun...@open-

Re: [MTT users] MTT trivial tests fails to complete on Centos5.3-x86_64 bit platform with OFED 1.5

Could you run with --debug (instead of --verbose), and send the output. Thanks, Ethan On Wed, Nov/18/2009 11:08:18AM, Venkat Venkatsubra wrote: > > > > >From: Venkat Venkatsubra >Sent: Wednesday, November 18, 2009 12:54 PM >To: 'mtt-us...@open-mpi.org' >Subject: MTT trivial

Re: [MTT users] autogen.sh in svn_post_export

On Wed, Nov/04/2009 02:22:28PM, Jeff Squyres wrote: > On Nov 4, 2009, at 1:51 PM, Ethan Mallove wrote: > >> I recently ran into the error "./configure: No such file or directory" >> in my nightly test build for the ibm, mpicxx, and onesided test >> suites: &

[MTT users] autogen.sh in svn_post_export

I recently ran into the error "./configure: No such file or directory" in my nightly test build for the ibm, mpicxx, and onesided test suites: http://www.open-mpi.org/mtt/index.php?do_redir=1169 This problem had something to do with autogen.sh being run in the Test get section (different

Re: [MTT users] MTT Error on SLES11

On Mon, Apr/13/2009 09:38:27AM, Rafael Folco wrote: > On Thu, 2009-04-09 at 16:05 -0400, Ethan Mallove wrote: > > On Wed, Apr/08/2009 05:05:30PM, Rafael Folco wrote: > > > Ethan, Jeff, > > > > > > Sorry for the perl confusion, nevermind... > > >

Re: [MTT users] MTT Error on SLES11

g ./f90_hello ./cxx_ring >./f77_hello ./cxx_hello ./f90_ring ./c_hello > *** ERROR: Module aborted: MTT::Test::Specify::Simple:Specify: Can't use > string ("8") as an ARRAY ref while "strict refs" in use at > /tmp/ompi-core-testers/lib/MTT/Values.pm line 75.

Re: [MTT users] MTT Error on SLES11

On Wed, Apr/08/2009 11:36:05AM, Rafael Folco wrote: > Well, I took a look at /tmp/ompi-core-testers/lib/MTT/Values.pm line 75. > > This piece of code looks wrong to me: > > if ($#{@$ret} < 0) { > > $ret references an array > @$ret points to the first element of this array > $# returns the

Re: [MTT users] Patch for whatami (new sles10 lsb-release fileformat)

tami, it may break existing tests >> they depend on. >> >> I'm leaning towards a). >> >> Thoughts? >> >> -Brian >> >> >> Jeff Squyres wrote: >>> Ditto: >>> >>> [8:23] svbu-mpi:~/svn/mtt % ./client/whatami/whatami

Re: [MTT users] [MTT bugs] [MTT] #258: Compare non-contiguous date ranges

Folks, I have a fix for this ticket. The syntax to get non-contiguous date ranges is to use space-delimited quoted tokens (see http://tinyurl.com/6e2pqa), e.g., "2007-10-29 - 2007-11-30" "2008-11-07 - 2008-11-14" "by month" Trying to view year-old results alongside week-old results in the

Re: [MTT users] Fwd: [Alert] Found server-side submit error messages

t; -- Josh > > On Oct 30, 2008, at 11:36 AM, Ethan Mallove wrote: > >> On Wed, Oct/29/2008 09:15:37AM, Ethan Mallove wrote: >>> On Tue, Oct/28/2008 06:17:12PM, Jeff Squyres wrote: >>>> Should we set a default value of report_after_n_results to, say

Re: [MTT users] Fwd: [Alert] Found server-side submit error messages

On Wed, Oct/29/2008 09:15:37AM, Ethan Mallove wrote: > On Tue, Oct/28/2008 06:17:12PM, Jeff Squyres wrote: > > Should we set a default value of report_after_n_results to, say, 50 or 100? > > > > We should. > > -Ethan > > > > On Oct 28, 2008, at 6:15 PM,

[MTT users] Fwd: [Alert] Found server-side submit error messages

IP address to the log file, and then this can be matched with the IP addr against the submit.php errors. -Ethan - Forwarded message from Ethan Mallove <emall...@osl.iu.edu> ----- From: Ethan Mallove <emall...@osl.iu.edu> List-Post: mtt-users@lists.open-mpi.org Date: Tue, 28 O

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

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. >> >>

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

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

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] Can not find my testing results in OMPI MTT DB

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

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] MTT server side problem

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

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, > &

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

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] Introduce myself.

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

Re: [MTT users] Reporter problems

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] questions on MTT setup instructions.

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] hostlist enhancement

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.

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] mtt multiple mpi install and non open mpi instal issues

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] SVN URLs

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 database access

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

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] unable to pull tests

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] "Passed" result on a run-time linker error

... $ ./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

[MTT users] Private-MTT setup HOWTOs

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] Problems running MTT with already installed MPICH-MX

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: > > >

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

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] OSU parsing module issue?

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: > >

[MTT users] OSU parsing module issue?

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] [MTT] #245: Support multiplicative effect for other INI params

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] Associating "description" with a single phase

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

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

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

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 >

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

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] Textfile Reporter

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

Re: [MTT users] Perl Wrap Error

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

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,

[MTT users] max_np on multi-processor nodes

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] funclet and quoting

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] funclet and quoting

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] New version of MTT

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! > >

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

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] script to resubmit results

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] Deadline to go back to "testers" branch

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] [devel-core] first steps with MTT

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

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

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] Minor bug found in MTT 2 client side.

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

[MTT users] "Cherry picking" feature

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] Corrupted MTT database or incorrucet query

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

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

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] New MTT home page

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

[MTT users] 1.2b1r12528 results DELETE

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

[MTT users] New MTT home page

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

Re: [MTT users] make distclean option?

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

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

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

Re: [MTT users] Discussion on teleconf yesterday?

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] Bproc support in MTT

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] MTT reporter module settings

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] Tests build, but do not run

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] Post run result submission

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

Re: [MTT users] Post run result submission

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] Timeouts for specific tests

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] perfbase.php not slurping test run data

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

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

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] [MTT svn] svn:mtt r196 - in trunk: lib/MTT lib/MTT/Reporter server

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