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