MITgcm_contrib/test_scripts/README.txt



The directories here contain shell scripts used to automate testing on
various systems.  The directory names approximately match the machine
or cluster "nicknames" for which they are intended.  For a description
of the machines and the latest testing output, please see:

  http://mitgcm.org/testing.html

July 28, 2005: Scripts currently used for testing on
   faulks, cg01, itrda (ACESgrid) and columbia
 have been moved to MITgcm/tools/example_scripts/

======================================================================

NOTE: mpack problems

The mpack utility is used by testreport to mime-encode and email the
testing results back to the mitgcm.org server.  There appears to be a
problem with the mpack utility on some 64-bit systems.  Notably,
emails sent from the following systems:

  SGI Altix
  AMD Opteron

will consistently result in errors ("MIME file corrupted in transit").
Perhaps the mpack utility is not "64-bit clean" and this is
interpreted by munpack as an error during transmission?

1	edhill	1.1
2
3			The directories here contain shell scripts used to automate testing on
4			various systems. The directory names approximately match the machine
5			or cluster "nicknames" for which they are intended. For a description
6			of the machines and the latest testing output, please see:
7
8			http://mitgcm.org/testing.html
9
10	jmc	1.2	July 28, 2005: Scripts currently used for testing on
11			faulks, cg01, itrda (ACESgrid) and columbia
12			have been moved to MITgcm/tools/example_scripts/
13	edhill	1.1
14			======================================================================
15
16			NOTE: mpack problems
17
18			The mpack utility is used by testreport to mime-encode and email the
19			testing results back to the mitgcm.org server. There appears to be a
20			problem with the mpack utility on some 64-bit systems. Notably,
21			emails sent from the following systems:
22
23			SGI Altix
24			AMD Opteron
25
26			will consistently result in errors ("MIME file corrupted in transit").
27			Perhaps the mpack utility is not "64-bit clean" and this is
28			interpreted by munpack as an error during transmission?
29