[OMPI devel] Fwd: === CREATE FAILURE (trunk) ===

2013-09-13 Thread Jeff Squyres (jsquyres) 
Bah -- I forwarded the wrong build failure.  This is the shmem failure that has 
failed for the last 2 nights.


Begin forwarded message:

> From: MPI Team 
> Subject: === CREATE FAILURE (trunk) ===
> Date: September 13, 2013 3:48:47 AM GMT+02:00
> To: 
> Reply-To: 
> 
> 
> ERROR: Command returned a non-zero exist status (trunk):
>   make distcheck
> 
> Start time: Thu Sep 12 21:00:01 EDT 2013
> End time:   Thu Sep 12 21:48:46 EDT 2013
> 
> ===
> [... previous lines snipped ...]
>  CC   shmem_get.lo
>  CC   shmem_broadcast.lo
>  CC   shmem_collect.lo
>  CC   shmem_ptr.lo
>  CC   shmem_pe_accessible.lo
>  CC   shmem_addr_accessible.lo
>  CC   shmem_barrier.lo
>  CC   shmem_fence.lo
>  CC   shmem_quiet.lo
>  CC   shmem_wait.lo
>  CC   shmem_iget.lo
>  CC   shmem_iput.lo
>  CC   shmem_udcflush.lo
>  CC   shmem_udcflush_line.lo
>  CC   shmem_set_cache_inv.lo
>  CC   shmem_set_cache_line_inv.lo
>  CC   shmem_clear_cache_inv.lo
>  CC   shmem_clear_cache_line_inv.lo
>  CC   shmem_reduce.lo
>  CC   shmem_swap.lo
>  CC   shmem_cswap.lo
>  CC   shmem_fadd.lo
>  CC   shmem_finc.lo
>  CC   shmem_add.lo
>  CC   shmem_inc.lo
>  CC   shmem_clear_lock.lo
>  CC   shmem_set_lock.lo
>  CC   shmem_test_lock.lo
>  CC   shmem_lock.lo
>  CCLD libshmem_c.la
> make[4]: Leaving directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r29158/ompi/openmpi-1.9a1r29158/_build/oshmem/shmem/c'
> make[3]: Leaving directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r29158/ompi/openmpi-1.9a1r29158/_build/oshmem/shmem/c'
> Making all in shmem/f77
> make[3]: Entering directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r29158/ompi/openmpi-1.9a1r29158/_build/oshmem/shmem/f77'
>  CC   start_pes_f.lo
>  CC   num_pes_f.lo
>  CC   my_pe_f.lo
>  CC   shmem_finalize_f.lo
>  CC   shmem_barrier_all_f.lo
>  CC   shpalloc_f.lo
>  CC   shpdeallc_f.lo
> ../../../../oshmem/shmem/f77/shpdeallc_f.c: In function `shpdeallc_f':
> ../../../../oshmem/shmem/f77/shpdeallc_f.c:28: warning: cast to pointer from 
> integer of different size
> make[3]: *** [shpdeallc_f.lo] Error 1
> make[3]: Leaving directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r29158/ompi/openmpi-1.9a1r29158/_build/oshmem/shmem/f77'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r29158/ompi/openmpi-1.9a1r29158/_build/oshmem'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r29158/ompi/openmpi-1.9a1r29158/_build'
> make: *** [distcheck] Error 1
> ===
> 
> Your friendly daemon,
> Cyrador
> ___
> testing mailing list
> test...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/testing


-- 
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

[OMPI devel] Fwd: === CREATE FAILURE (trunk) ===

2011-06-22 Thread Jeff Squyres (jsquyres) 
VT guys - please fix. 

Sent from my phone. No type good. 

Begin forwarded message:

> From: MPI Team 
> Date: June 22, 2011 9:42:42 PM EDT
> To: test...@open-mpi.org
> Subject: === CREATE FAILURE (trunk) ===
> Reply-To: de...@open-mpi.org
> 

> 
> ERROR: Command returned a non-zero exist status (trunk):
>   make distcheck
> 
> Start time: Wed Jun 22 21:00:02 EDT 2011
> End time:   Wed Jun 22 21:42:42 EDT 2011
> 
> ===
> [... previous lines snipped ...]
> make[7]: Leaving directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r24808/ompi/openmpi-1.7a1r24808/_build/ompi/contrib/vt/vt/tools/opari/doc'
> make[6]: Leaving directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r24808/ompi/openmpi-1.7a1r24808/_build/ompi/contrib/vt/vt/tools/opari'
> (cd vtcpcavail && make  top_distdir=../../../../../../openmpi-1.7a1r24808 
> distdir=../../../../../../openmpi-1.7a1r24808/ompi/contrib/vt/vt/tools/vtcpcavail
>  \
> am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
> make[6]: Entering directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r24808/ompi/openmpi-1.7a1r24808/_build/ompi/contrib/vt/vt/tools/vtcpcavail'
> make[6]: Leaving directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r24808/ompi/openmpi-1.7a1r24808/_build/ompi/contrib/vt/vt/tools/vtcpcavail'
> (cd vtdyn && make  top_distdir=../../../../../../openmpi-1.7a1r24808 
> distdir=../../../../../../openmpi-1.7a1r24808/ompi/contrib/vt/vt/tools/vtdyn \
> am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
> make[6]: Entering directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r24808/ompi/openmpi-1.7a1r24808/_build/ompi/contrib/vt/vt/tools/vtdyn'
> (cd dynattlib && make  top_distdir=../../../../../../../openmpi-1.7a1r24808 
> distdir=../../../../../../../openmpi-1.7a1r24808/ompi/contrib/vt/vt/tools/vtdyn/dynattlib
>  \
> am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
> make[7]: Entering directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r24808/ompi/openmpi-1.7a1r24808/_build/ompi/contrib/vt/vt/tools/vtdyn/dynattlib'
> make[7]: Leaving directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r24808/ompi/openmpi-1.7a1r24808/_build/ompi/contrib/vt/vt/tools/vtdyn/dynattlib'
> make[6]: Leaving directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r24808/ompi/openmpi-1.7a1r24808/_build/ompi/contrib/vt/vt/tools/vtdyn'
> (cd vtfilter && make  top_distdir=../../../../../../openmpi-1.7a1r24808 
> distdir=../../../../../../openmpi-1.7a1r24808/ompi/contrib/vt/vt/tools/vtfilter
>  \
> am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
> make[6]: Entering directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r24808/ompi/openmpi-1.7a1r24808/_build/ompi/contrib/vt/vt/tools/vtfilter'
> (cd mpi && make  top_distdir=../../../../../../../openmpi-1.7a1r24808 
> distdir=../../../../../../../openmpi-1.7a1r24808/ompi/contrib/vt/vt/tools/vtfilter/mpi
>  \
> am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
> make[7]: Entering directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r24808/ompi/openmpi-1.7a1r24808/_build/ompi/contrib/vt/vt/tools/vtfilter/mpi'
> make[7]: Leaving directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r24808/ompi/openmpi-1.7a1r24808/_build/ompi/contrib/vt/vt/tools/vtfilter/mpi'
> make[6]: Leaving directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r24808/ompi/openmpi-1.7a1r24808/_build/ompi/contrib/vt/vt/tools/vtfilter'
> (cd vtjava && make  top_distdir=../../../../../../openmpi-1.7a1r24808 
> distdir=../../../../../../openmpi-1.7a1r24808/ompi/contrib/vt/vt/tools/vtjava 
> \
> am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
> make[6]: Entering directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r24808/ompi/openmpi-1.7a1r24808/_build/ompi/contrib/vt/vt/tools/vtjava'
> make[6]: Leaving directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r24808/ompi/openmpi-1.7a1r24808/_build/ompi/contrib/vt/vt/tools/vtjava'
> (cd vtlibwrapgen && make  top_distdir=../../../../../../openmpi-1.7a1r24808 
> distdir=../../../../../../openmpi-1.7a1r24808/ompi/contrib/vt/vt/tools/vtlibwrapgen
>  \
> am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
> make[6]: Entering directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r24808/ompi/openmpi-1.7a1r24808/_build/ompi/contrib/vt/vt/tools/vtlibwrapgen'
> make[6]: Leaving directory 
> `/home/mpiteam/openmpi/nightly-tarball-build-root/trunk/create-r24808/ompi/openmpi-1.7a1r24808/_build/ompi/contrib/vt/vt/tools/vtlibwrapgen'
>

