Hi Aamer,
The instructions for running the stand-alone instance of Cloud9 is mostly to
verify that Cloud9 will be correctly executed in that machine. The scripts for
the cluster mode are the ones that are going to manage these instances of
c9-worker. By using the scripts we are able to distribute the work within a
single node or across multiple nodes. What you need to do appears in the step
number 5:
"To generate an experiment schedule we will create a .exp file in the
infra/exp/ directory (e.g., coreutils.exp or example.exp). Inside, each line in
the file is for one iteration of the experiment - and all the items in one line
are executed in parallel. The items are space-separated, and have the format
"[testing target id] [# workers] {[host] [# cores]}*" that describes the number
of workers allocated for a testing target, and their allocation per physical
host. Notice that the [testing target id] refers to entry specified in the
.cmdlines file."
For example, if we want to test the printf binary using one worker, the .exp
file will look like this:
printf 1 server1 1
If we want to test prinft with 6 instances in the same node:
printf 6 server1 6
On the other hand, if we want to distribute across two nodes:
printf 6 server1 3 server2 3
Do not hesitate to ask if you have any problem with any step.
Regards,
Javier
________________________________________
From: Jaleel, Aamer [[email protected]]
Sent: 10 February 2012 20:59
To: Adileh Almutaz; Picorel Javier
Cc: [email protected]
Subject: RE: Cloud9 code coverage
I was trying to run this on a single node. And I followed the instructions for
the single node. Will the run-experiment.py approach work for a single-node?
-----Original Message-----
From: Adileh Almutaz [mailto:[email protected]]
Sent: Friday, February 10, 2012 2:00 PM
To: Jaleel, Aamer
Cc: [email protected]
Subject: FW: Cloud9 code coverage
Hi Aamer,
This is Javier's reply to your question.
Regards,
Mutaz
________________________________________
From: Picorel Javier [ ]
Sent: Friday, February 10, 2012 7:44 PM
To: [email protected]
Subject: [cloudsuite] Cloud9 code coverage
That output says that Cloud9 is running but it's not computing the code
coverage. Be sure that the example.coverable file is inside the
cloud9/infra/coverable folder as step 4 suggests:
"4- Setup the file that describes the source files accounted for when computing
code coverage in the infra/coverable/ directory (e.g., example.coverable). You
may use the provided coreutils.coverable file for running the Coreutils."
It should be there by default. Afterwards when running the experiment by
following step 5:
"./run-experiment.py -t [time in seconds] --strategy random-path,cov-opt epfl
coreutils coreutils-12 coreutils coreutils"
The last argument has to have the same name as the file inside the coverable
folder before the dot. For instance if this file inside cloud9/infra/coverable
has the name
example.coveable I should run the command like this "./run-experiment.py ...
example".
Regards,
Javier
-----Original Message-----
Who is in charge of Cloud9? The online tool suggests running till code
coverage of 80%. I don't seem to see much of that...
What should the output be like? I get the following from the beginning:
[00530.487] Worker< >: Debug: Code coverage is 0/0 (local) and 0/0 (global)...
missing hexadecimal number in escape
[00536.187] Worker< >: Debug: Code coverage is 0/0 (local) and 0/0 (global)...
[00539.215] Worker< >: Debug: Code coverage is 0/0 (local) and 0/0 (global)...
[00542.547] Worker< >: Debug: Code coverage is 0/0 (local) and 0/0 (global)...
[00548.451] Worker< >: Debug: Code coverage is 0/0 (local) and 0/0 (global)...
warning: ignoring excess arguments, starting with `\'
[00559.085] Worker< >: Debug: Code coverage is 0/0 (local) and 0/0 (global)...
KLEE: WARNING: calling external: newlocale(8127, 140717362122656, 0)
KLEE: WARNING: calling external: strtold_l(140717362121280, 140717362394336,
140717645837280)
KLEE: WARNING: calling external: freelocale(140717645837280)
warning: ignoring excess arguments, starting with `\\r'
[00568.760] Worker< >: Debug: Code coverage is 0/0 (local) and 0/0 (global)...
[00573.466] Worker< >: Debug: Code coverage is 0/0 (local) and 0/0 (global)...
[00576.613] Worker< >: Debug: Code coverage is 0/0 (local) and 0/0 (global)...
