From: Ethan Mallove (ethan.mallove_at_[hidden])
Date: 2006-10-10 14:55:10
The problem is configure_arguments is not large enough to
hold:
--enable-debug --disable-mpi-f90
CC=cc CXX=CC FC=f90 F77=f77
CFLAGS="-xarch=v8plusa -xO5 -xmemalign=8s"
CXXFLAGS="-xarch=v8plusa -xO5 -xmemalign=8s"
FFLAGS="-xarch=v8plusa -xO5 -xmemalign=8s"
FCFLAGS="-xarch=v8plusa -xO5 -xmemalign=8s -KPIC"
Though isn't the above only 245 characters long? Anyhow, do
we want an upper bound on this column? I will make it an
unbound text for now (like stdout/stderr).
-Ethan
On Tue, Oct/10/2006 02:28:44PM, Ethan Mallove wrote:
> I'm missing some data. I see the following in my --debug
> output:
>
> ...
> Build was a success
> Evaluating: require MTT::Reporter::MTTDatabase
> Evaluating: $ret =
> &MTT::Reporter::MTTDatabase::Submit(@args)
> MTTDatabase reporter
> Submitting to MTTDatabase...
> MTTDatabase submit complete
> Writing to MTTDatabase debug file:
> /workspace/em162155/hpc/mtt/cron/ompi-core-testers/sparc/32/trunk/mttdatabase_debug.burl-ct-v440-4.20061010.111631.0.txt
> Debug MTTDatabase file write complete
> >> 1 successful submit, 0 failed submits (total of 1 result)
> Completed MPI install successfully
> *** MPI install phase complete
> ...
>
> The debug file contains a success for a sparc/32-bit/trunk
> MPI Install, but curiously this result doesn't seem to have
> arrived in the 'mtt' db (around Tue Oct 10 15:48:39 2006).
>
> mtt=> SELECT platform_hardware, os_name, mpi_name,
> mpi_version, platform_id, (CASE WHEN success='t' THEN
> 'pass_case_installs' END) as pass, (CASE WHEN success='f'
> THEN 'fail_case_installs' END) as fail FROM installs JOIN
> once USING (run_index) WHERE start_test_timestamp >
> date_trunc('day', now()) AND os_name = 'SunOS';
>
> platform_hardware | os_name | mpi_name | mpi_version | platform_id |pass|fail
> -------------------+---------+--------------------+-------------+-------------+----+-----
> i86pc | SunOS | ompi-nightly-trunk | 1.3a1r12066 | Sun 32-bit | | 1
> i86pc | SunOS | ompi-nightly-trunk | 1.3a1r12066 | Sun 64-bit | | 1
> i86pc | SunOS | ompi-nightly-v1.2 | 1.2a1r12050 | Sun 32-bit | 1 |
> i86pc | SunOS | ompi-nightly-v1.2 | 1.2a1r12050 | Sun 64-bit | 1 |
> sun4u | SunOS | ompi-nightly-trunk | 1.3a1r12066 | Sun 64-bit | | 1
> sun4u | SunOS | ompi-nightly-v1.2 | 1.2a1r12050 | Sun 64-bit | 1 |
> i86pc | SunOS | ompi-nightly-trunk | 1.3a1r12069 | Sun 32-bit | | 1
> i86pc | SunOS | ompi-nightly-trunk | 1.3a1r12069 | Sun 32-bit | 1 |
> i86pc | SunOS | ompi-nightly-trunk | 1.3a1r12069 | Sun 64-bit | 1 |
> sun4u | SunOS | ompi-nightly-trunk | 1.3a1r12069 | Sun 64-bit | 1 |
> (10 rows)
>
> mtt=> select timestamp without time zone 'now()';
> timestamp
> ----------------------------
> 2006-10-10 14:06:22.251253
> (1 row)
>
> Note the missing sparc/32-bit/trunk result. Oddly, the Test
> Builds and Test Runs for this submission did go through.
> I've put in a request to get access to /var/log/pgsql to see
> if I can see a failed INSERT.
>
> -Ethan
> _______________________________________________
> mtt-users mailing list
> mtt-users_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users