Re: [OMPI devel] Fwd: === CREATE FAILURE ===

2008-01-24 Thread Jeff Squyres 
Correct.  Still looking into that problem -- we'll likely .ompi_ignore  
the v pml tonight.



On Jan 24, 2008, at 6:20 PM, Rolf Vandevaart wrote:


Hi Jeff:

Works for me.  I downloaded both the gz and bz2 formats.  Unzipped and
untarred using Solaris tar on sparc and all looks good.  No issues  
with

the long filename.

I also ran configure and saw this error:
config.status: error: cannot find input file:
ompi/mca/pml/v/vprotocol/pessimist/Makefile.in

I assume that has nothing to do with the tar issue?

Rolf



Jeff Squyres wrote:

Rolf -- I've made tarballs in the ustar format; can you give them a
whirl?

http://www.open-mpi.org/~jsquyres/unofficial/


On Jan 24, 2008, at 5:07 PM, Rolf Vandevaart wrote:


Jeff Squyres wrote:

On Jan 24, 2008, at 4:00 PM, Ralf Wildenhues wrote:

Automake forces v7 mode so that Solaris tar can untar the  
tarball,

IIRC.

You can choose how it should behave:



Can Solaris untar the other formats?


I just did a quick check on Solaris tar and GNU tar on Solaris 9 and
10.
It looks like Solaris tar can handle the v7,oldgnu,ustar,gnu.  It
seemed to handle the posix format, but spit out some complaints.

(tar: ompi/PaxHeaders.19602/test_get1_mod.c~: typeflag 'x' not
recognized, converting to regular file)

I can dig deeper into this if we need to.  From what I have read  
maybe
using the ustar format will satisfy all our needs?  We get the  
longer

filenames and compatibility with older tars.  The tar man page on
Solaris 9 and 10 does not mention a 99 character limit, it says:

"the   filename   cannot
exceed  256 characters. In addition,
it must be  possible  to  split  the
name  between parent directory names
so that the prefix is no longer than
155  characters  and  the name is no
longer than 100 characters."

Rolf

--

=
rolf.vandeva...@sun.com
781-442-3043
=
___
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel






--

=
rolf.vandeva...@sun.com
781-442-3043
=
___
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel



--
Jeff Squyres
Cisco Systems

Re: [OMPI devel] Fwd: === CREATE FAILURE ===

2008-01-24 Thread Rolf Vandevaart 

Hi Jeff:

Works for me.  I downloaded both the gz and bz2 formats.  Unzipped and 
untarred using Solaris tar on sparc and all looks good.  No issues with 
the long filename.


