Trace number 216613

Some explanations

A solver is run under the control of another program named runsolver. runsolver is in charge of imposing the CPU time limit and the memory limit to the solver. It also monitors some information about the process. The trace of the execution of a solver is divided into four (or five) parts:
  1. SOLVER DATA
    This is the output of the solver (stdout and stderr).
    Note that some very long lines in this section may be truncated by your web browser ! In such a case, you may want to use the "Download as text" link to get the trace as a text file.

    When the --timestamp option is passed to the runsolver program, each line output by the solver is prepended with a timestamp which indicates at what time the line was output by the solver. Times are relative to the start of the program, given in seconds, and are wall clock time (not CPU time).

    As some 'v lines' may be very long (sometimes several megabytes), the 'v line' output by your solver may be split on several lines to help limit the size of the trace recorded in the database. In any case, the exact output of your solver is preserved in a trace file.
  2. VERIFIER DATA
    The output of the solver is piped to a verifier program which will search a value line "v " and, if found, will check that the given interpretation satisfies all constraints.
  3. CONVERSION SCRIPT DATA (Optionnal)
    When a conversion script is used, this section shows the messages that were output by the conversion script.
  4. WATCHER DATA
    This is the informations gathered by the runsolver program. It first prints the different limits. There's a first limit on CPU time set to X seconds (see the parameters in the trace). After this time has ellapsed, runsolver sends a SIGTERM and 2 seconds later a SIGKILL to the solver. For safety, there's also another limit set to X+30 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (see the parameters in the trace).
    Every ten seconds, the runsolver process fetches the content of /proc/loadavg, /proc/pid/stat and /proc/pid/statm (see man proc) and prints it as raw data. This is only recorded in case we need to investigate the behaviour of a solver. The memory used by the solver (vsize) is also given every ten seconds.
    When the solver exits, runsolver prints some informations such as status and time. CPU usage is the ratio CPU Time/Real Time.
  5. LAUNCHER DATA
    These informations are related to the script which will launch the solver. The most important informations are the command line given to the solver, the md5sum of the different files and the dump of the /proc/cpuinfo and /proc/meminfo which provides some useful information on the computer.

Solver answer on this benchmark

Solver NameAnswerCPU timeWall clock time
buggy_2_5 2007-01-08SAT 0.236963 0.248385

General information on the benchmark

Namerlfap/rlfapScensMod/
scen6-w1.xml
MD5SUMe4761551e00079c0c6c5437557356554
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.148977
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables200
Number of constraints319
Maximum constraint arity2
Maximum domain size44
Number of constraints which are defined in extension0
Number of constraints which are defined in intension319
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

SAT
268 30 338 100 16 254 16 254 16 254 652 414 254 16 100 338 254 16 16 254 694 456 30 268 680 442 16 254 16 254 708 470 254 16 526 764 652 414 736 498 16 254 442 680 254 16 30 268 16 254 16 254 16 254 16 254 254 16 352 114 254 16 254 16 16 254 44 282 254 16 16 254 16 254 254 16 30 268 512 750 428 666 268 30 16 254 666 428 470 708 268 30 30 268 30 268 30 268 268 30 414 652 498 736 722 484 254 16 414 652 16 254 526 764 512 750 30 268 268 30 100 338 484 722 526 764 268 30 428 666 86 324 512 750 428 666 666 428 268 30 428 666 30 268 268 30 708 470 16 254 16 254 526 764 16 254 694 456 652 414 86 324 254 16 778 540 324 86 30 268 764 526 694 456 666 428 254 16 16 254 254 16 428 666 428 666 268 30 268 30 268 30 470 708 268 30 680 442 30 268

Verifier Data (download as text)

OK

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node15/watcher-216613-1168701806 -o ROOT/results/node15/solver-216613-1168701806 -C 1800 -M 900 /tmp/evaluation/216613-1168701806/solver /tmp/evaluation/216613-1168701806/unknown 1800 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 921600 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 972800 KiB
Current StackSize limit: 10240 KiB

/proc/loadavg: 1.15 1.41 0.93 5/87 6278
/proc/meminfo: memFree=1544152/2055920 swapFree=4174172/4192956
[pid=6277] ppid=6275 vsize=18540 CPUtime=0
/proc/6277/stat : 6277 (runsolver) R 6275 6277 5445 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 218575662 18984960 279 18446744073709551615 4194304 4267372 548682069072 18446744073709551615 240472616231 0 0 4096 24578 0 0 0 17 1 0 0
/proc/6277/statm: 4635 279 244 17 0 2626 0

[startup+0.108456 s]
/proc/loadavg: 1.15 1.41 0.93 5/87 6278
/proc/meminfo: memFree=1544152/2055920 swapFree=4174172/4192956
[pid=6277] ppid=6275 vsize=5352 CPUtime=0.01
/proc/6277/stat : 6277 (solver) S 6275 6277 5445 0 -1 4194304 376 2232 0 0 0 0 0 1 20 0 1 0 218575662 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 240472613700 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/6277/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 5352

Child status: 0
Real time (s): 0.248385
CPU time (s): 0.236963
CPU user time (s): 0.097985
CPU system time (s): 0.138978
CPU usage (%): 95.4015
Max. virtual memory (cumulated for all children) (KiB): 5352

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.097985
system time used= 0.138978
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3767
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 78
involuntary context switches= 23

runsolver used 0.004999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node15 on Sat Jan 13 15:23:28 UTC 2007


IDJOB= 216613
IDBENCH= 5090
IDSOLVER= 83
FILE ID= node15/216613-1168701806

PBS_JOBID= 3547036

Free space on /tmp= 66552 MiB

SOLVER NAME= buggy_2_5 2007-01-08
BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapScensMod/scen6-w1.xml
COMMAND LINE= /tmp/evaluation/216613-1168701806/solver /tmp/evaluation/216613-1168701806/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node15/watcher-216613-1168701806 -o ROOT/results/node15/solver-216613-1168701806 -C 1800 -M 900  /tmp/evaluation/216613-1168701806/solver /tmp/evaluation/216613-1168701806/unknown 1800

META MD5SUM SOLVER= 6c84d9851726bfff2e2bc2bb5530c705
MD5SUM BENCH=  e4761551e00079c0c6c5437557356554

RANDOM SEED= 199887162

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.276
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5914.62
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.276
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1544568 kB
Buffers:         14316 kB
Cached:         175800 kB
SwapCached:       6200 kB
Active:         305512 kB
Inactive:       137576 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1544568 kB
SwapTotal:     4192956 kB
SwapFree:      4174172 kB
Dirty:           11252 kB
Writeback:           0 kB
Mapped:         263168 kB
Slab:            52392 kB
Committed_AS:  7182368 kB
PageTables:       2828 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66552 MiB



End job on node15 on Sat Jan 13 15:23:28 UTC 2007