[MTT devel] No summary mails since Aug 29

2007-09-05 Thread Jeff Squyres
Has anyone gotten summary e-mails since Aug 29?  The last bunch I got  
were the morning of Aug 29.


We should have also gotten:

- Evening Aug 29 (Wed)
- Morning/Evening Aug 30 (Thu)
- Morning Aug 31 (Fri)
- Morning Sep 3 (Mon) (can't remember if we do Monday evenings or not)
- Morning/Evening Sep 4 (Tue)
- Morning Sep 5 (Wed) -- so far

It seems like something is wrong with the cron script...?

--
Jeff Squyres
Cisco Systems



Re: [MTT devel] No summary mails since Aug 29

2007-09-05 Thread Ethan Mallove
I started getting these on Aug 29:

  "Sorry, this page is not mirrored.  Please see the http://www.open-mpi.org/";>original version of this page on the main
  Open MPI web site."

curl_get.inc in ompi-www appears to be out-of-date.

-Ethan


On Wed, Sep/05/2007 11:06:25AM, Jeff Squyres wrote:
> Has anyone gotten summary e-mails since Aug 29?  The last bunch I got  
> were the morning of Aug 29.
> 
> We should have also gotten:
> 
> - Evening Aug 29 (Wed)
> - Morning/Evening Aug 30 (Thu)
> - Morning Aug 31 (Fri)
> - Morning Sep 3 (Mon) (can't remember if we do Monday evenings or not)
> - Morning/Evening Sep 4 (Tue)
> - Morning Sep 5 (Wed) -- so far
> 
> It seems like something is wrong with the cron script...?
> 
> -- 
> Jeff Squyres
> Cisco Systems
> 
> ___
> mtt-devel mailing list
> mtt-de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel


Re: [MTT devel] No summary mails since Aug 29

2007-09-05 Thread Jeff Squyres

Crud -- I think we talked about this and then I forgot about it.

Ethan and I will followup in IM...



On Sep 5, 2007, at 11:58 AM, Ethan Mallove wrote:


I started getting these on Aug 29:

  "Sorry, this page is not mirrored.  Please see the   href="http://www.open-mpi.org/";>original version of this page  
on the main

  Open MPI web site."

curl_get.inc in ompi-www appears to be out-of-date.

-Ethan


On Wed, Sep/05/2007 11:06:25AM, Jeff Squyres wrote:

Has anyone gotten summary e-mails since Aug 29?  The last bunch I got
were the morning of Aug 29.

We should have also gotten:

- Evening Aug 29 (Wed)
- Morning/Evening Aug 30 (Thu)
- Morning Aug 31 (Fri)
- Morning Sep 3 (Mon) (can't remember if we do Monday evenings or  
not)

- Morning/Evening Sep 4 (Tue)
- Morning Sep 5 (Wed) -- so far

It seems like something is wrong with the cron script...?

--
Jeff Squyres
Cisco Systems

___
mtt-devel mailing list
mtt-de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel

___
mtt-devel mailing list
mtt-de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel



--
Jeff Squyres
Cisco Systems



Re: [MTT devel] No summary mails since Aug 29

2007-09-05 Thread Jeff Squyres
To followup for the list: we fixed this problem today.  The mails  
should resume this evening (in about 45 minutes).


On Sep 5, 2007, at 12:01 PM, Jeff Squyres wrote:


Crud -- I think we talked about this and then I forgot about it.

Ethan and I will followup in IM...



On Sep 5, 2007, at 11:58 AM, Ethan Mallove wrote:


I started getting these on Aug 29:

  "Sorry, this page is not mirrored.  Please see the http://www.open-mpi.org/";>original version of this page
on the main
  Open MPI web site."

curl_get.inc in ompi-www appears to be out-of-date.

-Ethan


On Wed, Sep/05/2007 11:06:25AM, Jeff Squyres wrote:
Has anyone gotten summary e-mails since Aug 29?  The last bunch I  
got

were the morning of Aug 29.

We should have also gotten:

- Evening Aug 29 (Wed)
- Morning/Evening Aug 30 (Thu)
- Morning Aug 31 (Fri)
- Morning Sep 3 (Mon) (can't remember if we do Monday evenings or
not)
- Morning/Evening Sep 4 (Tue)
- Morning Sep 5 (Wed) -- so far

It seems like something is wrong with the cron script...?

--
Jeff Squyres
Cisco Systems

___
mtt-devel mailing list
mtt-de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel

___
mtt-devel mailing list
mtt-de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel



--
Jeff Squyres
Cisco Systems

___
mtt-devel mailing list
mtt-de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel



--
Jeff Squyres
Cisco Systems



[MTT devel] Fwd: [mtt-results] Evening Test Run Failures

2007-09-05 Thread Jeff Squyres

Doh.

Any idea what happened here?

Begin forwarded message:


From: mtt-resu...@osl.iu.edu
Date: September 5, 2007 9:00:19 PM EDT
To: mtt-resu...@open-mpi.org
Subject: [mtt-results] Evening Test Run Failures
Reply-To: MPI Test Tool result submissions 

1



--
Jeff Squyres
Cisco Systems



Re: [MTT devel] [MTT users] Test runs not getting into database

2007-09-05 Thread Jeff Squyres

Josh / Ethan --

Not getting a serial means that the client is not getting a value  
back from the server that it can parse into a serial.


Can you guys dig into this and see why the mtt dbdebug file that Tim  
has at the end of this message is not getting a serial?


Thanks...


On Sep 5, 2007, at 9:24 AM, Tim Prins wrote:


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 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 other in the reports

Reported to MTTDatabase: 1 successful submit, 0 failed submits

(total of 1 result)

I have the database submit files if they would help.

Thanks,

Tim

___
mtt-users mailing list
mtt-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users


$VAR1 = {
  'exit_signal_1' => -1,
  'duration_1' => '5 seconds',
  'mpi_version' => '1.3a1r16038',
  'trial' => 0,
  'mpi_install_section_name_1' => 'bigred 32 bit gcc',
  'client_serial' => undef,
  'hostname' => 's1c2b12',
  'result_stdout_1' => '/bin/rm -f *.o *~ PI* core IMB-IO  
IMB-EXT IMB-MPI1 exe_io exe_ext exe_mpi1

touch IMB_declare.h
touch exe_mpi1 *.c; rm -rf exe_io exe_ext
make MPI1 CPP=MPI1
make[1]: Entering directory `/N/ptl01/mpiteam/bigred/20070905- 
Wednesday/pb_0/installs/d7Ri/tests/imb/IMB_2.3/src\'

mpicc  -I.  -DMPI1 -O -c IMB.c
mpicc  -I.  -DMPI1 -O -c IMB_declare.c
mpicc  -I.  -DMPI1 -O -c IMB_init.c
mpicc  -I.  -DMPI1 -O -c IMB_mem_manager.c
mpicc  -I.  -DMPI1 -O -c IMB_parse_name_mpi1.c
mpicc  -I.  -DMPI1 -O -c IMB_benchlist.c
mpicc  -I.  -DMPI1 -O -c IMB_strgs.c
mpicc  -I.  -DMPI1 -O -c IMB_err_handler.c
mpicc  -I.  -DMPI1 -O -c IMB_g_info.c
mpicc  -I.  -DMPI1 -O -c IMB_warm_up.c
mpicc  -I.  -DMPI1 -O -c IMB_output.c
mpicc  -I.  -DMPI1 -O -c IMB_pingpong.c
mpicc  -I.  -DMPI1 -O -c IMB_pingping.c
mpicc  -I.  -DMPI1 -O -c IMB_allreduce.c
mpicc  -I.  -DMPI1 -O -c IMB_reduce_scatter.c
mpicc  -I.  -DMPI1 -O -c IMB_reduce.c
mpicc  -I.  -DMPI1 -O -c IMB_exchange.c
mpicc  -I.  -DMPI1 -O -c IMB_bcast.c
mpicc  -I.  -DMPI1 -O -c IMB_barrier.c
mpicc  -I.  -DMPI1 -O -c IMB_allgather.c
mpicc  -I.  -DMPI1 -O -c IMB_allgatherv.c
mpicc  -I.  -DMPI1 -O -c IMB_alltoall.c
mpicc  -I.  -DMPI1 -O -c IMB_sendrecv.c
mpicc  -I.  -DMPI1 -O -c IMB_init_transfer.c
mpicc  -I.  -DMPI1 -O -c IMB_chk_diff.c
mpicc  -I.  -DMPI1 -O -c IMB_cpu_exploit.c
mpicc   -o IMB-MPI1 IMB.o IMB_declare.o  IMB_init.o  
IMB_mem_manager.o IMB_parse_name_mpi1.o  IMB_benchlist.o  
IMB_strgs.o IMB_err_handler.o IMB_g_info.o  IMB_warm_up.o  
IMB_output.o IMB_pingpong.o IMB_pingping.o IMB_allreduce.o  
IMB_reduce_scatter.o IMB_reduce.o IMB_exchange.o IMB_bcast.o  
IMB_barrier.o IMB_allgather.o IMB_allgatherv.o IMB_alltoall.o  
IMB_sendrecv.o IMB_init_transfer.o  IMB_chk_diff.o IMB_cpu_exploit.o
make[1]: Leaving directory `/N/ptl01/mpiteam/bigred/20070905- 
Wednesday/pb_0/installs/d7Ri/tests/imb/IMB_2.3/src\'

',
  'mpi_name' => 'ompi-nightly-trunk',
  'number_of_results' => '1',
  'phase' => 'Test Build',
  'compiler_version_1' => '3.3.3',
  'exit_value_1' => 0,
  'result_message_1' => 'Success',
  'start_timestamp_1' => 'Wed Sep  5 04:16:52 2007',
  'compiler_name_1' => 'gnu',
  'suite_name_1' => 'imb',
  'test_result_1' => 1,
  'mtt_client_version' => '2.1devel',
  'fields' =>  
'compiler_name,compiler_version,duration,exit_signal,exit_value,mpi_ge 
t_section_name,mpi_install_id,mpi_install_section_name,mpi_name,mpi_ve 
rsion,phase,result_message,result_stdout,start_timestamp,suite_name,te 
st_result',

  'mpi_install_id' => undef,
  'platform_name' => 'IU_BigRed',
  'local_username' => 'mpiteam',
  'mpi_get_section_name_1' => 'ompi-nightly-trunk'
};
___
mtt-users mailing list
mtt-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users



--
Jeff Squyres
Cisco Systems



Re: [MTT devel] [MTT users] Test runs not getting into database

2007-09-05 Thread Josh Hursey
yeah I'll try to take a look at it tomorrow. I suspect that something  
is going wrong with the relay, but I can't really think of what it  
might be at the moment.


-- Josh

On Sep 5, 2007, at 9:11 PM, Jeff Squyres wrote:


Josh / Ethan --

Not getting a serial means that the client is not getting a value
back from the server that it can parse into a serial.

Can you guys dig into this and see why the mtt dbdebug file that Tim
has at the end of this message is not getting a serial?

Thanks...


On Sep 5, 2007, at 9:24 AM, Tim Prins wrote:


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 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 other in the reports

Reported to MTTDatabase: 1 successful submit, 0 failed submits

(total of 1 result)

I have the database submit files if they would help.

Thanks,

Tim

___
mtt-users mailing list
mtt-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users


$VAR1 = {
  'exit_signal_1' => -1,
  'duration_1' => '5 seconds',
  'mpi_version' => '1.3a1r16038',
  'trial' => 0,
  'mpi_install_section_name_1' => 'bigred 32 bit gcc',
  'client_serial' => undef,
  'hostname' => 's1c2b12',
  'result_stdout_1' => '/bin/rm -f *.o *~ PI* core IMB-IO
IMB-EXT IMB-MPI1 exe_io exe_ext exe_mpi1
touch IMB_declare.h
touch exe_mpi1 *.c; rm -rf exe_io exe_ext
make MPI1 CPP=MPI1
make[1]: Entering directory `/N/ptl01/mpiteam/bigred/20070905-
Wednesday/pb_0/installs/d7Ri/tests/imb/IMB_2.3/src\'
mpicc  -I.  -DMPI1 -O -c IMB.c
mpicc  -I.  -DMPI1 -O -c IMB_declare.c
mpicc  -I.  -DMPI1 -O -c IMB_init.c
mpicc  -I.  -DMPI1 -O -c IMB_mem_manager.c
mpicc  -I.  -DMPI1 -O -c IMB_parse_name_mpi1.c
mpicc  -I.  -DMPI1 -O -c IMB_benchlist.c
mpicc  -I.  -DMPI1 -O -c IMB_strgs.c
mpicc  -I.  -DMPI1 -O -c IMB_err_handler.c
mpicc  -I.  -DMPI1 -O -c IMB_g_info.c
mpicc  -I.  -DMPI1 -O -c IMB_warm_up.c
mpicc  -I.  -DMPI1 -O -c IMB_output.c
mpicc  -I.  -DMPI1 -O -c IMB_pingpong.c
mpicc  -I.  -DMPI1 -O -c IMB_pingping.c
mpicc  -I.  -DMPI1 -O -c IMB_allreduce.c
mpicc  -I.  -DMPI1 -O -c IMB_reduce_scatter.c
mpicc  -I.  -DMPI1 -O -c IMB_reduce.c
mpicc  -I.  -DMPI1 -O -c IMB_exchange.c
mpicc  -I.  -DMPI1 -O -c IMB_bcast.c
mpicc  -I.  -DMPI1 -O -c IMB_barrier.c
mpicc  -I.  -DMPI1 -O -c IMB_allgather.c
mpicc  -I.  -DMPI1 -O -c IMB_allgatherv.c
mpicc  -I.  -DMPI1 -O -c IMB_alltoall.c
mpicc  -I.  -DMPI1 -O -c IMB_sendrecv.c
mpicc  -I.  -DMPI1 -O -c IMB_init_transfer.c
mpicc  -I.  -DMPI1 -O -c IMB_chk_diff.c
mpicc  -I.  -DMPI1 -O -c IMB_cpu_exploit.c
mpicc   -o IMB-MPI1 IMB.o IMB_declare.o  IMB_init.o
IMB_mem_manager.o IMB_parse_name_mpi1.o  IMB_benchlist.o
IMB_strgs.o IMB_err_handler.o IMB_g_info.o  IMB_warm_up.o
IMB_output.o IMB_pingpong.o IMB_pingping.o IMB_allreduce.o
IMB_reduce_scatter.o IMB_reduce.o IMB_exchange.o IMB_bcast.o
IMB_barrier.o IMB_allgather.o IMB_allgatherv.o IMB_alltoall.o
IMB_sendrecv.o IMB_init_transfer.o  IMB_chk_diff.o IMB_cpu_exploit.o
make[1]: Leaving directory `/N/ptl01/mpiteam/bigred/20070905-
Wednesday/pb_0/installs/d7Ri/tests/imb/IMB_2.3/src\'
',
  'mpi_name' => 'ompi-nightly-trunk',
  'number_of_results' => '1',
  'phase' => 'Test Build',
  'compiler_version_1' => '3.3.3',
  'exit_value_1' => 0,
  'result_message_1' => 'Success',
  'start_timestamp_1' => 'Wed Sep  5 04:16:52 2007',
  'compiler_name_1' => 'gnu',
  'suite_name_1' => 'imb',
  'test_result_1' => 1,
  'mtt_client_version' => '2.1devel',
  'fields' =>
'compiler_name,compiler_version,duration,exit_signal,exit_value,mpi_g 
e
t_section_name,mpi_install_id,mpi_install_section_name,mpi_name,mpi_v 
e
rsion,phase,result_message,result_stdout,start_timestamp,suite_name,t 
e

st_result',
  'mpi_install_id' => undef,
  'platform_name' => 'IU_BigRed',
  'local_username' => 'mpiteam',
  'mpi_get_section_name_1' => 'ompi-nightly-trunk'
};
___
mtt-users mailing list
mtt-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users



--
Jeff Squyres
Cisco Systems

___
mtt-users mailing list
mtt-us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users