Trace number 2074278

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
pcs-restart 0.3.2SAT 0.749885 0.754327

DiagnosticValue
ASSIGNMENTS682

General information on the benchmark

Namecsp/
chessboardColoration/normalized-cc-8-8-3.xml
MD5SUMe59c736386e4fa7e0c818bdb4dad0b97
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.06199
Satisfiable
(Un)Satisfiability was proved
Number of variables64
Number of constraints784
Maximum constraint arity4
Maximum domain size3
Number of constraints which are defined in extension0
Number of constraints which are defined in intension784
Global constraints used (with number of constraints)

Solver Data

0.00/0.01	c small-domain mode
0.00/0.01	c Seed is 1200520846
0.00/0.01	c Constructing HOME/instance-2074278-1247712324.xml  with 14224 constraints
0.05/0.09	c Solving 682 backtracks 7 restarts
0.68/0.75	s SATISFIABLE
0.68/0.75	c V0=1, V1=0, V2=0, V3=1, V4=2, V5=1, V6=2, V7=0, V8=1, V9=1, V10=2, V11=0, V12=1, V13=2, V14=0, V15=1, V16=2, V17=0, V18=2, V19=1, V20=2, V21=0, V22=0, V23=1, V24=0, V25=1, V26=0, V27=0, V28=2, V29=1, V30=1, V31=2, V32=1, V33=2, V34=2, V35=0, V36=0, V37=0, V38=2, V39=0, V40=1, V41=2, V42=1, V43=2, V44=2, V45=2, V46=1, V47=0, V48=2, V49=2, V50=0, V51=1, V52=1, V53=0, V54=1, V55=2, V56=0, V57=1, V58=1, V59=1, V60=0, V61=2, V62=2, V63=2, 
0.68/0.75	v 1 0 0 1 2 1 2 0 1 1 2 0 1 2 0 1 2 0 2 1 2 0 0 1 0 1 0 0 2 1 1 2 1 2 2 0 0 0 2 0 1 2 1 2 2 2 1 0 2 2 0 1 1 0 1 2 0 1 1 1 0 2 2 2 
0.68/0.75	d ASSIGNMENTS 682

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-2074278-1247712324/watcher-2074278-1247712324 -o /tmp/evaluation-result-2074278-1247712324/solver-2074278-1247712324 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 1200520846 HOME/instance-2074278-1247712324.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.10 2.05 2.06 4/72 13828
/proc/meminfo: memFree=1540496/2055920 swapFree=4192812/4192956
[pid=13828] ppid=13826 vsize=5356 CPUtime=0
/proc/13828/stat : 13828 (pcssolve) R 13826 13828 13570 0 -1 4194304 273 0 0 0 0 0 0 0 20 0 1 0 58296877 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 231882680991 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/13828/statm: 1339 241 200 169 0 50 0
[pid=13829] ppid=13828 vsize=5356 CPUtime=0
/proc/13829/stat : 13829 (pcssolve) R 13828 13828 13570 0 -1 4194368 0 0 0 0 0 0 0 0 20 0 1 0 58296877 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 231882680991 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/13829/statm: 1339 241 200 169 0 50 0

[startup+0.075202 s]
/proc/loadavg: 2.10 2.05 2.06 4/72 13828
/proc/meminfo: memFree=1540496/2055920 swapFree=4192812/4192956
[pid=13828] ppid=13826 vsize=6244 CPUtime=0.05
/proc/13828/stat : 13828 (pcs.small) R 13826 13828 13570 0 -1 4194304 1306 822 0 0 5 0 0 0 24 0 1 0 58296877 6393856 817 996147200 134512640 135095119 4294956304 18446744073709551615 134822891 0 0 4096 0 0 0 0 17 0 0 0
/proc/13828/statm: 1561 817 374 142 0 515 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 6244

[startup+0.101205 s]
/proc/loadavg: 2.10 2.05 2.06 4/72 13828
/proc/meminfo: memFree=1540496/2055920 swapFree=4192812/4192956
[pid=13828] ppid=13826 vsize=7036 CPUtime=0.08
/proc/13828/stat : 13828 (pcs.small) R 13826 13828 13570 0 -1 4194304 1561 822 0 0 8 0 0 0 24 0 1 0 58296877 7204864 1072 996147200 134512640 135095119 4294956304 18446744073709551615 134524952 0 0 4096 0 0 0 0 17 0 0 0
/proc/13828/statm: 1759 1072 386 142 0 713 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 7036

[startup+0.301232 s]
/proc/loadavg: 2.10 2.05 2.06 4/72 13828
/proc/meminfo: memFree=1540496/2055920 swapFree=4192812/4192956
[pid=13828] ppid=13826 vsize=7416 CPUtime=0.28
/proc/13828/stat : 13828 (pcs.small) R 13826 13828 13570 0 -1 4194304 1677 822 0 0 28 0 0 0 25 0 1 0 58296877 7593984 1187 996147200 134512640 135095119 4294956304 18446744073709551615 134642970 0 0 4096 0 0 0 0 17 0 0 0
/proc/13828/statm: 1854 1187 387 142 0 808 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 7416

[startup+0.701278 s]
/proc/loadavg: 2.10 2.05 2.06 4/72 13828
/proc/meminfo: memFree=1540496/2055920 swapFree=4192812/4192956
[pid=13828] ppid=13826 vsize=7416 CPUtime=0.68
/proc/13828/stat : 13828 (pcs.small) R 13826 13828 13570 0 -1 4194304 1682 822 0 0 68 0 0 0 25 0 1 0 58296877 7593984 1192 996147200 134512640 135095119 4294956304 18446744073709551615 134882992 0 0 4096 0 0 0 0 17 0 0 0
/proc/13828/statm: 1854 1192 387 142 0 808 0
Current children cumulated CPU time (s) 0.68
Current children cumulated vsize (KiB) 7416

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

Child status: 0
Real time (s): 0.754327
CPU time (s): 0.749885
CPU user time (s): 0.736887
CPU system time (s): 0.012998
CPU usage (%): 99.4111
Max. virtual memory (cumulated for all children) (KiB): 7416

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.736887
system time used= 0.012998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2508
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= 18
involuntary context switches= 22

runsolver used 0.001999 second user time and 0.004999 second system time

The end

Launcher Data

Begin job on node75 at 2009-07-16 04:45:24
IDJOB=2074278
IDBENCH=56083
IDSOLVER=734
FILE ID=node75/2074278-1247712324
PBS_JOBID= 9521471
Free space on /tmp= 66256 MiB

SOLVER NAME= pcs-restart 0.2.restart
BENCH NAME= CPAI08/csp/chessboardColoration/normalized-cc-8-8-3.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2074278-1247712324/watcher-2074278-1247712324 -o /tmp/evaluation-result-2074278-1247712324/solver-2074278-1247712324 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 1200520846 HOME/instance-2074278-1247712324.xml

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

MD5SUM BENCH= e59c736386e4fa7e0c818bdb4dad0b97
RANDOM SEED=1200520846

node75.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.232
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.232
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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1540912 kB
Buffers:         70660 kB
Cached:         336320 kB
SwapCached:          0 kB
Active:         112992 kB
Inactive:       314664 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1540912 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1844 kB
Writeback:           0 kB
Mapped:          32128 kB
Slab:            72620 kB
Committed_AS:   516760 kB
PageTables:       1760 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= 66252 MiB
End job on node75 at 2009-07-16 04:45:25