Index: parameters.xml =================================================================== --- parameters.xml (revision 538452) +++ parameters.xml (working copy) @@ -1,4 +1,4 @@ - + - - - + Index: adaptor.xml =================================================================== --- adaptor.xml (revision 538452) +++ adaptor.xml (working copy) @@ -17,6 +17,8 @@ + + @@ -28,24 +30,46 @@ + + + + + + - + + + + + + + ${suite.name} run - + + + + + + + + + + + Index: readme.txt =================================================================== --- readme.txt (revision 538452) +++ readme.txt (working copy) @@ -7,21 +7,17 @@ the location specified by two optional parameters: 'download.address' and 'jar.name'. By default they are pointing to sourceforge site. If, by any change, you already have the Dacapo jar, and would like to skip the downloading -step, you can simply put tjhe jar to 'build/checkouts/dacapo' directory. +step, you can simply put the jar to 'build/checkouts/dacapo' directory. Another optional parameters are: 1) 'benchmarks' - specifying a set of benchmarks to run. By default the list - contains all available benchmarks. + contains all available benchmarks. + NOTE: to make chart benchmark working on linux, one should run X server + and provide proper DISPLAY variable in the environment prior to running, + the runner doesn't yet run X server by itself. 2) 'size' - Specifies the workload size, can be 'small', 'default' or 'large'. By default it's 'small' -3) 'always.mail' - when set to 'true', notifications are being sent after each - run; when 'false', only changes between passed/failed state are reported. The benchmark run is considered to be PASSED, if a number of PASSED workloads is equal to the number of workloads specified by 'benchmarks' parameter and to be FAILED otherwise. - -The notification contains finishing lines of each workload's log in case of -normal execution of the benchmark, and the whole log if the run was considered -FAILED. -