Log of /MITgcm_contrib/test_scripts/sx8/mitgcmtestreport_split
Parent Directory
|
Revision Log
|
Revision Graph
Revision
1.7
Thu Jun 2 12:51:57 2016 UTC
(9 years, 1 month ago)
by
mlosch
Branch:
MAIN
CVS Tags:
HEAD
Changes since
1.6: +1 -1 lines
FILE REMOVED
- add scripts to run testreport on ollie
- remove directories that belong to machines that are long gone
Revision
1.6 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Mon Mar 2 14:21:31 2015 UTC
(10 years, 4 months ago)
by
mlosch
Branch:
MAIN
Changes since
1.5: +8 -6 lines
Diff to
previous 1.5
add more module command
fix bash syntax carried over from csh script: replace $status by $?
Revision
1.5 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Mon Mar 2 09:13:18 2015 UTC
(10 years, 4 months ago)
by
mlosch
Branch:
MAIN
Changes since
1.4: +4 -1 lines
Diff to
previous 1.4
add definition of module command (bash function), so that we can
actually have compilers in this script
Revision
1.1 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Thu Feb 26 17:50:43 2015 UTC
(10 years, 4 months ago)
by
mlosch
Branch:
MAIN
add new script for running testreport on sx8.awi.de
- split the testreport into 3 steps:
1/ compiling on head node (tx7.awi.de), with -norun option
2/ running on compute node (using PBS qsub), with -runonly option
3/ evaluating result on head node with -runonly option
Notes:
- step 2 leads to many error messages, because the OS on the compute
nodes does not have the appropriate shell tools, modifying the
-runonly option to skip the evalution step would be nice but not
necessary; you'll just have to live with the error messages
- step 3 assumes that all experiments have been run successfully, i.e.
that the output files are up-to-date.
if not, testreport will try to run the sx8-code on the tx7 frontend
which will fail inevitably and produce more errors, maybe we can
have a flag that skips everything but the evaluation step to avoid this
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
select a symbolic revision name using the selection box, or choose
'Use Text Field' and enter a numeric revision.