Trace number 201844

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
Mistral 2006-12-04SAT 1.3248 1.33849

General information on the benchmark

Namerlfap/rlfapScens/
scen3.xml
MD5SUMf0a2bd3f50a529cea49f9ef816c8636b
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 benchmark1.00984
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables400
Number of constraints2760
Maximum constraint arity2
Maximum domain size44
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2760
Global constraints used (with number of constraints)

Solver Data (download as text)

0.23	c 
0.23	c Parsing xml file
0.23	c 	domains...............    0
0.23	c 	variables.............    0
0.23	c 	predicates............    0
0.23	c 	constraints........... 0.17
0.23	c Allocating memory
0.23	c 
0.23	c time limit = -1
0.23	c heuristic = dom/wdeg
0.23	c restart policy = No restart
0.23	c 
0.23	c Solving
0.23	c
0.98	s SATISFIABLE
0.98	v 72 310 72 310 114 352 394 156 100 338 16 254 310 72 380 142 282 44 114 352 114 352 254 16 310 72 16 254 100 338 72 310 128 366 428 666 86 324 156 394 296 58 86 324 268 30 352 114 254 16 16 254 30 268 16 254 366 128 58 296 394 156 456 694 58 296 254 16 44 282 428 666 30 268 30 268 254 16 512 750 324 86 394 156 254 16 254 16 338 100 338 100 254 16 456 694 114 352 72 310 16 254 268 30 100 338 142 380 254 16 30 268 100 338 114 352 44 282 268 30 16 254 338 100 338 100 72 310 72 310 352 114 680 442 142 380 394 156 338 100 338 100 16 254 86 324 100 338 44 282 282 44 30 268 366 128 128 366 58 296 142 380 30 268 100 338 16 254 30 268 428 666 44 282 30 268 394 156 128 366 128 366 366 128 470 708 86 324 16 254 30 268 352 114 44 282 268 30 100 338 324 86 268 30 30 268 338 100 58 296 352 114 366 128 58 296 44 282 100 338 128 366 428 666 268 30 282 44 352 114 254 16 100 338 156 394 72 310 338 100 114 352 16 254 268 30 352 114 282 44 366 128 58 296 352 114 268 30 30 268 380 142 30 268 282 44 268 30 352 114 114 352 338 100 30 268 30 268 44 282 296 58 366 128 352 114 30 268 128 366 428 666 16 254 16 254 58 296 268 30 16 254 142 380 16 254 16 254 254 16 442 680 268 30 338 100 156 394 156 394 156 394 156 394 114 352 86 324 30 268 128 366 100 338 30 268 282 44 100 338 366 128 16 254 86 324 16 254 30 268 114 352 394 156 86 324 268 30 100 338 30 268 100 338 30 268 282 44 380 142 114 352 44 282 470 708 156 394 44 282 44 282 114 352 30 268 100 338 114 352 268 30 282 44 352 114 16 254 414 652
0.98	d          SAT         0 BTS      0.23 s

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/node17/watcher-201844-1168150013 -o ROOT/results/node17/solver-201844-1168150013 -C 1800 -M 900 /tmp/evaluation/201844-1168150013/mistral/bin/solver /tmp/evaluation/201844-1168150013/unknown.xml -v 1 

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: 2.13 2.07 2.04 5/94 9074
/proc/meminfo: memFree=1305576/2055920 swapFree=4192812/4192956
[pid=9073] ppid=9071 vsize=18540 CPUtime=0
/proc/9073/stat : 9073 (runsolver) R 9071 9073 8829 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 163396201 18984960 279 18446744073709551615 4194304 4267372 548682069040 18446744073709551615 245482712359 0 0 4096 24578 0 0 0 17 1 0 0
/proc/9073/statm: 4635 279 244 17 0 2626 0

[startup+0.108658 s]
/proc/loadavg: 2.13 2.07 2.04 5/94 9074
/proc/meminfo: memFree=1305576/2055920 swapFree=4192812/4192956
[pid=9073] ppid=9071 vsize=9952 CPUtime=0.09
/proc/9073/stat : 9073 (solver) R 9071 9073 8829 0 -1 4194304 1558 0 0 0 9 0 0 0 18 0 1 0 163396201 10190848 1526 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4158648190 0 0 4096 0 0 0 0 17 1 0 0
/proc/9073/statm: 2488 1526 706 92 0 832 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 9952

[startup+0.516702 s]
/proc/loadavg: 2.13 2.07 2.04 5/94 9074
/proc/meminfo: memFree=1305576/2055920 swapFree=4192812/4192956
[pid=9073] ppid=9071 vsize=56288 CPUtime=0.5
/proc/9073/stat : 9073 (solver) R 9071 9073 8829 0 -1 4194304 13150 0 0 0 43 7 0 0 21 0 1 0 163396201 57638912 13118 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 3292882 0 0 4096 0 0 0 0 17 1 0 0
/proc/9073/statm: 14072 13118 715 92 0 12416 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 56288

Child status: 0
Real time (s): 1.33849
CPU time (s): 1.3248
CPU user time (s): 1.16082
CPU system time (s): 0.163975
CPU usage (%): 98.9771
Max. virtual memory (cumulated for all children) (KiB): 91944

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.16082
system time used= 0.163975
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 22076
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= 13
involuntary context switches= 20

runsolver used 0.004999 s user time and 0.008998 s system time

The end

Launcher Data (download as text)

Begin job on node17 on Sun Jan  7 06:06:54 UTC 2007


IDJOB= 201844
IDBENCH= 3787
FILE ID= node17/201844-1168150013

PBS_JOBID= 3478198

Free space on /tmp= 66319 MiB

BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapScens/scen3.xml
COMMAND LINE= /tmp/evaluation/201844-1168150013/mistral/bin/solver /tmp/evaluation/201844-1168150013/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node17/watcher-201844-1168150013 -o ROOT/results/node17/solver-201844-1168150013 -C 1800 -M 900  /tmp/evaluation/201844-1168150013/mistral/bin/solver /tmp/evaluation/201844-1168150013/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  f0a2bd3f50a529cea49f9ef816c8636b

RANDOM SEED= 701570318

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.236
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.236
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:       1305992 kB
Buffers:         40104 kB
Cached:         194020 kB
SwapCached:          0 kB
Active:         560456 kB
Inactive:       106000 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1305992 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3508 kB
Writeback:           0 kB
Mapped:         460092 kB
Slab:            67388 kB
Committed_AS:  4983912 kB
PageTables:       3084 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= 66319 MiB



End job on node17 on Sun Jan  7 06:06:56 UTC 2007