I also ran configure and saw this error:
config.status: error: cannot find input file: 
ompi/mca/pml/v/vprotocol/pessimist/Makefile.in


I assume that has nothing to do with the tar issue?

Rolf



Jeff Squyres wrote:
Rolf -- I've made tarballs in the ustar format; can you give them a  
whirl?


 http://www.open-mpi.org/~jsquyres/unofficial/


On Jan 24, 2008, at 5:07 PM, Rolf Vandevaart wrote:


Jeff Squyres wrote:

On Jan 24, 2008, at 4:00 PM, Ralf Wildenhues wrote:


Automake forces v7 mode so that Solaris tar can untar the tarball,
IIRC.

You can choose how it should behave:



Can Solaris untar the other formats?

I just did a quick check on Solaris tar and GNU tar on Solaris 9 and  
10.

 It looks like Solaris tar can handle the v7,oldgnu,ustar,gnu.  It
seemed to handle the posix format, but spit out some complaints.

(tar: ompi/PaxHeaders.19602/test_get1_mod.c~: typeflag 'x' not
recognized, converting to regular file)

I can dig deeper into this if we need to.  From what I have read maybe
using the ustar format will satisfy all our needs?  We get the longer
filenames and compatibility with older tars.  The tar man page on
Solaris 9 and 10 does not mention a 99 character limit, it says:

 "the   filename   cannot
 exceed  256 characters. In addition,
 it must be  possible  to  split  the
 name  between parent directory names
 so that the prefix is no longer than
 155  characters  and  the name is no
 longer than 100 characters."

Rolf

--

=
rolf.vandeva...@sun.com
781-442-3043
=
___
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel






--

=
rolf.vandeva...@sun.com
781-442-3043
=

Re: [OMPI devel] Fwd: === CREATE FAILURE ===

2008-01-24 Thread Jeff Squyres 
Rolf -- I've made tarballs in the ustar format; can you give them a  
whirl?


http://www.open-mpi.org/~jsquyres/unofficial/


On Jan 24, 2008, at 5:07 PM, Rolf Vandevaart wrote:


Jeff Squyres wrote:

On Jan 24, 2008, at 4:00 PM, Ralf Wildenhues wrote:


Automake forces v7 mode so that Solaris tar can untar the tarball,
IIRC.

You can choose how it should behave:




Can Solaris untar the other formats?



I just did a quick check on Solaris tar and GNU tar on Solaris 9 and  
10.

 It looks like Solaris tar can handle the v7,oldgnu,ustar,gnu.  It
seemed to handle the posix format, but spit out some complaints.

(tar: ompi/PaxHeaders.19602/test_get1_mod.c~: typeflag 'x' not
recognized, converting to regular file)

I can dig deeper into this if we need to.  From what I have read maybe
using the ustar format will satisfy all our needs?  We get the longer
filenames and compatibility with older tars.  The tar man page on
Solaris 9 and 10 does not mention a 99 character limit, it says:

 "the   filename   cannot
 exceed  256 characters. In addition,
 it must be  possible  to  split  the
 name  between parent directory names
 so that the prefix is no longer than
 155  characters  and  the name is no
 longer than 100 characters."

Rolf

--

=
rolf.vandeva...@sun.com
781-442-3043
=
___
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel



--
Jeff Squyres
Cisco Systems

Re: [OMPI devel] Fwd: === CREATE FAILURE ===

2008-01-24 Thread Rolf Vandevaart 

Jeff Squyres wrote:

On Jan 24, 2008, at 4:00 PM, Ralf Wildenhues wrote:

Automake forces v7 mode so that Solaris tar can untar the tarball,  
IIRC.

You can choose how it should behave:




Can Solaris untar the other formats?



I just did a quick check on Solaris tar and GNU tar on Solaris 9 and 10. 
 It looks like Solaris tar can handle the v7,oldgnu,ustar,gnu.  It 
seemed to handle the posix format, but spit out some complaints.


(tar: ompi/PaxHeaders.19602/test_get1_mod.c~: typeflag 'x' not 
recognized, converting to regular file)


I can dig deeper into this if we need to.  From what I have read maybe 
using the ustar format will satisfy all our needs?  We get the longer 
filenames and compatibility with older tars.  The tar man page on 
Solaris 9 and 10 does not mention a 99 character limit, it says:


 "the   filename   cannot
 exceed  256 characters. In addition,
 it must be  possible  to  split  the
 name  between parent directory names
 so that the prefix is no longer than
 155  characters  and  the name is no
 longer than 100 characters."

Rolf

--

=
rolf.vandeva...@sun.com
781-442-3043
=

Re: [OMPI devel] Fwd: === CREATE FAILURE ===

2008-01-24 Thread Jeff Squyres 
My question before is still relevant: can Solaris untar tarballs that  
are in the POSIX format?  If not, finding a tar that makes POSIX  
tarballs is moot.



On Jan 24, 2008, at 4:44 PM, Paul H. Hargrove wrote:


IMHO shortening the names now just delays dealing with the problem.

I see 2 possible approaches to a long-term fix:
1) add some machinery on the build system to complain when a filename
would exceed 99 chars (before the file gets into svn).
2) probe at configure time for a $TAR command that produces the  
POSIX format


I favor #2

-Paul

Aurélien Bouteiller wrote:

Ok, I'll change the filenames.

Aurelien

Le 24 janv. 08 à 15:43, Brian W. Barrett a écrit :



Automake forces v7 mode so that Solaris tar can untar the tarball,
IIRC.

