Re: [OMPI devel] 1.7.x support statement

On Oct 4, 2013, at 8:38 AM, marco atzeri wrote: > At first glance it does not seems particular user friendly nor with a clear > HOWTO guide for good start. How's this for a start: https://svn.open-mpi.org/trac/mtt/wiki/OMPITesting > Additional LWP::Protocol::https

Re: [OMPI devel] oshmem 32 bit compile failures

On Oct 4, 2013, at 1:51 PM, Mike Dubman wrote: > the code passes compilation with gcc/icc 32bit toolkits. > We don`t have absoft fortran compiler in the lab, is there any way we can > have it to try? No -- Absoft themselves run the test and simply upload to our MTT

Re: [OMPI devel] oshmem 32 bit compile failures

Hi, the code passes compilation with gcc/icc 32bit toolkits. We don`t have absoft fortran compiler in the lab, is there any way we can have it to try? Igor has some wild guess about what problem can be and created patch (attached). Could you try to apply it on OMPI tree and check with absoft

Re: [OMPI devel] 1.6.5 large matrix test doesn't pass (decode) ?

It is a bug in the test program, test/datatype/ddt_raw.c, and it was fixed at r24328 in trunk. https://svn.open-mpi.org/trac/ompi/changeset/24328 I've confirmed the failure occurs with plain v1.6.5 and it doesn't occur with patched v1.6.5. Thanks, KAWASHIMA Takahiro > Not sure if this is

Re: [OMPI devel] 1.7.x support statement

Il 10/4/2013 1:47 PM, Jeff Squyres (jsquyres) ha scritto: Good call; yes. Marco: is there any chance you can run Open MPI through the MPI Testing Tool (MTT) on a regular basis, and submit your results to mtt.open-mpi.org? You can run as few or as many tests a night as you want. For example,

Re: [OMPI devel] 1.7.x support statement

Good call; yes. Marco: is there any chance you can run Open MPI through the MPI Testing Tool (MTT) on a regular basis, and submit your results to mtt.open-mpi.org? You can run as few or as many tests a night as you want. For example, the Absoft compiler company runs only hello world and ring

[OMPI devel] oshmem 32 bit compile failures

Absoft is seeing compile failures for oshmem. Here's one example: http://mtt.open-mpi.org/index.php?do_redir=2132 If you scroll down through the stderr, it looks like there's a problem in oshmsm/op/op.c. Perhaps it's just a missing header file, or some code in an #if/#else that isn't

Re: [OMPI devel] 1.7.x support statement

Il 10/4/2013 1:08 PM, Jeff Squyres (jsquyres) ha scritto: This is in the README -- is it still accurate? I'm thinking that all Solaris support should move to the "lightly but not fully tested" category, for example: - - Systems that have been tested are: - Linux (various

[OMPI devel] RFC: remove udapl BTL

WHAT: Remove the udapl BTL from the trunk (it's not in v1.7) WHY: No one is using it WHERE: README, config/ompi_check_udapl.m4, and ompi/mca/btl/udapl TIMEOUT: Tuesday October 15 teleconf - While editing the 1.7.x README this morning, I noticed: - we still document --with-udapl - the

[OMPI devel] 1.7.x support statement

This is in the README -- is it still accurate? I'm thinking that all Solaris support should move to the "lightly but not fully tested" category, for example: - - Systems that have been tested are: - Linux (various flavors/distros), 32 bit, with

[OMPI devel] Please check 1.7.3 NEWS bullets

In preparation for 1.7.3, I updated the NEWS bullets. Please check and verify that your favorite items are listed (and are correct): https://svn.open-mpi.org/trac/ompi/browser/branches/v1.7/NEWS#L56 -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to:

[OMPI devel] 1.6.5 large matrix test doesn't pass (decode) ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Not sure if this is important, or expected, but I ran a make check out of interest after seeing recent emails and saw the final one of these tests be reported as "NOT PASSED" (it seems to be the only failure). No idea if this is important or not.