Change problem size for ptrans performance runs

[ok'd by perf team]

ptrans has been timing out on chap04 for long time and is pretty close to
timing out on the other machines. This sets the problem size to be numrows=5733
for performance runs.

Previously the values were based on amount of memory on the system set to:
 chap04:    ~28,000 rows
 chap03:    ~8,000 rows
 brac-lnx:   5,733 rows

5,733 rows is ~.5GB of memory. Such an odd number was chosen because it was
previously what was running on bradc-lnx and it will be nice to keep the
historical data for it.

.graph and perkeys were updated to put the values into a new .dat file since
the old performance data will be off. I'll svn copy the data from bradc-lnx to
the new .dat file too.


git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23570 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove "final" timeout file: release/examples/benchmarks/hpcc/TIMEOUT

[ok'd by perf team]

With r23570 ptrans will no longer take over 30 minutes on chap04 so we can get
rid of this timeout. I tested some of the others in the directory and I'm
pretty sure they don't need the timeout either, but we'll see how testing goes.
This is the last of the timeouts that will be removed in the near term.

There are still 11 left overall. 7 of those are staying because they have
timeouts smaller than the default.The other 4 are:

  600  - release/examples/benchmarks/shootout/threadring.perftimeout
  400  - studies/shootout/thread-ring/lydia/TIMEOUT
   - Should be able to remove with switch to qthreads

  500  - release/examples/benchmarks/ssca2/SSCA_main.timeout
  500  - distributions/dm/t5a.timeout
   - These are because the cray compiler is really slow. Should be able to
     remove when our compilation times get better.


git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23571 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove chap02 crontab entry, it has been migrated to new system.

The chap02 test scripts were also updated to use the current working directory,
instead of ~/chapel, and remove the stdout/stderr pipes to log file. The new
system guarantees the current dir is a clean working copy of trunk, and it
captures stdout/stderr.

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23572 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove chap05 crontab entry, it has been migrated to new system.

The chap05 test scripts were also updated to use the current working directory,
instead of ~/chapel, and remove the stdout/stderr pipes to log file. The new
system guarantees the current dir is a clean working copy of trunk, and it
captures stdout/stderr.

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23573 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove chap06 crontab entry, it has been migrated to new system.

The chap06 test scripts were also updated to use the current working directory,
instead of ~/chapel, and remove the stdout/stderr pipes to log file. The new
system guarantees the current dir is a clean working copy of trunk, and it
captures stdout/stderr.

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23574 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove chap07 crontab entry, it has been migrated to new system.

The chap07 test scripts were also updated to use the current working directory,
instead of ~/chapel, and remove the stdout/stderr pipes to log file. The new
system guarantees the current dir is a clean working copy of trunk, and it
captures stdout/stderr.

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23575 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove chap08 crontab entry, it has been migrated to new system.

The chap08 test scripts were also updated to use the current working directory,
instead of ~/chapel, and remove the stdout/stderr pipes to log file. The new
system guarantees the current dir is a clean working copy of trunk, and it
captures stdout/stderr.

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23576 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove chap09 and chap10 crontab entries, they are empty.

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23577 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove chap11 crontab entry, it has been migrated to new system.

The chap11 test scripts were also updated to use the current working directory,
instead of ~/chapel, and remove the stdout/stderr pipes to log file. The new
system guarantees the current dir is a clean working copy of trunk, and it
captures stdout/stderr.

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23578 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove chap12 crontab entry, it has been migrated to new system.

The chap12 test scripts were also updated to use the current working directory,
instead of ~/chapel, and remove the stdout/stderr pipes to log file. The new
system guarantees the current dir is a clean working copy of trunk, and it
captures stdout/stderr.

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23579 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove chap13 crontab entry, it has been migrated to new system.

The chap13 test scripts were also updated to use the current working directory,
instead of ~/chapel, and remove the stdout/stderr pipes to log file. The new
system guarantees the current dir is a clean working copy of trunk, and it
captures stdout/stderr.

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23580 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove chap14 crontab entry, it has been migrated to new system.

The chap14 test scripts were also updated to use the current working directory,
instead of ~/chapel, and remove the stdout/stderr pipes to log file. The new
system guarantees the current dir is a clean working copy of trunk, and it
captures stdout/stderr.

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23581 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove mbp-tvandoren crontab and machine script.

They were empty.

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23582 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove mbp-kbrady crontab entry, it has been migrated to new system.

The mbp-kbrady test scripts were also updated to use the current working directory,
instead of ~/chapel, and remove the stdout/stderr pipes to log file. The new
system guarantees the current dir is a clean working copy of trunk, and it
captures stdout/stderr.

These tests have been disabled, and will continue to be disabled in the current
system. The configuration has moved, though, so they will be available whenever
mac testing stabilizes.

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23583 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove chpbld01 crontab entry, it has been migrated to new system.

The chpbld01 test scripts were also updated to use the current working directory,
instead of ~/chapel, and remove the stdout/stderr pipes to log file. The new
system guarantees the current dir is a clean working copy of trunk, and it
captures stdout/stderr.

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23584 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove chpbld02 crontab entry, it has been migrated to new system.

The chpbld02 test scripts were also updated to use the current working directory,
instead of ~/chapel, and remove the stdout/stderr pipes to log file. The new
system guarantees the current dir is a clean working copy of trunk, and it
captures stdout/stderr.

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23585 3a8e244f-b0f2-452b-bcba-4c88e055c3ca
Remove chap01 crontab entry, it has been migrated to new system.

The chap01 test scripts were also updated to use the current working directory,
instead of ~/chapel, and remove the stdout/stderr pipes to log file. The new
system guarantees the current dir is a clean working copy of trunk, and it
captures stdout/stderr.

This also removes the scripts to synchronize the crontabs across the testing
hosts. All of the jobs have been migrated to the new system. w00t!

git-svn-id: http://svn.code.sf.net/p/chapel/code/trunk@23586 3a8e244f-b0f2-452b-bcba-4c88e055c3ca