Brian

On Thu, 24 Jan 2008, Aurélien Bouteiller wrote:



According to posix, tar should not limit the file name length. Only
the v7 implementation of tar is limited to 99 characters. GNU tar  
has

never been limited in the number of characters file names can have.
You should check with tar --help that tar on your machine  
defaults to
format=gnu or format=posix. If it defaults to format=v7 I am  
curious

why. Are you using solaris ?

Aurelien

Le 24 janv. 08 à 15:18, Jeff Squyres a écrit :



I'm trying to replicate and getting a lot of these:

tar: openmpi-1.3a1r17212M/ompi/mca/pml/v/vprotocol/mca/vprotocol/
pessimist/vprotocol_pessimist_sender_based.c: file name is too  
long

(max 99); not dumped
tar: openmpi-1.3a1r17212M/ompi/mca/pml/v/vprotocol/mca/vprotocol/
pessimist/vprotocol_pessimist_component.c: file name is too long
(max
99); not dumped

I'll bet that this is the real problem.  GNU tar on linux defaults
to
99 characters max, and the _component.c filename is 102, for
example.

Can you shorten your names?



[snip]

--
Paul H. Hargrove  phhargr...@lbl.gov
Future Technologies Group
HPC Research Department   Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900


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



--
Jeff Squyres
Cisco Systems

Re: [OMPI devel] Fwd: === CREATE FAILURE ===

2008-01-24 Thread Paul H. Hargrove 

IMHO shortening the names now just delays dealing with the problem.

I see 2 possible approaches to a long-term fix:
1) add some machinery on the build system to complain when a filename 
would exceed 99 chars (before the file gets into svn).

2) probe at configure time for a $TAR command that produces the POSIX format

I favor #2

-Paul

Aurélien Bouteiller wrote:

Ok, I'll change the filenames.

Aurelien

Le 24 janv. 08 à 15:43, Brian W. Barrett a écrit :

  
Automake forces v7 mode so that Solaris tar can untar the tarball,  
IIRC.


Brian

On Thu, 24 Jan 2008, Aurélien Bouteiller wrote:



According to posix, tar should not limit the file name length. Only
the v7 implementation of tar is limited to 99 characters. GNU tar has
never been limited in the number of characters file names can have.
You should check with tar --help that tar on your machine defaults to
format=gnu or format=posix. If it defaults to format=v7 I am curious
why. Are you using solaris ?

Aurelien

Le 24 janv. 08 à 15:18, Jeff Squyres a écrit :

  

I'm trying to replicate and getting a lot of these:

tar: openmpi-1.3a1r17212M/ompi/mca/pml/v/vprotocol/mca/vprotocol/
pessimist/vprotocol_pessimist_sender_based.c: file name is too long
(max 99); not dumped
tar: openmpi-1.3a1r17212M/ompi/mca/pml/v/vprotocol/mca/vprotocol/
pessimist/vprotocol_pessimist_component.c: file name is too long  
(max

99); not dumped

I'll bet that this is the real problem.  GNU tar on linux defaults  
to
99 characters max, and the _component.c filename is 102, for  
example.


Can you shorten your names?



[snip]

--
Paul H. Hargrove  phhargr...@lbl.gov
Future Technologies Group
HPC Research Department   Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900

Re: [OMPI devel] Fwd: === CREATE FAILURE ===

2008-01-24 Thread Jeff Squyres 

On Jan 24, 2008, at 4:00 PM, Ralf Wildenhues wrote:

Automake forces v7 mode so that Solaris tar can untar the tarball,  
IIRC.


You can choose how it should behave:






Can Solaris untar the other formats?

--
Jeff Squyres
Cisco Systems

Re: [OMPI devel] Fwd: === CREATE FAILURE ===

2008-01-24 Thread Ralf Wildenhues 
Hello,

* Brian W. Barrett wrote on Thu, Jan 24, 2008 at 09:43:12PM CET:
> Automake forces v7 mode so that Solaris tar can untar the tarball, IIRC.

You can choose how it should behave:



Cheers,
Ralf

Re: [OMPI devel] Fwd: === CREATE FAILURE ===

2008-01-24 Thread Brian W. Barrett 

Automake forces v7 mode so that Solaris tar can untar the tarball, IIRC.

Brian

On Thu, 24 Jan 2008, Aurélien Bouteiller wrote:


According to posix, tar should not limit the file name length. Only
the v7 implementation of tar is limited to 99 characters. GNU tar has
never been limited in the number of characters file names can have.
You should check with tar --help that tar on your machine defaults to
format=gnu or format=posix. If it defaults to format=v7 I am curious
why. Are you using solaris ?

Aurelien

Le 24 janv. 08 à 15:18, Jeff Squyres a écrit :


I'm trying to replicate and getting a lot of these:

tar: openmpi-1.3a1r17212M/ompi/mca/pml/v/vprotocol/mca/vprotocol/
pessimist/vprotocol_pessimist_sender_based.c: file name is too long
(max 99); not dumped
tar: openmpi-1.3a1r17212M/ompi/mca/pml/v/vprotocol/mca/vprotocol/
pessimist/vprotocol_pessimist_component.c: file name is too long (max
99); not dumped

I'll bet that this is the real problem.  GNU tar on linux defaults to
99 characters max, and the _component.c filename is 102, for example.

Can you shorten your names?


On Jan 24, 2008, at 3:02 PM, George Bosilca wrote:


We cannot reproduce this one. A simple "make checkdist" exit long
before doing anything in the ompi directory. It is difficult to see
where exactly it fails, but it is somewhere in the opal directory. I
suspect the new carto framework ...

