Trace number 1883805

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
BoolVar 2009-04-26UNSAT 0.225965 0.204519

General information on the benchmark

Namenormalized-PB07/SATUNSAT-SMALLINT-NLC/submittedPB07/
manquinho/dbsg/normalized-dbsg_10_4_5_8.opb
MD5SUM90a2e4775cb0b93d8a9a388ce1bcf6ee
Bench CategoryDEC-SMALLINT-NLC (no optimisation, small integers, non linear constraints)
Best result obtained on this benchmarkUNSAT
Best value of the objective obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark0.001999
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables20
Total number of constraints32
Number of constraints which are clauses10
Number of constraints which are cardinality constraints (but not clauses)1
Number of constraints which are nor clauses,nor cardinality constraints21
Minimum length of a constraint2
Maximum length of a constraint20
Number of terms in the objective function 0
Biggest coefficient in the objective function 0
Number of bits for the biggest coefficient in the objective function 0
Sum of the numbers in the objective function 0
Number of bits of the sum of numbers in the objective function 0
Biggest number in a constraint 8
Number of bits of the biggest number in a constraint 4
Biggest sum of numbers in a constraint 20
Number of bits of the biggest sum of numbers5
Number of products (including duplicates)92
Sum of products size (including duplicates)184
Number of different products46
Sum of products size92

Solver Data 

0.11/0.16	------------------------
0.11/0.16	Encoding : LINEAR, DIRECT, BDD, POLYW, GLOBC
0.11/0.16	Size : 0, 690, 0, 0, 2046
0.11/0.16	Count : 0, 122, 0, 0, 3
0.11/0.16	
0.11/0.16	Command line : minisat tmp.dimacs %var 
0.11/0.16	
0.11/0.16	------------------------
0.11/0.16	This is MiniSat 2.0 beta
0.11/0.16	WARNING: for repeatability, setting FPU to use double precision
0.11/0.16	============================[ Problem Statistics ]=============================
0.11/0.16	|                                                                             |
0.11/0.16	|  Number of variables:  1                                                    |
0.11/0.16	|  Number of clauses:    67                                                   |
0.11/0.16	|  Parsing time:         0.00         s                                       |
0.11/0.16	Solved by unit propagation
0.11/0.16	s UNSATISFIABLE

Verifier Data 

ERROR: no interpretation found !

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1883805-1245215818/watcher-1883805-1245215818 -o /tmp/evaluation-result-1883805-1245215818/solver-1883805-1245215818 -C 1800 -W 2000 -M 1800 java -Xmx1500m -jar pb2cnfsolver.jar 6 HOME/instance-1883805-1245215818.opb minisat %dimacs %var 

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): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.93 1.00 0.99 3/64 2229
/proc/meminfo: memFree=1777632/2055920 swapFree=4181500/4192956
[pid=2229] ppid=2227 vsize=152 CPUtime=0
/proc/2229/stat : 2229 (java) R 2227 2229 1590 0 -1 0 221 0 0 0 0 0 0 0 18 0 1 0 189181605 155648 26 1992294400 134512640 134550932 4294956032 18446744073709551615 10027307 0 0 4096 0 0 0 0 17 0 0 0
/proc/2229/statm: 38 26 19 9 0 4 0

[startup+0.042505 s]
/proc/loadavg: 0.93 1.00 0.99 3/64 2229
/proc/meminfo: memFree=1777632/2055920 swapFree=4181500/4192956
[pid=2229] ppid=2227 vsize=1683848 CPUtime=0.03
/proc/2229/stat : 2229 (java) S 2227 2229 1590 0 -1 0 2072 0 1 0 2 1 0 0 18 0 9 0 189181605 1724260352 1629 1992294400 134512640 134550932 4294956032 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/2229/statm: 420962 1632 916 9 0 415877 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 1683848

[startup+0.102419 s]
/proc/loadavg: 0.93 1.00 0.99 3/64 2229
/proc/meminfo: memFree=1777632/2055920 swapFree=4181500/4192956
[pid=2229] ppid=2227 vsize=1685288 CPUtime=0.11
/proc/2229/stat : 2229 (java) S 2227 2229 1590 0 -1 0 2905 0 1 0 10 1 0 0 18 0 9 0 189181605 1725734912 2391 1992294400 134512640 134550932 4294956032 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/2229/statm: 421322 2391 1243 9 0 416233 0
Current children cumulated CPU time (s) 0.11
Current children cumulated vsize (KiB) 1685288

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

[startup+0.201522 s]
/proc/loadavg: 0.93 1.00 0.99 3/64 2229
/proc/meminfo: memFree=1777632/2055920 swapFree=4181500/4192956
[pid=2229] ppid=2227 vsize=1686420 CPUtime=0.21
/proc/2229/stat : 2229 (java) S 2227 2229 1590 0 -1 0 3451 121 1 0 20 1 0 0 18 0 9 0 189181605 1726894080 2656 1992294400 134512640 134550932 4294956032 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 0 0 0
/proc/2229/statm: 421605 2656 1270 9 0 416516 0
Current children cumulated CPU time (s) 0.21
Current children cumulated vsize (KiB) 1686420

Child status: 0
Real time (s): 0.204519
CPU time (s): 0.225965
CPU user time (s): 0.202969
CPU system time (s): 0.022996
CPU usage (%): 110.486
Max. virtual memory (cumulated for all children) (KiB): 1686420

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.202969
system time used= 0.022996
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3625
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 134
involuntary context switches= 62

runsolver used 0.003999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node25 at 2009-06-17 07:16:58
IDJOB=1883805
IDBENCH=48344
IDSOLVER=688
FILE ID=node25/1883805-1245215818
PBS_JOBID= 9368401
Free space on /tmp= 66312 MiB

SOLVER NAME= BoolVar 2009-04-26
BENCH NAME= PB07/normalized-PB07/SATUNSAT-SMALLINT-NLC/submittedPB07/manquinho/dbsg/normalized-dbsg_10_4_5_8.opb
COMMAND LINE= java -Xmx1500m -jar pb2cnfsolver.jar 6 BENCHNAME minisat %dimacs %var
CONVERSION SCRIPT= PBconversionToLinear BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1883805-1245215818/watcher-1883805-1245215818 -o /tmp/evaluation-result-1883805-1245215818/solver-1883805-1245215818 -C 1800 -W 2000 -M 1800  java -Xmx1500m -jar pb2cnfsolver.jar 6 HOME/instance-1883805-1245215818.opb minisat %dimacs %var

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

MD5SUM BENCH= 90a2e4775cb0b93d8a9a388ce1bcf6ee
RANDOM SEED=1039341657

node25.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.238
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.238
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:       1778240 kB
Buffers:         58772 kB
Cached:         141112 kB
SwapCached:       5884 kB
Active:          86912 kB
Inactive:       121556 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1778240 kB
SwapTotal:     4192956 kB
SwapFree:      4181500 kB
Dirty:             908 kB
Writeback:           0 kB
Mapped:          13652 kB
Slab:            55308 kB
Committed_AS:   216760 kB
PageTables:       1464 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

CONVERSION COMMAND LINE= PBconversionToLinear HOME/instance-1883805-1245215818.opb

Free space on /tmp at the end= 66312 MiB
End job on node25 at 2009-06-17 07:16:59