Trace number 2090566

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.195969 0.201964

General information on the benchmark

Namecsp/composed-25-1-40/
normalized-composed-25-1-40-3_ext.xml
MD5SUM195ad38e5c9c38eee78ce79399db53d8
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.019996
Satisfiable
(Un)Satisfiability was proved
Number of variables33
Number of constraints262
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension262
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-2090566-1247391146)
0.13/0.17	c Converted in 53 ms
0.13/0.18	c solving(HOME/instance-2090566-1247391146,1800000)
0.13/0.18	c solving(HOME/instance-2090566-1247391146,1800000)
0.13/0.20	c (ffc_inout)
0.13/0.20	s UNSATISFIABLE
0.13/0.20	
0.13/0.20	c Time=27 ms Backtracks=7
0.13/0.20

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-2090566-1247391146/watcher-2090566-1247391146 -o /tmp/evaluation-result-2090566-1247391146/solver-2090566-1247391146 -C 1800 -W 2000 -M 900 HOME/solver HOME/instance-2090566-1247391146 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: 1.92 1.98 1.99 4/81 29183
/proc/meminfo: memFree=1847312/2055920 swapFree=4192812/4192956
[pid=29183] ppid=29181 vsize=5596 CPUtime=0
/proc/29183/stat : 29183 (bprolog) R 29181 29183 26629 0 -1 4194304 293 0 0 0 0 0 0 0 20 0 1 0 26177307 5730304 24 996147200 134512640 135105188 4294956096 18446744073709551615 11952932 0 0 4096 0 0 0 0 17 1 0 0
/proc/29183/statm: 1399 24 18 144 0 1229 0

[startup+0.139116 s]
/proc/loadavg: 1.92 1.98 1.99 4/81 29183
/proc/meminfo: memFree=1847312/2055920 swapFree=4192812/4192956
[pid=29183] ppid=29181 vsize=62208 CPUtime=0.13
/proc/29183/stat : 29183 (bprolog) R 29181 29183 26629 0 -1 4194304 1098 0 0 0 5 8 0 0 20 0 1 0 26177307 63700992 811 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 1 0 0
/proc/29183/statm: 15552 811 176 144 0 15036 0
Current children cumulated CPU time (s) 0.13
Current children cumulated vsize (KiB) 62208

[startup+0.201277 s]
/proc/loadavg: 1.92 1.98 1.99 4/81 29183
/proc/meminfo: memFree=1847312/2055920 swapFree=4192812/4192956
[pid=29183] ppid=29181 vsize=0 CPUtime=0.19
/proc/29183/stat : 29183 (bprolog) Z 29181 29183 26629 0 -1 4194316 1379 0 0 0 9 10 0 0 20 0 2 0 26177307 0 0 996147200 0 0 0 0 0 0 0 4096 2 18446744073709551615 0 0 17 1 0 0
/proc/29183/statm: 0 0 0 0 0 0 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 0

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

Child status: 0
Real time (s): 0.201964
CPU time (s): 0.195969
CPU user time (s): 0.093985
CPU system time (s): 0.101984
CPU usage (%): 97.0316
Max. virtual memory (cumulated for all children) (KiB): 62208

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.093985
system time used= 0.101984
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1379
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= 4
involuntary context switches= 38

runsolver used 0.000999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node69 at 2009-07-12 11:32:26
IDJOB=2090566
IDBENCH=59779
IDSOLVER=770
FILE ID=node69/2090566-1247391146
PBS_JOBID= 9507254
Free space on /tmp= 66504 MiB

SOLVER NAME= bpsolver 09
BENCH NAME= CPAI08/csp/composed-25-1-40/normalized-composed-25-1-40-3_ext.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2090566-1247391146/watcher-2090566-1247391146 -o /tmp/evaluation-result-2090566-1247391146/solver-2090566-1247391146 -C 1800 -W 2000 -M 900  HOME/solver HOME/instance-2090566-1247391146 1800

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

MD5SUM BENCH= 195ad38e5c9c38eee78ce79399db53d8
RANDOM SEED=1457295834

node69.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.211
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.211
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:       1847792 kB
Buffers:         21520 kB
Cached:         102240 kB
SwapCached:          0 kB
Active:         112028 kB
Inactive:        44240 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1847792 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1960 kB
Writeback:           0 kB
Mapped:          52852 kB
Slab:            36860 kB
Committed_AS:   234260 kB
PageTables:       1984 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= 66504 MiB
End job on node69 at 2009-07-12 11:32:26