Trace number 1884710

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.109982 0.155788

General information on the benchmark

Name/PURE-SAT/SAT09/CRAFTED/
parity-games/instance_n2_i2_pp.opb
MD5SUMe1525758eb4413d1342840694ada876e
Bench CategoryPURE-SAT (instances containing only clauses)
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.000999
Has Objective FunctionNO
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables27
Total number of constraints53
Number of constraints which are clauses53
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint2
Maximum length of a constraint3
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 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 4
Number of bits of the biggest sum of numbers3
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data 

0.07/0.09	------------------------
0.07/0.09	Encoding : LINEAR, DIRECT, BDD, POLYW, GLOBC
0.07/0.09	Size : 0, 114, 0, 0, 0
0.07/0.09	Count : 0, 53, 0, 0, 0
0.07/0.09	
0.07/0.09	Command line : minisat tmp.dimacs %var 
0.07/0.09	
0.07/0.09	------------------------
0.07/0.10	This is MiniSat 2.0 beta
0.09/0.10	WARNING: for repeatability, setting FPU to use double precision
0.09/0.10	============================[ Problem Statistics ]=============================
0.09/0.10	|                                                                             |
0.09/0.10	|  Number of variables:  -1                                                   |
0.09/0.10	|  Number of clauses:    19                                                   |
0.09/0.10	|  Parsing time:         0.00         s                                       |
0.09/0.10	Solved by unit propagation
0.09/0.10	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-1884710-1245260192/watcher-1884710-1245260192 -o /tmp/evaluation-result-1884710-1245260192/solver-1884710-1245260192 -C 1800 -W 2000 -M 1800 java -Xmx1500m -jar pb2cnfsolver.jar 6 HOME/instance-1884710-1245260192.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.01 0.99 3/65 6452
/proc/meminfo: memFree=1747096/2055920 swapFree=4182240/4192956
[pid=6452] ppid=6450 vsize=18576 CPUtime=0
/proc/6452/stat : 6452 (runsolver) R 6450 6452 5911 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 193617724 19021824 284 1992294400 4194304 4302564 548682068448 18446744073709551615 214945033511 0 2147483391 4096 24578 0 0 0 17 0 0 0
/proc/6452/statm: 4644 284 249 26 0 2626 0

[startup+0.083745 s]
/proc/loadavg: 0.93 1.01 0.99 3/65 6452
/proc/meminfo: memFree=1747096/2055920 swapFree=4182240/4192956
[pid=6452] ppid=6450 vsize=1685156 CPUtime=0.07
/proc/6452/stat : 6452 (java) S 6450 6452 5911 0 -1 0 2813 0 1 0 5 2 0 0 18 0 9 0 193617724 1725599744 2301 1992294400 134512640 134550932 4294956032 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/6452/statm: 421289 2301 1236 9 0 416200 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 1685156

[startup+0.102743 s]
/proc/loadavg: 0.93 1.01 0.99 3/65 6452
/proc/meminfo: memFree=1747096/2055920 swapFree=4182240/4192956
[pid=6452] ppid=6450 vsize=1686128 CPUtime=0.09
/proc/6452/stat : 6452 (java) S 6450 6452 5911 0 -1 0 3230 103 1 0 7 2 0 0 18 0 11 0 193617724 1726595072 2430 1992294400 134512640 134550932 4294956032 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/6452/statm: 421532 2430 1262 9 0 416443 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 1686128

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

Child status: 0
Real time (s): 0.155788
CPU time (s): 0.109982
CPU user time (s): 0.079987
CPU system time (s): 0.029995
CPU usage (%): 70.5973
Max. virtual memory (cumulated for all children) (KiB): 1686128

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.079987
system time used= 0.029995
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3582
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= 105
involuntary context switches= 27

runsolver used 0.001999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node85 at 2009-06-17 19:36:32
IDJOB=1884710
IDBENCH=71984
IDSOLVER=688
FILE ID=node85/1884710-1245260192
PBS_JOBID= 9372377
Free space on /tmp= 126840 MiB

SOLVER NAME= BoolVar 2009-04-26
BENCH NAME= PB09/normalized-PB09/PURE-SAT/SAT09/CRAFTED/parity-games/instance_n2_i2_pp.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-1884710-1245260192/watcher-1884710-1245260192 -o /tmp/evaluation-result-1884710-1245260192/solver-1884710-1245260192 -C 1800 -W 2000 -M 1800  java -Xmx1500m -jar pb2cnfsolver.jar 6 HOME/instance-1884710-1245260192.opb minisat %dimacs %var

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

MD5SUM BENCH= e1525758eb4413d1342840694ada876e
RANDOM SEED=1916429738

node85.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.213
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	: 5931.00
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.213
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:       1747712 kB
Buffers:         39920 kB
Cached:         195536 kB
SwapCached:       5196 kB
Active:          73340 kB
Inactive:       170312 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1747712 kB
SwapTotal:     4192956 kB
SwapFree:      4182240 kB
Dirty:             844 kB
Writeback:           0 kB
Mapped:          13828 kB
Slab:            50600 kB
Committed_AS:    95768 kB
PageTables:       1376 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-1884710-1245260192.opb

Free space on /tmp at the end= 126836 MiB
End job on node85 at 2009-06-17 19:36:32