Thanks,
  george.

On Jan 24, 2008, at 7:12 AM, Jeff Squyres wrote:


Aurelien --

Can you fix please?  Last night's tests didn't run because of this
failure.


Begin forwarded message:


From: MPI Team 
Date: January 23, 2008 9:13:30 PM EST
To: test...@open-mpi.org
Subject: === CREATE FAILURE ===
Reply-To: de...@open-mpi.org


ERROR: Command returned a non-zero exist status
   make -j 4 distcheck

Start time: Wed Jan 23 21:00:08 EST 2008
End time:   Wed Jan 23 21:13:30 EST 2008

=
=
=
=
===
[... previous lines snipped ...]
config.status: creating orte/mca/snapc/Makefile
config.status: creating orte/mca/snapc/full/Makefile
config.status: creating ompi/mca/allocator/Makefile
config.status: creating ompi/mca/allocator/basic/Makefile
config.status: creating ompi/mca/allocator/bucket/Makefile
config.status: creating ompi/mca/bml/Makefile
config.status: creating ompi/mca/bml/r2/Makefile
config.status: creating ompi/mca/btl/Makefile
config.status: creating ompi/mca/btl/gm/Makefile
config.status: creating ompi/mca/btl/mx/Makefile
config.status: creating ompi/mca/btl/ofud/Makefile
config.status: creating ompi/mca/btl/openib/Makefile
config.status: creating ompi/mca/btl/portals/Makefile
config.status: creating ompi/mca/btl/sctp/Makefile
config.status: creating ompi/mca/btl/self/Makefile
config.status: creating ompi/mca/btl/sm/Makefile
config.status: creating ompi/mca/btl/tcp/Makefile
config.status: creating ompi/mca/btl/udapl/Makefile
config.status: creating ompi/mca/coll/Makefile
config.status: creating ompi/mca/coll/basic/Makefile
config.status: creating ompi/mca/coll/inter/Makefile
config.status: creating ompi/mca/coll/self/Makefile
config.status: creating ompi/mca/coll/sm/Makefile
config.status: creating ompi/mca/coll/tuned/Makefile
config.status: creating ompi/mca/common/Makefile
config.status: creating ompi/mca/common/mx/Makefile
config.status: creating ompi/mca/common/portals/Makefile
config.status: creating ompi/mca/common/sm/Makefile
config.status: creating ompi/mca/crcp/Makefile
config.status: creating ompi/mca/crcp/coord/Makefile
config.status: creating ompi/mca/io/Makefile
config.status: creating ompi/mca/io/romio/Makefile
config.status: creating ompi/mca/mpool/Makefile
config.status: creating ompi/mca/mpool/rdma/Makefile
config.status: creating ompi/mca/mpool/sm/Makefile
config.status: creating ompi/mca/mtl/Makefile
config.status: creating ompi/mca/mtl/mx/Makefile
config.status: creating ompi/mca/mtl/portals/Makefile
config.status: creating ompi/mca/mtl/psm/Makefile
config.status: creating ompi/mca/osc/Makefile
config.status: creating ompi/mca/osc/pt2pt/Makefile
config.status: creating ompi/mca/osc/rdma/Makefile
config.status: creating ompi/mca/pml/Makefile
config.status: creating ompi/mca/pml/cm/Makefile
config.status: creating ompi/mca/pml/crcpw/Makefile
config.status: creating ompi/mca/pml/dr/Makefile
config.status: creating ompi/mca/pml/ob1/Makefile
config.status: creating ompi/mca/pml/v/vprotocol/Makefile
config.status: error: cannot find input file: ompi/mca/pml/v/
vprotocol/pessimist/Makefile.in
make: *** [distcheck] Error 1
=
=
=
=
===

Your friendly daemon,
Cyrador
___
testing mailing list
test...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/testing



--
Jeff Squyres
Cisco Systems

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

Re: [OMPI devel] Fwd: === CREATE FAILURE ===

2008-01-24 Thread Aurélien Bouteiller 
According to posix, tar should not limit the file name length. Only  
the v7 implementation of tar is limited to 99 characters. GNU tar has  
never been limited in the number of characters file names can have.  
You should check with tar --help that tar on your machine defaults to  
format=gnu or format=posix. If it defaults to format=v7 I am curious  
why. Are you using solaris ?


Aurelien

Le 24 janv. 08 à 15:18, Jeff Squyres a écrit :


I'm trying to replicate and getting a lot of these:

tar: openmpi-1.3a1r17212M/ompi/mca/pml/v/vprotocol/mca/vprotocol/
pessimist/vprotocol_pessimist_sender_based.c: file name is too long
(max 99); not dumped
tar: openmpi-1.3a1r17212M/ompi/mca/pml/v/vprotocol/mca/vprotocol/
pessimist/vprotocol_pessimist_component.c: file name is too long (max
99); not dumped

I'll bet that this is the real problem.  GNU tar on linux defaults to
99 characters max, and the _component.c filename is 102, for example.

Can you shorten your names?


On Jan 24, 2008, at 3:02 PM, George Bosilca wrote:


We cannot reproduce this one. A simple "make checkdist" exit long
before doing anything in the ompi directory. It is difficult to see
where exactly it fails, but it is somewhere in the opal directory. I
suspect the new carto framework ...

Thanks,
  george.

On Jan 24, 2008, at 7:12 AM, Jeff Squyres wrote:


Aurelien --

Can you fix please?  Last night's tests didn't run because of this
failure.


Begin forwarded message:


