PTP/testing/6.x

Test Plan for PTP 6.x Release

This plan describes the tests that will be undertaken to verify the 6.x series of PTP releases - Eclipse 6.0.0 will be available June 27, 2012 with the Eclipse Juno (4.2) Simultaneous release.

Test Setup

The following steps should be carried out prior to testing PTP. Refer to the release notes for the appropriate PTP version if necessary.

1. Make sure you have Java 1.5 or later
2. Start with a fresh Eclipse installation
3. Use a new workspace for testing (or remove old testing workspaces)
4. Download and install the "Eclipse IDE for Parallel Application Developers" package
   • from http://eclipse.org/downloads Select "Developer Builds" at the top to get pre-release downloads.
5. Depending on your test plan requirements, install PTP server components using instructions from the 6.0 release notes.
6. Launch Eclipse on the test machine.
7. If you require an MPI program for testing, use the following code:

#include <stdio.h>

#include <mpi.h> 
int main(int argc, char *argv[]) 
{ 
  int i, rank; 
  MPI_Init(&argc, &argv); 
  MPI_Comm_rank(MPI_COMM_WORLD, &rank); 

  for (i = 0; i < 10; i++) 
  { 
     printf("hello from %d loop %d\n", rank, i); 
     sleep(1); 
  } 

  MPI_Finalize(); 
  return 0; 
}

Test Iterations

The following table shows the test iterations for the RC builds. PTP is +2 which means that it's build is completed on the +2 day. Testing can begin using the Juno aggregation site (http://download.eclipse.org/releases/staging) on +3 and later. The EPP build is generally available at the end of the +3 day, but sometimes this is delayed a day.

	M7	RC1+1	RC1+2	RC1+3	RC1	RC2+1	RC2+2	RC2+3	RC2	RC3+1	RC3+2	RC3+3	RC3	RC4+1	RC4+2	RC4+3	RC4
Open MPI RM	##	Greg Rui (client and server)	Rui (client) ##		Greg ##		Jay (R) ##
MPICH2 RM	Hari	Greg ##			Greg ##		Jay (maybe) ##

Testers

Please add your name to this list, or remove the comment if you are still participating in 6.0

• Greg Watson
• Beth Tibbitts
• Dave Wootton
• Alan Humphrey
• Wyatt Spear (remove this if participating in 6.0)
• Jeff Overbey
• Jay Alameda (remove this if participating in 6.0)
• Galen Arnold
• Rui Liu (remove this if participating in 6.0)
• Jie Jiang (remove this if participating in 6.0)
• Max Billingsley III (remove this if participating in 6.0)
• Roland Schulz (remove this if participating in 6.0)
• John Eblen (remove this if participating in 6.0)
• Hari Krishnan

Test Matrix

The following test matrix shows who will be testing each component on the different supported architectures. Note that because PTP is client/server, you should list both the client and server architectures for each component being tested. For example, if you are testing the PE RM on a Mac OS X x86 client and an AIX backend, you should list both these architectures.

Questions

• do we need to test mac32?

When you find bugs, please open a bug report against the relevant component.

	Linux x86*	Linux x86_64	Linux PPC	Mac OS X x86**	Mac OS X x86_64	Windows	Windows x86_64	AIX***
Open MPI RM	##	Greg Rui (client and server)	Rui (client) ##		Greg ##		Jay (R) ##
MPICH2 RM	Hari	Greg ##			Greg ##		Jay (maybe) ##
PE/LL RM		Dave (client) ##	Dave (server) ##				Dave (client) ## Jay (R, client) ##	Dave ##
PE JAXB RM		Dave (client) ##	Dave (server) ##				Dave (client)	Dave ##
PBS RM	Hari			Al ##			Jay (R) ##
SLURM RM	Jie ##	Jie (Client and Server) ##				Jie ##
Grid Engine RMs	Jeff ##				Jeff ##	Jeff ##	Jeff ##
Debugger	Beth α ##	Greg ##			Greg ##		Jay (R) ##
PLDT - C/C++	Beth ##	Hari			Beth (R,L) ##	Beth α ##	Jay (R) ##
PLDT - Fortran	Jeff ##				Jeff ##	Jeff ##	Jeff ##
RDT + RSE		Galen
RDT + RT		Galen					Jay ##
RDT Sync		Greg ##			Greg ##		Jay ##
Photran	Jeff ##				Jeff ##	Jeff ##	Jeff ##
ETFw (Core)	Wyatt ##	Wyatt ##						Wyatt ##
ETFw (Feedback)	Beth α ##	Rui (L,R) ##	Rui (L,R) ##		Beth (R,L) ##	Beth α ##
ETFw (TAU)	Wyatt ##	Wyatt ##						Wyatt ##
ETFw (GEM)	Alan ##	Alan ##			Alan ##
ETFw (PPW)	Max ##	Max ##			Max ##
Error Parsers	Jeff ##				Jeff ##	Jeff ##	Jeff ##
Env Mgmt	Jeff ##	Galen			Jeff ##	Jeff ##	Jeff ##

• "*": Only the GTK 2 version of Eclipse will be tested. "**": Only the Cocoa version of Eclipse will be tested. "***": AIX testing is for the server side only.
• α Limited testing here
• (client) indicates that eclipse runs here; (server) indicates remote target runs here.
• (R) will test remote usage; (L) will test Local usage
  1. 1. (two hash marks): old (not updated to PTP 6.0 testing) - remove ## if you update this and/or confirm you are still testing this

---

Very Rough test outline

In case we don't get detailed test case info written, start with this:

1. Unzip or untar and launch parallel package
2. Make a sync project (originally sync: local then convert? From CVS then convert? start with empty project? start with source on remote target?)
   • MPI hello world or 'shallow' from PTP tutorial are good candidates if you don't have your own app - if you do, by all means test that.
3. Test editor (type code, do some code completion, find some MPI(or?) artifacts, to hyperlink navigation to header files and APIs in other files.
4. Build
5. Run - need test matrix of target configs to test
6. Parallel debugger

Each of us can most effectively test the components we were involved in. If you could write a basic test for your component, it might help the rest of it test it as well.

Packaging tests

1. are there update tests to perform now that Juno/6.0 is new? Do we need to be able to install anything over top ? Testing this NOW can alleviate problems at PTP 6.0.1 and SR1