Trace number 2073771

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 0.3.2SAT 0.168973 0.181958

DiagnosticValue
ASSIGNMENTS42

General information on the benchmark

Namecsp/ukPuzzle/
normalized-crossword-m1-uk-puzzle12.xml
MD5SUMd34ed66d8e42e023238a8a6590560938
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.092985
Satisfiable
(Un)Satisfiability was proved
Number of variables52
Number of constraints166
Maximum constraint arity10
Maximum domain size26
Number of constraints which are defined in extension28
Number of constraints which are defined in intension138
Global constraints used (with number of constraints)

Solver Data 

0.00/0.02	c small-domain mode
0.07/0.18	c Seed is 1113416010
0.07/0.18	c Constructing HOME/instance-2073771-1247712238.xml  with 1706 constraints
0.07/0.18	c Solving 42 backtracks 2 restarts
0.07/0.18	s SATISFIABLE
0.07/0.18	c V0=19, V1=25, V2=0, V3=17, V4=22, V5=0, V6=18, V7=8, V8=14, V9=22, V10=0, V11=7, V12=14, V13=0, V14=1, V15=0, V16=4, V17=25, V18=8, V19=13, V20=18, V21=14, V22=2, V23=17, V24=4, V25=0, V26=20, V27=7, V28=20, V29=17, V30=20, V31=17, V32=4, V33=25, V34=1, V35=0, V36=11, V37=0, V38=4, V39=11, V40=8, V41=4, V42=24, V43=4, V44=3, V45=0, V46=3, V47=18, V48=1, V49=20, V50=25, V51=25, 
0.07/0.18	v 19 25 0 17 22 0 18 8 14 22 0 7 14 0 1 0 4 25 8 13 18 14 2 17 4 0 20 7 20 17 20 17 4 25 1 0 11 0 4 11 8 4 24 4 3 0 3 18 1 20 25 25 
0.07/0.18	d ASSIGNMENTS 42

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-2073771-1247712238/watcher-2073771-1247712238 -o /tmp/evaluation-result-2073771-1247712238/solver-2073771-1247712238 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 1113416010 HOME/instance-2073771-1247712238.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.00 2.01 2.00 4/81 11478
/proc/meminfo: memFree=1453384/2055920 swapFree=4192812/4192956
[pid=11478] ppid=11476 vsize=5356 CPUtime=0
/proc/11478/stat : 11478 (pcssolve) R 11476 11478 10722 0 -1 4194304 170 0 0 0 0 0 0 0 22 0 1 0 58286817 5484544 141 996147200 4194304 4889804 548682068800 18446744073709551615 271894115747 0 0 4096 0 0 0 0 17 1 0 0
/proc/11478/statm: 1339 141 114 169 0 50 0

[startup+0.098919 s]
/proc/loadavg: 2.00 2.01 2.00 4/81 11478
/proc/meminfo: memFree=1453384/2055920 swapFree=4192812/4192956
[pid=11478] ppid=11476 vsize=5532 CPUtime=0.07
/proc/11478/stat : 11478 (pcs.small) R 11476 11478 10722 0 -1 4194304 1023 1097 0 0 7 0 0 0 18 0 1 0 58286817 5664768 632 996147200 134512640 135095119 4294956304 18446744073709551615 4158924113 0 0 4096 0 0 0 0 17 1 0 0
/proc/11478/statm: 1383 632 388 142 0 337 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 5532

[startup+0.106543 s]
/proc/loadavg: 2.00 2.01 2.00 4/81 11478
/proc/meminfo: memFree=1453384/2055920 swapFree=4192812/4192956
[pid=11478] ppid=11476 vsize=5532 CPUtime=0.07
/proc/11478/stat : 11478 (pcs.small) R 11476 11478 10722 0 -1 4194304 1023 1097 0 0 7 0 0 0 18 0 1 0 58286817 5664768 632 996147200 134512640 135095119 4294956304 18446744073709551615 4159186624 0 0 4096 0 0 0 0 17 1 0 0
/proc/11478/statm: 1383 632 388 142 0 337 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 5532

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

Child status: 0
Real time (s): 0.181958
CPU time (s): 0.168973
CPU user time (s): 0.157975
CPU system time (s): 0.010998
CPU usage (%): 92.8637
Max. virtual memory (cumulated for all children) (KiB): 5532

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.157975
system time used= 0.010998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2155
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= 21
involuntary context switches= 14

runsolver used 0.001999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node60 at 2009-07-16 04:43:58
IDJOB=2073771
IDBENCH=56014
IDSOLVER=733
FILE ID=node60/2073771-1247712238
PBS_JOBID= 9521351
Free space on /tmp= 66428 MiB

SOLVER NAME= pcs 0.2
BENCH NAME= CPAI08/csp/ukPuzzle/normalized-crossword-m1-uk-puzzle12.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2073771-1247712238/watcher-2073771-1247712238 -o /tmp/evaluation-result-2073771-1247712238/solver-2073771-1247712238 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 1113416010 HOME/instance-2073771-1247712238.xml

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

MD5SUM BENCH= d34ed66d8e42e023238a8a6590560938
RANDOM SEED=1113416010

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


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1453864 kB
Buffers:         72132 kB
Cached:         364836 kB
SwapCached:          0 kB
Active:         146708 kB
Inactive:       371612 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1453864 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1956 kB
Writeback:           0 kB
Mapped:         101756 kB
Slab:            68652 kB
Committed_AS:   635548 kB
PageTables:       2072 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= 66428 MiB
End job on node60 at 2009-07-16 04:43:58