From: MPI Team 
Date: January 23, 2008 9:13:30 PM EST
To: test...@open-mpi.org
Subject: === CREATE FAILURE ===
Reply-To: de...@open-mpi.org


ERROR: Command returned a non-zero exist status
   make -j 4 distcheck

Start time: Wed Jan 23 21:00:08 EST 2008
End time:   Wed Jan 23 21:13:30 EST 2008

=
=
=
= 
===

[... previous lines snipped ...]
config.status: creating orte/mca/snapc/Makefile
config.status: creating orte/mca/snapc/full/Makefile
config.status: creating ompi/mca/allocator/Makefile
config.status: creating ompi/mca/allocator/basic/Makefile
config.status: creating ompi/mca/allocator/bucket/Makefile
config.status: creating ompi/mca/bml/Makefile
config.status: creating ompi/mca/bml/r2/Makefile
config.status: creating ompi/mca/btl/Makefile
config.status: creating ompi/mca/btl/gm/Makefile
config.status: creating ompi/mca/btl/mx/Makefile
config.status: creating ompi/mca/btl/ofud/Makefile
config.status: creating ompi/mca/btl/openib/Makefile
config.status: creating ompi/mca/btl/portals/Makefile
config.status: creating ompi/mca/btl/sctp/Makefile
config.status: creating ompi/mca/btl/self/Makefile
config.status: creating ompi/mca/btl/sm/Makefile
config.status: creating ompi/mca/btl/tcp/Makefile
config.status: creating ompi/mca/btl/udapl/Makefile
config.status: creating ompi/mca/coll/Makefile
config.status: creating ompi/mca/coll/basic/Makefile
config.status: creating ompi/mca/coll/inter/Makefile
config.status: creating ompi/mca/coll/self/Makefile
config.status: creating ompi/mca/coll/sm/Makefile
config.status: creating ompi/mca/coll/tuned/Makefile
config.status: creating ompi/mca/common/Makefile
config.status: creating ompi/mca/common/mx/Makefile
config.status: creating ompi/mca/common/portals/Makefile
config.status: creating ompi/mca/common/sm/Makefile
config.status: creating ompi/mca/crcp/Makefile
config.status: creating ompi/mca/crcp/coord/Makefile
config.status: creating ompi/mca/io/Makefile
config.status: creating ompi/mca/io/romio/Makefile
config.status: creating ompi/mca/mpool/Makefile
config.status: creating ompi/mca/mpool/rdma/Makefile
config.status: creating ompi/mca/mpool/sm/Makefile
config.status: creating ompi/mca/mtl/Makefile
config.status: creating ompi/mca/mtl/mx/Makefile
config.status: creating ompi/mca/mtl/portals/Makefile
config.status: creating ompi/mca/mtl/psm/Makefile
config.status: creating ompi/mca/osc/Makefile
config.status: creating ompi/mca/osc/pt2pt/Makefile
config.status: creating ompi/mca/osc/rdma/Makefile
config.status: creating ompi/mca/pml/Makefile
config.status: creating ompi/mca/pml/cm/Makefile
config.status: creating ompi/mca/pml/crcpw/Makefile
config.status: creating ompi/mca/pml/dr/Makefile
config.status: creating ompi/mca/pml/ob1/Makefile
config.status: creating ompi/mca/pml/v/vprotocol/Makefile
config.status: error: cannot find input file: ompi/mca/pml/v/
vprotocol/pessimist/Makefile.in
make: *** [distcheck] Error 1
=
=
=
= 
===


Your friendly daemon,
Cyrador
___
testing mailing list
test...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/testing



--
Jeff Squyres
Cisco Systems

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


___
devel mailing list
de...@open-mpi.org

Re: [OMPI devel] Fwd: === CREATE FAILURE ===

2008-01-24 Thread Jeff Squyres 

I'm trying to replicate and getting a lot of these:

tar: openmpi-1.3a1r17212M/ompi/mca/pml/v/vprotocol/mca/vprotocol/ 
pessimist/vprotocol_pessimist_sender_based.c: file name is too long  
(max 99); not dumped
tar: openmpi-1.3a1r17212M/ompi/mca/pml/v/vprotocol/mca/vprotocol/ 
pessimist/vprotocol_pessimist_component.c: file name is too long (max  
99); not dumped


I'll bet that this is the real problem.  GNU tar on linux defaults to  
99 characters max, and the _component.c filename is 102, for example.


Can you shorten your names?


On Jan 24, 2008, at 3:02 PM, George Bosilca wrote:

We cannot reproduce this one. A simple "make checkdist" exit long  
before doing anything in the ompi directory. It is difficult to see  
where exactly it fails, but it is somewhere in the opal directory. I  
suspect the new carto framework ...


 Thanks,
   george.

On Jan 24, 2008, at 7:12 AM, Jeff Squyres wrote:


Aurelien --

Can you fix please?  Last night's tests didn't run because of this
failure.


Begin forwarded message:


From: MPI Team 
Date: January 23, 2008 9:13:30 PM EST
To: test...@open-mpi.org
Subject: === CREATE FAILURE ===
Reply-To: de...@open-mpi.org


ERROR: Command returned a non-zero exist status
make -j 4 distcheck

Start time: Wed Jan 23 21:00:08 EST 2008
End time:   Wed Jan 23 21:13:30 EST 2008

=
= 
= 


