Trace number 2076961

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.136978 0.149801

DiagnosticValue
ASSIGNMENTS28

General information on the benchmark

Namecsp/ogdHerald/
normalized-crossword-m1-ogd-05-07.xml
MD5SUM1f2b24ca3568cf58ecc49f3227589cf3
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.051991
Satisfiable
(Un)Satisfiability was proved
Number of variables21
Number of constraints23
Maximum constraint arity10
Maximum domain size26
Number of constraints which are defined in extension10
Number of constraints which are defined in intension13
Global constraints used (with number of constraints)

Solver Data 

0.00/0.02	c small-domain mode
0.00/0.02	c Seed is 665119128
0.00/0.02	c Constructing HOME/instance-2076961-1247714494.xml  with 215 constraints
0.00/0.06	c Solving 28 backtracks 1 restarts
0.07/0.14	s SATISFIABLE
0.07/0.14	c V0=4, V1=17, V2=18, V3=4, V4=11, V5=14, V6=19, V7=14, V8=1, V9=20, V10=1, V11=14, V12=13, V13=19, V14=17, V15=14, V16=20, V17=15, V18=20, V19=19, V20=19, 
0.07/0.14	v 4 17 18 4 11 14 19 14 1 20 1 14 13 19 17 14 20 15 20 19 19 
0.07/0.14	d ASSIGNMENTS 28

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-2076961-1247714494/watcher-2076961-1247714494 -o /tmp/evaluation-result-2076961-1247714494/solver-2076961-1247714494 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 665119128 HOME/instance-2076961-1247714494.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.06 2.03 4/82 17862
/proc/meminfo: memFree=1634888/2055920 swapFree=4192812/4192956
[pid=17862] ppid=17860 vsize=18576 CPUtime=0
/proc/17862/stat : 17862 (runsolver) R 17860 17862 17322 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 58514407 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 251279240487 0 0 4096 24578 0 0 0 17 1 0 0
/proc/17862/statm: 4644 284 249 26 0 2626 0

[startup+0.0129821 s]
/proc/loadavg: 2.00 2.06 2.03 4/82 17862
/proc/meminfo: memFree=1634888/2055920 swapFree=4192812/4192956
[pid=17862] ppid=17860 vsize=5356 CPUtime=0
/proc/17862/stat : 17862 (pcssolve) R 17860 17862 17322 0 -1 4194304 305 0 0 0 0 0 0 0 21 0 1 0 58514407 5484544 242 996147200 4194304 4889804 548682068800 18446744073709551615 251279237956 0 65536 4100 65538 0 0 0 17 0 0 0
/proc/17862/statm: 1339 242 201 169 0 50 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5356

[startup+0.102512 s]
/proc/loadavg: 2.00 2.06 2.03 4/82 17862
/proc/meminfo: memFree=1634888/2055920 swapFree=4192812/4192956
[pid=17862] ppid=17860 vsize=4968 CPUtime=0.07
/proc/17862/stat : 17862 (pcs.small) R 17860 17862 17322 0 -1 4194304 971 956 0 0 7 0 0 0 24 0 1 0 58514407 5087232 579 996147200 134512640 135095119 4294956304 18446744073709551615 134918271 0 0 4096 0 0 0 0 17 0 0 0
/proc/17862/statm: 1242 579 400 142 0 196 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 4968

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

Child status: 0
Real time (s): 0.149801
CPU time (s): 0.136978
CPU user time (s): 0.131979
CPU system time (s): 0.004999
CPU usage (%): 91.4399
Max. virtual memory (cumulated for all children) (KiB): 5356

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

runsolver used 0.003999 second user time and 0.004999 second system time

The end

Launcher Data 

Begin job on node92 at 2009-07-16 05:21:34
IDJOB=2076961
IDBENCH=56533
IDSOLVER=733
FILE ID=node92/2076961-1247714494
PBS_JOBID= 9521414
Free space on /tmp= 66304 MiB

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

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

MD5SUM BENCH= 1f2b24ca3568cf58ecc49f3227589cf3
RANDOM SEED=665119128

node92.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.216
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.216
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:       1635368 kB
Buffers:         72908 kB
Cached:         225272 kB
SwapCached:          0 kB
Active:         123304 kB
Inactive:       227580 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1635368 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1876 kB
Writeback:           0 kB
Mapped:          73076 kB
Slab:            54736 kB
Committed_AS:   545892 kB
PageTables:       2020 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= 66300 MiB
End job on node92 at 2009-07-16 05:21:34