Trace number 2073761

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.469928 0.482275

DiagnosticValue
ASSIGNMENTS22

General information on the benchmark

Namecsp/ukPuzzle/
normalized-crossword-m1-uk-puzzle09.xml
MD5SUM33255ab1db6eee138a2f933ce51e63f1
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.153975
Satisfiable
(Un)Satisfiability was proved
Number of variables35
Number of constraints55
Maximum constraint arity14
Maximum domain size26
Number of constraints which are defined in extension17
Number of constraints which are defined in intension38
Global constraints used (with number of constraints)

Solver Data 

0.00/0.02	c small-domain mode
0.00/0.06	c Seed is 300729980
0.00/0.06	c Constructing HOME/instance-2073761-1247712233.xml  with 434 constraints
0.18/0.22	c Solving 22 backtracks 1 restarts
0.36/0.48	s SATISFIABLE
0.36/0.48	c V0=6, V1=4, V2=4, V3=21, V4=14, V5=11, V6=21, V7=14, V8=15, V9=14, V10=3, V11=4, V12=20, V13=10, V14=18, V15=2, V16=7, V17=4, V18=17, V19=25, V20=14, V21=19, V22=0, V23=14, V24=19, V25=14, V26=15, V27=1, V28=14, V29=25, V30=14, V31=18, V32=3, V33=14, V34=17, 
0.36/0.48	v 6 4 4 21 14 11 21 14 15 14 3 4 20 10 18 2 7 4 17 25 14 19 0 14 19 14 15 1 14 25 14 18 3 14 17 
0.36/0.48	d ASSIGNMENTS 22

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-2073761-1247712233/watcher-2073761-1247712233 -o /tmp/evaluation-result-2073761-1247712233/solver-2073761-1247712233 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 300729980 HOME/instance-2073761-1247712233.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.00 2.00 4/72 16069
/proc/meminfo: memFree=1552568/2055920 swapFree=4192812/4192956
[pid=16069] ppid=16067 vsize=18576 CPUtime=0
/proc/16069/stat : 16069 (runsolver) R 16067 16069 15829 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 58286793 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 246406507815 0 0 4096 24578 0 0 0 17 1 0 0
/proc/16069/statm: 4644 284 249 26 0 2626 0

[startup+0.220654 s]
/proc/loadavg: 2.00 2.00 2.00 4/72 16069
/proc/meminfo: memFree=1552568/2055920 swapFree=4192812/4192956
[pid=16069] ppid=16067 vsize=7248 CPUtime=0.18
/proc/16069/stat : 16069 (pcs.small) R 16067 16069 15829 0 -1 4194304 1490 1532 0 0 18 0 0 0 19 0 1 0 58286793 7421952 939 996147200 134512640 135095119 4294956304 18446744073709551615 10814768 0 0 4096 0 0 0 0 17 1 0 0
/proc/16069/statm: 1812 939 388 142 0 766 0
Current children cumulated CPU time (s) 0.18
Current children cumulated vsize (KiB) 7248

[startup+0.302655 s]
/proc/loadavg: 2.00 2.00 2.00 4/72 16069
/proc/meminfo: memFree=1552568/2055920 swapFree=4192812/4192956
[pid=16069] ppid=16067 vsize=6444 CPUtime=0.27
/proc/16069/stat : 16069 (pcs.small) R 16067 16069 15829 0 -1 4194304 1503 1532 0 0 27 0 0 0 19 0 1 0 58286793 6598656 949 996147200 134512640 135095119 4294956304 18446744073709551615 134918194 0 0 4096 0 0 0 0 17 1 0 0
/proc/16069/statm: 1611 949 400 142 0 565 0
Current children cumulated CPU time (s) 0.27
Current children cumulated vsize (KiB) 6444

[startup+0.402666 s]
/proc/loadavg: 2.00 2.00 2.00 4/72 16069
/proc/meminfo: memFree=1552568/2055920 swapFree=4192812/4192956
[pid=16069] ppid=16067 vsize=6444 CPUtime=0.36
/proc/16069/stat : 16069 (pcs.small) R 16067 16069 15829 0 -1 4194304 1503 1532 0 0 36 0 0 0 20 0 1 0 58286793 6598656 949 996147200 134512640 135095119 4294956304 18446744073709551615 134918253 0 0 4096 0 0 0 0 17 1 0 0
/proc/16069/statm: 1611 949 400 142 0 565 0
Current children cumulated CPU time (s) 0.36
Current children cumulated vsize (KiB) 6444

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

[startup+0.402666 s]
/proc/loadavg: 2.00 2.00 2.00 4/72 16069
/proc/meminfo: memFree=1552568/2055920 swapFree=4192812/4192956
[pid=16069] ppid=16067 vsize=6444 CPUtime=0.36
/proc/16069/stat : 16069 (pcs.small) R 16067 16069 15829 0 -1 4194304 1503 1532 0 0 36 0 0 0 20 0 1 0 58286793 6598656 949 996147200 134512640 135095119 4294956304 18446744073709551615 134918253 0 0 4096 0 0 0 0 17 1 0 0
/proc/16069/statm: 1611 949 400 142 0 565 0
Current children cumulated CPU time (s) 0.36
Current children cumulated vsize (KiB) 6444

Child status: 0
Real time (s): 0.482275
CPU time (s): 0.469928
CPU user time (s): 0.450931
CPU system time (s): 0.018997
CPU usage (%): 97.4398
Max. virtual memory (cumulated for all children) (KiB): 7248

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

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node61 at 2009-07-16 04:43:53
IDJOB=2073761
IDBENCH=56013
IDSOLVER=734
FILE ID=node61/2073761-1247712233
PBS_JOBID= 9521385
Free space on /tmp= 66380 MiB

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

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

MD5SUM BENCH= 33255ab1db6eee138a2f933ce51e63f1
RANDOM SEED=300729980

node61.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.229
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.229
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:       1553048 kB
Buffers:        100672 kB
Cached:         282032 kB
SwapCached:          0 kB
Active:          92032 kB
Inactive:       310760 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1553048 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2492 kB
Writeback:           0 kB
Mapped:          31544 kB
Slab:            85596 kB
Committed_AS:   538864 kB
PageTables:       1700 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264884 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66376 MiB
End job on node61 at 2009-07-16 04:43:54