[... previous lines snipped ...]
config.status: creating orte/mca/snapc/Makefile
config.status: creating orte/mca/snapc/full/Makefile
config.status: creating ompi/mca/allocator/Makefile
config.status: creating ompi/mca/allocator/basic/Makefile
config.status: creating ompi/mca/allocator/bucket/Makefile
config.status: creating ompi/mca/bml/Makefile
config.status: creating ompi/mca/bml/r2/Makefile
config.status: creating ompi/mca/btl/Makefile
config.status: creating ompi/mca/btl/gm/Makefile
config.status: creating ompi/mca/btl/mx/Makefile
config.status: creating ompi/mca/btl/ofud/Makefile
config.status: creating ompi/mca/btl/openib/Makefile
config.status: creating ompi/mca/btl/portals/Makefile
config.status: creating ompi/mca/btl/sctp/Makefile
config.status: creating ompi/mca/btl/self/Makefile
config.status: creating ompi/mca/btl/sm/Makefile
config.status: creating ompi/mca/btl/tcp/Makefile
config.status: creating ompi/mca/btl/udapl/Makefile
config.status: creating ompi/mca/coll/Makefile
config.status: creating ompi/mca/coll/basic/Makefile
config.status: creating ompi/mca/coll/inter/Makefile
config.status: creating ompi/mca/coll/self/Makefile
config.status: creating ompi/mca/coll/sm/Makefile
config.status: creating ompi/mca/coll/tuned/Makefile
config.status: creating ompi/mca/common/Makefile
config.status: creating ompi/mca/common/mx/Makefile
config.status: creating ompi/mca/common/portals/Makefile
config.status: creating ompi/mca/common/sm/Makefile
config.status: creating ompi/mca/crcp/Makefile
config.status: creating ompi/mca/crcp/coord/Makefile
config.status: creating ompi/mca/io/Makefile
config.status: creating ompi/mca/io/romio/Makefile
config.status: creating ompi/mca/mpool/Makefile
config.status: creating ompi/mca/mpool/rdma/Makefile
config.status: creating ompi/mca/mpool/sm/Makefile
config.status: creating ompi/mca/mtl/Makefile
config.status: creating ompi/mca/mtl/mx/Makefile
config.status: creating ompi/mca/mtl/portals/Makefile
config.status: creating ompi/mca/mtl/psm/Makefile
config.status: creating ompi/mca/osc/Makefile
config.status: creating ompi/mca/osc/pt2pt/Makefile
config.status: creating ompi/mca/osc/rdma/Makefile
config.status: creating ompi/mca/pml/Makefile
config.status: creating ompi/mca/pml/cm/Makefile
config.status: creating ompi/mca/pml/crcpw/Makefile
config.status: creating ompi/mca/pml/dr/Makefile
config.status: creating ompi/mca/pml/ob1/Makefile
config.status: creating ompi/mca/pml/v/vprotocol/Makefile
config.status: error: cannot find input file: ompi/mca/pml/v/
vprotocol/pessimist/Makefile.in
make: *** [distcheck] Error 1
=
= 
= 



Your friendly daemon,
Cyrador
___
testing mailing list
test...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/testing



--
Jeff Squyres
Cisco Systems

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


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



--
Jeff Squyres
Cisco Systems

Re: [OMPI devel] Fwd: === CREATE FAILURE ===

2008-01-24 Thread George Bosilca 
We cannot reproduce this one. A simple "make checkdist" exit long  
before doing anything in the ompi directory. It is difficult to see  
where exactly it fails, but it is somewhere in the opal directory. I  
suspect the new carto framework ...


  Thanks,
george.

On Jan 24, 2008, at 7:12 AM, Jeff Squyres wrote:


Aurelien --

Can you fix please?  Last night's tests didn't run because of this
failure.


Begin forwarded message:


From: MPI Team 
Date: January 23, 2008 9:13:30 PM EST
To: test...@open-mpi.org
Subject: === CREATE FAILURE ===
Reply-To: de...@open-mpi.org


ERROR: Command returned a non-zero exist status
 make -j 4 distcheck

Start time: Wed Jan 23 21:00:08 EST 2008
End time:   Wed Jan 23 21:13:30 EST 2008

=
= 
=

