Trace number 2063747

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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 1.545SAT 0.108982 0.116116

DiagnosticValue
ASSIGNMENTS351
CHECKS64824
NODES351

General information on the benchmark

Namecsp/radar-9-28-4-2/
normalized-radar-9-28-4-2-17.xml
MD5SUM19b87120d9b5d562811d3a9be967d4f1
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.108982
Satisfiable
(Un)Satisfiability was proved
Number of variables168
Number of constraints81
Maximum constraint arity22
Maximum domain size5
Number of constraints which are defined in extension0
Number of constraints which are defined in intension81
Global constraints used (with number of constraints)

Solver Data 

0.08/0.11	c mistral version 1.545
0.08/0.11	s SATISFIABLE
0.08/0.11	v 0 0 1 1 0 0 0 4 2 3 4 0 1 0 3 2 0 0 0 4 0 4 1 4 4 4 2 2 0 0 1 4 1 0 4 3 2 2 0 1 0 0 2 4 0 0 1 0 2 0 0 1 1 1 3 0 0 2 4 4 0 4 3 1 2 0 4 1 0 4 0 4 0 3 2 0 0 2 0 0 0 0 0 4 0 0 1 1 1 0 1 0 2 0 0 2 3 0 4 1 0 0 0 0 4 0 2 2 0 2 2 4 4 0 0 2 4 2 0 2 2 0 3 0 1 0 4 0 0 0 0 1 0 0 4 0 0 0 1 4 4 0 0 4 1 0 0 0 0 3 4 1 0 0 0 0 1 3 0 0 4 4 4 1 0 0 2 0
0.08/0.11	d CHECKS 64824
0.08/0.11	d ASSIGNMENTS 351
0.08/0.11	d NODES 351 BACKTRACKS 232 FAILURES 232 RUNTIME 0.05 TOTALTIME 0.09 NODES/s 7020 CHECKS/s 1.29648e+06

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2063747-1247332802/watcher-2063747-1247332802 -o /tmp/evaluation-result-2063747-1247332802/solver-2063747-1247332802 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2063747-1247332802.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2000 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


[startup+0 s]
/proc/loadavg: 2.13 2.16 2.08 4/74 15108
/proc/meminfo: memFree=1799568/2055920 swapFree=4192812/4192956
[pid=15108] ppid=15106 vsize=18576 CPUtime=0
/proc/15108/stat : 15108 (runsolver) R 15106 15108 11978 0 -1 4194368 15 0 0 0 0 0 0 0 19 0 1 0 20346821 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 217871609127 0 2147483391 4096 24578 0 0 0 17 1 0 0
/proc/15108/statm: 4644 284 249 26 0 2626 0

[startup+0.0927759 s]
/proc/loadavg: 2.13 2.16 2.08 4/74 15108
/proc/meminfo: memFree=1799568/2055920 swapFree=4192812/4192956
[pid=15108] ppid=15106 vsize=7608 CPUtime=0.07
/proc/15108/stat : 15108 (ld-linux.so.2) R 15106 15108 11978 0 -1 4194304 1159 0 0 0 7 0 0 0 18 0 1 0 20346821 7790592 1138 996147200 1448431616 1448550632 4294956208 18446744073709551615 134839916 0 0 4096 0 0 0 0 17 1 0 0
/proc/15108/statm: 1902 1138 425 29 0 717 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 7608

[startup+0.102773 s]
/proc/loadavg: 2.13 2.16 2.08 4/74 15108
/proc/meminfo: memFree=1799568/2055920 swapFree=4192812/4192956
[pid=15108] ppid=15106 vsize=7608 CPUtime=0.08
/proc/15108/stat : 15108 (ld-linux.so.2) R 15106 15108 11978 0 -1 4194304 1163 0 0 0 8 0 0 0 18 0 1 0 20346821 7790592 1142 996147200 1448431616 1448550632 4294956208 18446744073709551615 135259360 0 0 4096 0 0 0 0 17 1 0 0
/proc/15108/statm: 1902 1142 425 29 0 717 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 7608

Solver just ended. Dumping a history of the last processes samples

Child status: 0
Real time (s): 0.116116
CPU time (s): 0.108982
CPU user time (s): 0.099984
CPU system time (s): 0.008998
CPU usage (%): 93.8562
Max. virtual memory (cumulated for all children) (KiB): 7608

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.099984
system time used= 0.008998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1215
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= 24
involuntary context switches= 3

runsolver used 0.001999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node28 at 2009-07-11 19:20:02
IDJOB=2063747
IDBENCH=54078
IDSOLVER=769
FILE ID=node28/2063747-1247332802
PBS_JOBID= 9506571
Free space on /tmp= 66092 MiB

SOLVER NAME= Mistral 1.545
BENCH NAME= CPAI08/csp/radar-9-28-4-2/normalized-radar-9-28-4-2-17.xml
COMMAND LINE= /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2063747-1247332802/watcher-2063747-1247332802 -o /tmp/evaluation-result-2063747-1247332802/solver-2063747-1247332802 -C 1800 -W 2000 -M 900  /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2063747-1247332802.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 19b87120d9b5d562811d3a9be967d4f1
RANDOM SEED=1223071244

node28.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/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.230
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.230
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:       1800048 kB
Buffers:         10424 kB
Cached:          69816 kB
SwapCached:          0 kB
Active:         183748 kB
Inactive:        22748 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1800048 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1240 kB
Writeback:           0 kB
Mapped:         133468 kB
Slab:            34204 kB
Committed_AS:   317628 kB
PageTables:       2116 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264960 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66088 MiB
End job on node28 at 2009-07-11 19:20:02