Trace number 2079115

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 09UNSAT 0.136979 0.144716

General information on the benchmark

Namecsp/lexVg/
normalized-crossword-m1c-lex-vg13-16_ext.xml
MD5SUM27760add14b2cdb3a3b114747434e548
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.020996
Satisfiable
(Un)Satisfiability was proved
Number of variables208
Number of constraints29
Maximum constraint arity16
Maximum domain size26
Number of constraints which are defined in extension29
Number of constraints which are defined in intension0
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-2079115-1247367843)
0.05/0.08	c Converted in 15 ms
0.05/0.09	c solving(HOME/instance-2079115-1247367843,1800000)
0.05/0.09	c solving(HOME/instance-2079115-1247367843,1800000)
0.09/0.14	c before_labeling
0.09/0.14	s UNSATISFIABLE
0.09/0.14	
0.09/0.14	
0.09/0.14	c Time=58 ms Backtracks=0
0.09/0.14

Verifier Data 

No possible verification on an UNSAT instance

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2079115-1247367843/watcher-2079115-1247367843 -o /tmp/evaluation-result-2079115-1247367843/solver-2079115-1247367843 -C 1800 -W 2000 -M 900 HOME/solver HOME/instance-2079115-1247367843 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.14 2.04 2.06 4/74 21598
/proc/meminfo: memFree=1301616/2055920 swapFree=4192956/4192956
[pid=21598] ppid=21596 vsize=18576 CPUtime=0
/proc/21598/stat : 21598 (runsolver) R 21596 21598 17578 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 23851290 19021824 284 996147200 4194304 4302564 548682068528 18446744073709551615 252429528359 0 0 4096 24578 0 0 0 17 1 0 0
/proc/21598/statm: 4644 284 249 26 0 2626 0

[startup+0.0699621 s]
/proc/loadavg: 2.14 2.04 2.06 4/74 21598
/proc/meminfo: memFree=1301616/2055920 swapFree=4192956/4192956
[pid=21598] ppid=21596 vsize=62208 CPUtime=0.05
/proc/21598/stat : 21598 (bprolog) R 21596 21598 17578 0 -1 4194304 1121 0 0 0 2 3 0 0 20 0 1 0 23851290 63700992 834 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 1 0 0
/proc/21598/statm: 15552 834 176 144 0 15036 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 62208

[startup+0.101959 s]
/proc/loadavg: 2.14 2.04 2.06 4/74 21598
/proc/meminfo: memFree=1301616/2055920 swapFree=4192956/4192956
[pid=21598] ppid=21596 vsize=70168 CPUtime=0.09
/proc/21598/stat : 21598 (bprolog) R 21596 21598 17578 0 -1 4194304 1331 0 0 0 5 4 0 0 20 0 1 0 23851290 71852032 1041 996147200 134512640 135105188 4294956096 18446744073709551615 134717767 0 0 4096 2 0 0 0 17 1 0 0
/proc/21598/statm: 17542 1041 193 144 0 17026 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 70168

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

Child status: 0
Real time (s): 0.144716
CPU time (s): 0.136979
CPU user time (s): 0.091986
CPU system time (s): 0.044993
CPU usage (%): 94.6537
Max. virtual memory (cumulated for all children) (KiB): 70168

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.091986
system time used= 0.044993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1334
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= 3
involuntary context switches= 31

runsolver used 0.003999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node12 at 2009-07-12 05:04:03
IDJOB=2079115
IDBENCH=56850
IDSOLVER=770
FILE ID=node12/2079115-1247367843
PBS_JOBID= 9507003
Free space on /tmp= 66212 MiB

SOLVER NAME= bpsolver 09
BENCH NAME= CPAI08/csp/lexVg/normalized-crossword-m1c-lex-vg13-16_ext.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2079115-1247367843/watcher-2079115-1247367843 -o /tmp/evaluation-result-2079115-1247367843/solver-2079115-1247367843 -C 1800 -W 2000 -M 900  HOME/solver HOME/instance-2079115-1247367843 1800

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

MD5SUM BENCH= 27760add14b2cdb3a3b114747434e548
RANDOM SEED=462886640

node12.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.240
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.240
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:       1302096 kB
Buffers:         81848 kB
Cached:         541440 kB
SwapCached:          0 kB
Active:         207224 kB
Inactive:       466084 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1302096 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            1720 kB
Writeback:           0 kB
Mapped:          61260 kB
Slab:            65872 kB
Committed_AS:   186632 kB
PageTables:       1856 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= 66208 MiB
End job on node12 at 2009-07-12 05:04:03