[... previous lines snipped ...]
config.status: creating orte/mca/snapc/Makefile
config.status: creating orte/mca/snapc/full/Makefile
config.status: creating ompi/mca/allocator/Makefile
config.status: creating ompi/mca/allocator/basic/Makefile
config.status: creating ompi/mca/allocator/bucket/Makefile
config.status: creating ompi/mca/bml/Makefile
config.status: creating ompi/mca/bml/r2/Makefile
config.status: creating ompi/mca/btl/Makefile
config.status: creating ompi/mca/btl/gm/Makefile
config.status: creating ompi/mca/btl/mx/Makefile
config.status: creating ompi/mca/btl/ofud/Makefile
config.status: creating ompi/mca/btl/openib/Makefile
config.status: creating ompi/mca/btl/portals/Makefile
config.status: creating ompi/mca/btl/sctp/Makefile
config.status: creating ompi/mca/btl/self/Makefile
config.status: creating ompi/mca/btl/sm/Makefile
config.status: creating ompi/mca/btl/tcp/Makefile
config.status: creating ompi/mca/btl/udapl/Makefile
config.status: creating ompi/mca/coll/Makefile
config.status: creating ompi/mca/coll/basic/Makefile
config.status: creating ompi/mca/coll/inter/Makefile
config.status: creating ompi/mca/coll/self/Makefile
config.status: creating ompi/mca/coll/sm/Makefile
config.status: creating ompi/mca/coll/tuned/Makefile
config.status: creating ompi/mca/common/Makefile
config.status: creating ompi/mca/common/mx/Makefile
config.status: creating ompi/mca/common/portals/Makefile
config.status: creating ompi/mca/common/sm/Makefile
config.status: creating ompi/mca/crcp/Makefile
config.status: creating ompi/mca/crcp/coord/Makefile
config.status: creating ompi/mca/io/Makefile
config.status: creating ompi/mca/io/romio/Makefile
config.status: creating ompi/mca/mpool/Makefile
config.status: creating ompi/mca/mpool/rdma/Makefile
config.status: creating ompi/mca/mpool/sm/Makefile
config.status: creating ompi/mca/mtl/Makefile
config.status: creating ompi/mca/mtl/mx/Makefile
config.status: creating ompi/mca/mtl/portals/Makefile
config.status: creating ompi/mca/mtl/psm/Makefile
config.status: creating ompi/mca/osc/Makefile
config.status: creating ompi/mca/osc/pt2pt/Makefile
config.status: creating ompi/mca/osc/rdma/Makefile
config.status: creating ompi/mca/pml/Makefile
config.status: creating ompi/mca/pml/cm/Makefile
config.status: creating ompi/mca/pml/crcpw/Makefile
config.status: creating ompi/mca/pml/dr/Makefile
config.status: creating ompi/mca/pml/ob1/Makefile
config.status: creating ompi/mca/pml/v/vprotocol/Makefile
config.status: error: cannot find input file: ompi/mca/pml/v/
vprotocol/pessimist/Makefile.in
make: *** [distcheck] Error 1
=
= 
=


Your friendly daemon,
Cyrador
___
testing mailing list
test...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/testing



--
Jeff Squyres
Cisco Systems

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




smime.p7s
Description: S/MIME cryptographic signature

[OMPI devel] Fwd: === CREATE FAILURE ===

2008-01-24 Thread Jeff Squyres 

Aurelien --

Can you fix please?  Last night's tests didn't run because of this  
failure.



Begin forwarded message:


From: MPI Team 
Date: January 23, 2008 9:13:30 PM EST
To: test...@open-mpi.org
Subject: === CREATE FAILURE ===
Reply-To: de...@open-mpi.org


ERROR: Command returned a non-zero exist status
  make -j 4 distcheck

Start time: Wed Jan 23 21:00:08 EST 2008
End time:   Wed Jan 23 21:13:30 EST 2008

= 
==

[... previous lines snipped ...]
config.status: creating orte/mca/snapc/Makefile
config.status: creating orte/mca/snapc/full/Makefile
config.status: creating ompi/mca/allocator/Makefile
config.status: creating ompi/mca/allocator/basic/Makefile
config.status: creating ompi/mca/allocator/bucket/Makefile
config.status: creating ompi/mca/bml/Makefile
config.status: creating ompi/mca/bml/r2/Makefile
config.status: creating ompi/mca/btl/Makefile
config.status: creating ompi/mca/btl/gm/Makefile
config.status: creating ompi/mca/btl/mx/Makefile
config.status: creating ompi/mca/btl/ofud/Makefile
config.status: creating ompi/mca/btl/openib/Makefile
config.status: creating ompi/mca/btl/portals/Makefile
config.status: creating ompi/mca/btl/sctp/Makefile
config.status: creating ompi/mca/btl/self/Makefile
config.status: creating ompi/mca/btl/sm/Makefile
config.status: creating ompi/mca/btl/tcp/Makefile
config.status: creating ompi/mca/btl/udapl/Makefile
config.status: creating ompi/mca/coll/Makefile
config.status: creating ompi/mca/coll/basic/Makefile
config.status: creating ompi/mca/coll/inter/Makefile
config.status: creating ompi/mca/coll/self/Makefile
config.status: creating ompi/mca/coll/sm/Makefile
config.status: creating ompi/mca/coll/tuned/Makefile
config.status: creating ompi/mca/common/Makefile
config.status: creating ompi/mca/common/mx/Makefile
config.status: creating ompi/mca/common/portals/Makefile
config.status: creating ompi/mca/common/sm/Makefile
config.status: creating ompi/mca/crcp/Makefile
config.status: creating ompi/mca/crcp/coord/Makefile
config.status: creating ompi/mca/io/Makefile
config.status: creating ompi/mca/io/romio/Makefile
config.status: creating ompi/mca/mpool/Makefile
config.status: creating ompi/mca/mpool/rdma/Makefile
config.status: creating ompi/mca/mpool/sm/Makefile
config.status: creating ompi/mca/mtl/Makefile
config.status: creating ompi/mca/mtl/mx/Makefile
config.status: creating ompi/mca/mtl/portals/Makefile
config.status: creating ompi/mca/mtl/psm/Makefile
config.status: creating ompi/mca/osc/Makefile
config.status: creating ompi/mca/osc/pt2pt/Makefile
config.status: creating ompi/mca/osc/rdma/Makefile
config.status: creating ompi/mca/pml/Makefile
config.status: creating ompi/mca/pml/cm/Makefile
config.status: creating ompi/mca/pml/crcpw/Makefile
config.status: creating ompi/mca/pml/dr/Makefile
config.status: creating ompi/mca/pml/ob1/Makefile
config.status: creating ompi/mca/pml/v/vprotocol/Makefile
config.status: error: cannot find input file: ompi/mca/pml/v/ 
vprotocol/pessimist/Makefile.in

make: *** [distcheck] Error 1
= 
==


Your friendly daemon,
Cyrador
___
testing mailing list
test...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/testing



--
Jeff Squyres
Cisco Systems