Trace number 1884540

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-26Wrong UNSAT 0.241962 0.216875

General information on the benchmark

Name/PURE-SAT/SAT09/CRAFTED/sgen/
sat/sgen1-sat-140-100.opb
MD5SUM49a573c597662f8fdba02237e2ca563f
Bench CategoryPURE-SAT (instances containing only clauses)
Best result obtained on this benchmarkSAT
Best value of the objective obtained on this benchmark0
Best CPU time to get the best result obtained on this benchmark100.112
Has Objective FunctionNO
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables140
Total number of constraints336
Number of constraints which are clauses336
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 constraint5
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 6
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.10/0.18	------------------------
0.10/0.18	Encoding : LINEAR, DIRECT, BDD, POLYW, GLOBC
0.10/0.18	Size : 0, 840, 0, 0, 0
0.10/0.18	Count : 0, 336, 0, 0, 0
0.10/0.18	
0.10/0.18	Command line : minisat tmp.dimacs %var 
0.10/0.18	
0.10/0.18	------------------------
0.10/0.19	This is MiniSat 2.0 beta
0.10/0.19	WARNING: for repeatability, setting FPU to use double precision
0.10/0.19	============================[ Problem Statistics ]=============================
0.10/0.19	|                                                                             |
0.10/0.19	|  Number of variables:  -1                                                   |
0.10/0.19	|  Number of clauses:    -2                                                   |
0.10/0.19	|  Parsing time:         0.00         s                                       |
0.10/0.19	Solved by unit propagation
0.10/0.19	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-1884540-1245259476/watcher-1884540-1245259476 -o /tmp/evaluation-result-1884540-1245259476/solver-1884540-1245259476 -C 1800 -W 2000 -M 1800 java -Xmx1500m -jar pb2cnfsolver.jar 6 HOME/instance-1884540-1245259476.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.99 1.00 0.91 3/64 21823
/proc/meminfo: memFree=1553888/2055920 swapFree=4182028/4192956
[pid=21823] ppid=21821 vsize=152 CPUtime=0
/proc/21823/stat : 21823 (java) R 21821 21823 21304 0 -1 0 41 0 0 0 0 0 0 0 20 0 1 0 193548539 155648 26 1992294400 134512640 134550932 4294956192 18446744073709551615 10588459 0 0 4096 0 0 0 0 17 1 0 0
/proc/21823/statm: 38 26 19 9 0 4 0

[startup+0.0290419 s]
/proc/loadavg: 0.99 1.00 0.91 3/64 21823
/proc/meminfo: memFree=1553888/2055920 swapFree=4182028/4192956
[pid=21823] ppid=21821 vsize=1682168 CPUtime=0.01
/proc/21823/stat : 21823 (java) S 21821 21823 21304 0 -1 0 1539 0 1 0 0 1 0 0 18 0 5 0 193548539 1722540032 1204 1992294400 134512640 134550932 4294956032 18446744073709551615 4294960144 0 0 0 16784584 18446744073709551615 0 0 17 1 0 0
/proc/21823/statm: 420542 1204 695 9 0 415457 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 1682168

[startup+0.102635 s]
/proc/loadavg: 0.99 1.00 0.91 3/64 21823
/proc/meminfo: memFree=1553888/2055920 swapFree=4182028/4192956
[pid=21823] ppid=21821 vsize=1684404 CPUtime=0.1
/proc/21823/stat : 21823 (java) S 21821 21823 21304 0 -1 0 2806 0 1 0 9 1 0 0 18 0 9 0 193548539 1724829696 2301 1992294400 134512640 134550932 4294956032 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/21823/statm: 421101 2301 1214 9 0 416012 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 1684404

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

[startup+0.201701 s]
/proc/loadavg: 0.99 1.00 0.91 3/64 21823
/proc/meminfo: memFree=1553888/2055920 swapFree=4182028/4192956
[pid=21823] ppid=21821 vsize=1685204 CPUtime=0.23
/proc/21823/stat : 21823 (java) S 21821 21823 21304 0 -1 0 3783 107 1 0 21 2 0 0 18 0 9 0 193548539 1725648896 2740 1992294400 134512640 134550932 4294956032 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/21823/statm: 421301 2740 1270 9 0 416212 0
Current children cumulated CPU time (s) 0.23
Current children cumulated vsize (KiB) 1685204

Child status: 0
Real time (s): 0.216875
CPU time (s): 0.241962
CPU user time (s): 0.214967
CPU system time (s): 0.026995
CPU usage (%): 111.567
Max. virtual memory (cumulated for all children) (KiB): 1685204

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.214967
system time used= 0.026995
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3923
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= 183
involuntary context switches= 39

runsolver used 0.003999 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node4 at 2009-06-17 19:24:36
IDJOB=1884540
IDBENCH=71967
IDSOLVER=688
FILE ID=node4/1884540-1245259476
PBS_JOBID= 9372449
Free space on /tmp= 66408 MiB

SOLVER NAME= BoolVar 2009-04-26
BENCH NAME= PB09/normalized-PB09/PURE-SAT/SAT09/CRAFTED/sgen/sat/sgen1-sat-140-100.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-1884540-1245259476/watcher-1884540-1245259476 -o /tmp/evaluation-result-1884540-1245259476/solver-1884540-1245259476 -C 1800 -W 2000 -M 1800  java -Xmx1500m -jar pb2cnfsolver.jar 6 HOME/instance-1884540-1245259476.opb minisat %dimacs %var

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

MD5SUM BENCH= 49a573c597662f8fdba02237e2ca563f
RANDOM SEED=566008170

node4.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.259
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.259
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:       1554432 kB
Buffers:         38580 kB
Cached:         371020 kB
SwapCached:       4996 kB
Active:          45412 kB
Inactive:       372360 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1554432 kB
SwapTotal:     4192956 kB
SwapFree:      4182028 kB
Dirty:             852 kB
Writeback:           0 kB
Mapped:          14464 kB
Slab:            69752 kB
Committed_AS:   170308 kB
PageTables:       1472 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-1884540-1245259476.opb

Free space on /tmp at the end= 66408 MiB
End job on node4 at 2009-06-17 19:24:36