Trace number 2076970

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
bpsolver 09SAT 0.684895 0.698912

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 bpsolver version 6.29.2009
0.00/0.02	c converting(HOME/instance-2076970-1247363234)
0.48/0.55	c Converted in 169 ms
0.58/0.62	c solving(HOME/instance-2076970-1247363234,1800000)
0.58/0.62	c solving(HOME/instance-2076970-1247363234,1800000)
0.58/0.69	c (ffc_inout)
0.58/0.69	s SATISFIABLE
0.58/0.69	v 0 1 1 4 1 0 4 18 15 0 17 10 0 0 2 17 0 5 0 0 0 
0.58/0.69	
0.58/0.69	c Time=134 ms Backtracks=0
0.58/0.69

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-2076970-1247363234/watcher-2076970-1247363234 -o /tmp/evaluation-result-2076970-1247363234/solver-2076970-1247363234 -C 1800 -W 2000 -M 900 HOME/solver HOME/instance-2076970-1247363234 1800 

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.15 2.10 2.03 4/82 18639
/proc/meminfo: memFree=1437152/2055920 swapFree=4192812/4192956
[pid=18639] ppid=18637 vsize=5356 CPUtime=0
/proc/18639/stat : 18639 (sh) R 18637 18639 16538 0 -1 4194304 263 0 0 0 0 0 0 0 22 0 1 0 23386738 5484544 230 996147200 4194304 4889804 548682068864 18446744073709551615 4314690 0 0 4100 65536 0 0 0 17 1 0 0
/proc/18639/statm: 1339 230 192 169 0 50 0

[startup+0.087785 s]
/proc/loadavg: 2.15 2.10 2.03 4/82 18639
/proc/meminfo: memFree=1437152/2055920 swapFree=4192812/4192956
[pid=18639] ppid=18637 vsize=62208 CPUtime=0.07
/proc/18639/stat : 18639 (bprolog) R 18637 18639 16538 0 -1 4194304 1101 0 0 0 4 3 0 0 22 0 1 0 23386738 63700992 814 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 1 0 0
/proc/18639/statm: 15552 814 174 144 0 15036 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 62208

[startup+0.102779 s]
/proc/loadavg: 2.15 2.10 2.03 4/82 18639
/proc/meminfo: memFree=1437152/2055920 swapFree=4192812/4192956
[pid=18639] ppid=18637 vsize=62208 CPUtime=0.08
/proc/18639/stat : 18639 (bprolog) R 18637 18639 16538 0 -1 4194304 1103 0 0 0 4 4 0 0 22 0 1 0 23386738 63700992 816 996147200 134512640 135105188 4294956096 18446744073709551615 134636111 0 0 4096 2 0 0 0 17 1 0 0
/proc/18639/statm: 15552 816 174 144 0 15036 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 62208

[startup+0.302805 s]
/proc/loadavg: 2.15 2.10 2.03 4/82 18639
/proc/meminfo: memFree=1437152/2055920 swapFree=4192812/4192956
[pid=18639] ppid=18637 vsize=62208 CPUtime=0.29
/proc/18639/stat : 18639 (bprolog) R 18637 18639 16538 0 -1 4194304 1116 0 0 0 10 19 0 0 23 0 1 0 23386738 63700992 829 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 1 0 0
/proc/18639/statm: 15552 829 176 144 0 15036 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 62208

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

[startup+0.502823 s]
/proc/loadavg: 2.15 2.10 2.03 4/82 18639
/proc/meminfo: memFree=1437152/2055920 swapFree=4192812/4192956
[pid=18639] ppid=18637 vsize=62208 CPUtime=0.48
/proc/18639/stat : 18639 (bprolog) R 18637 18639 16538 0 -1 4194304 1139 0 0 0 16 32 0 0 25 0 1 0 23386738 63700992 852 996147200 134512640 135105188 4294956096 18446744073709551615 134602988 0 0 4096 2 0 0 0 17 1 0 0
/proc/18639/statm: 15552 852 176 144 0 15036 0
Current children cumulated CPU time (s) 0.48
Current children cumulated vsize (KiB) 62208

[startup+0.60284 s]
/proc/loadavg: 2.15 2.10 2.03 4/82 18639
/proc/meminfo: memFree=1437152/2055920 swapFree=4192812/4192956
[pid=18639] ppid=18637 vsize=70020 CPUtime=0.58
/proc/18639/stat : 18639 (bprolog) R 18637 18639 16538 0 -1 4194304 1673 0 0 0 22 36 0 0 25 0 1 0 23386738 71700480 1384 996147200 134512640 135105188 4294956096 18446744073709551615 134570907 0 0 4096 2 0 0 0 17 1 0 0
/proc/18639/statm: 17505 1384 181 144 0 16989 0
Current children cumulated CPU time (s) 0.58
Current children cumulated vsize (KiB) 70020

Child status: 0
Real time (s): 0.698912
CPU time (s): 0.684895
CPU user time (s): 0.320951
CPU system time (s): 0.363944
CPU usage (%): 97.9945
Max. virtual memory (cumulated for all children) (KiB): 70020

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.320951
system time used= 0.363944
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1997
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= 5
involuntary context switches= 85

runsolver used 0.005999 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node64 at 2009-07-12 03:47:14
IDJOB=2076970
IDBENCH=56533
IDSOLVER=770
FILE ID=node64/2076970-1247363234
PBS_JOBID= 9506930
Free space on /tmp= 66324 MiB

SOLVER NAME= bpsolver 09
BENCH NAME= CPAI08/csp/ogdHerald/normalized-crossword-m1-ogd-05-07.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2076970-1247363234/watcher-2076970-1247363234 -o /tmp/evaluation-result-2076970-1247363234/solver-2076970-1247363234 -C 1800 -W 2000 -M 900  HOME/solver HOME/instance-2076970-1247363234 1800

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

MD5SUM BENCH= 1f2b24ca3568cf58ecc49f3227589cf3
RANDOM SEED=79342680

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:       1437632 kB
Buffers:         22592 kB
Cached:          85460 kB
SwapCached:          0 kB
Active:         514644 kB
Inactive:        53544 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1437632 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1512 kB
Writeback:           0 kB
Mapped:         480556 kB
Slab:            33988 kB
Committed_AS:   644868 kB
PageTables:       2696 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= 66320 MiB
End job on node64 at 2009-07-12 03:47:15