Trace number 2076829

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.284955 0.292155

DiagnosticValue
ASSIGNMENTS48

General information on the benchmark

Namecsp/ogdHerald/
normalized-crossword-m1-ogd-05-01.xml
MD5SUMe1b490498f3ff471ba21761182e48b82
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.05799
Satisfiable
(Un)Satisfiability was proved
Number of variables25
Number of constraints55
Maximum constraint arity10
Maximum domain size26
Number of constraints which are defined in extension10
Number of constraints which are defined in intension45
Global constraints used (with number of constraints)

Solver Data 

0.00/0.01	c small-domain mode
0.17/0.21	c Seed is 1555024731
0.17/0.21	c Constructing HOME/instance-2076829-1247714340.xml  with 757 constraints
0.17/0.21	c Solving 48 backtracks 2 restarts
0.17/0.29	s SATISFIABLE
0.17/0.29	c V0=12, V1=0, V2=19, V3=0, V4=18, V5=0, V6=21, V7=0, V8=13, V9=19, V10=25, V11=0, V12=12, V13=8, V14=0, V15=0, V16=17, V17=8, V18=4, V19=13, V20=8, V21=18, V22=0, V23=17, V24=3, 
0.17/0.29	v 12 0 19 0 18 0 21 0 13 19 25 0 12 8 0 0 17 8 4 13 8 18 0 17 3 
0.17/0.29	d ASSIGNMENTS 48

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-2076829-1247714340/watcher-2076829-1247714340 -o /tmp/evaluation-result-2076829-1247714340/solver-2076829-1247714340 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 1555024731 HOME/instance-2076829-1247714340.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: 1.93 2.00 1.99 4/82 9936
/proc/meminfo: memFree=763184/2055920 swapFree=4192812/4192956
[pid=9936] ppid=9934 vsize=5356 CPUtime=0
/proc/9936/stat : 9936 (pcssolve) R 9934 9936 9017 0 -1 4194304 290 0 0 0 0 0 0 0 21 0 1 0 58497304 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 251255122591 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/9936/statm: 1339 241 200 169 0 50 0
[pid=9937] ppid=9936 vsize=0 CPUtime=0
/proc/9937/stat : 9937 (fgrep) Z 9936 9936 9017 0 -1 4194316 199 0 0 0 0 0 0 0 22 0 1 0 58497305 0 0 996147200 0 0 0 0 0 0 0 4096 0 18446744071563351923 0 0 17 1 0 0
/proc/9937/statm: 0 0 0 0 0 0 0

[startup+0.11157 s]
/proc/loadavg: 1.93 2.00 1.99 4/82 9936
/proc/meminfo: memFree=763184/2055920 swapFree=4192812/4192956
[pid=9936] ppid=9934 vsize=4868 CPUtime=0.08
/proc/9936/stat : 9936 (pcs.small) R 9934 9936 9017 0 -1 4194304 955 954 0 0 8 0 0 0 18 0 1 0 58497304 4984832 563 996147200 134512640 135095119 4294956304 18446744073709551615 134918185 0 0 4096 0 0 0 0 17 1 0 0
/proc/9936/statm: 1217 563 400 142 0 171 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 4868

[startup+0.202576 s]
/proc/loadavg: 1.93 2.00 1.99 4/82 9936
/proc/meminfo: memFree=763184/2055920 swapFree=4192812/4192956
[pid=9936] ppid=9934 vsize=4868 CPUtime=0.17
/proc/9936/stat : 9936 (pcs.small) R 9934 9936 9017 0 -1 4194304 955 954 0 0 17 0 0 0 18 0 1 0 58497304 4984832 563 996147200 134512640 135095119 4294956304 18446744073709551615 134918161 0 0 4096 0 0 0 0 17 1 0 0
/proc/9936/statm: 1217 563 400 142 0 171 0
Current children cumulated CPU time (s) 0.17
Current children cumulated vsize (KiB) 4868

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

Child status: 0
Real time (s): 0.292155
CPU time (s): 0.284955
CPU user time (s): 0.269958
CPU system time (s): 0.014997
CPU usage (%): 97.5356
Max. virtual memory (cumulated for all children) (KiB): 4868

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.269958
system time used= 0.014997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1911
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= 22

runsolver used 0.002999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node64 at 2009-07-16 05:19:00
IDJOB=2076829
IDBENCH=56506
IDSOLVER=733
FILE ID=node64/2076829-1247714340
PBS_JOBID= 9521362
Free space on /tmp= 66332 MiB

SOLVER NAME= pcs 0.2
BENCH NAME= CPAI08/csp/ogdHerald/normalized-crossword-m1-ogd-05-01.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2076829-1247714340/watcher-2076829-1247714340 -o /tmp/evaluation-result-2076829-1247714340/solver-2076829-1247714340 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 1555024731 HOME/instance-2076829-1247714340.xml

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

MD5SUM BENCH= e1b490498f3ff471ba21761182e48b82
RANDOM SEED=1555024731

node64.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.220
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.220
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:        763664 kB
Buffers:         82520 kB
Cached:         352544 kB
SwapCached:          0 kB
Active:         835996 kB
Inactive:       367384 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        763664 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2092 kB
Writeback:           0 kB
Mapped:         788720 kB
Slab:            72300 kB
Committed_AS:  1262564 kB
PageTables:       3296 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= 66328 MiB
End job on node64 at 2009-07-16 05:19:00