[pygr-notify] [pygr commit] r185 - Edited wiki page through web user interface.
codesite-noreply at google.com
codesite-noreply at google.com
Wed Apr 15 17:06:32 PDT 2009
Author: marecki
Date: Wed Apr 15 16:33:23 2009
New Revision: 185
Modified:
wiki/MegatestSetup.wiki
Log:
Edited wiki page through web user interface.
Modified: wiki/MegatestSetup.wiki
==============================================================================
--- wiki/MegatestSetup.wiki (original)
+++ wiki/MegatestSetup.wiki Wed Apr 15 16:33:23 2009
@@ -13,15 +13,15 @@
You will need the following to be able to run megatests:
- # A computer system you don't mind placing under heavy load, particularly
I/O-wise, on a regular basis. Instructions on this page assume a box
running Linux, which so far is the only operating system we have tried
running megatests on; Unix(-based) systems should also be supported out of
the box, Windows should in principle work but will need either Cygwin or a
custom runner script. _Please let us know about the outcome of attempts of
running on non-Linux boxes!_
+ * A computer system you don't mind placing under heavy load, particularly
I/O-wise, on a regular basis. Instructions on this page assume a box
running Linux, which so far is the only operating system we have tried
running megatests on; Unix(-based) systems should also be supported out of
the box, Windows should in principle work but will need either Cygwin or a
custom runner script. _Please let us know about the outcome of attempts of
running on non-Linux boxes!_
- # A MySQL server with write access to. You'll probably want to use a
local, dedicated instance to minimise security implications of the above as
well as possible influence of database-access delays on test results;
+ * A MySQL server with write access to. You'll probably want to use a
local, dedicated instance to minimise security implications of the above as
well as possible influence of database-access delays on test results;
- # A (relative) lot of disc space. At present megatests take up about 200
GB when idle and up to 600 GB while running;
+ * A (relative) lot of disc space. At present megatests take up about 200
GB when idle and up to 600 GB while running;
- # Everything needed by Pygr itself;
+ * Everything needed by Pygr itself;
- # (optional) A local pygr.Data XML-RPC server, so that the data-download
test is not affected by the quality of your connection to the UCLA one.
+ * (optional) A local pygr.Data XML-RPC server, so that the data-download
test is not affected by the quality of your connection to the UCLA one.
XXX
More information about the pygr-notify
mailing list