Trace number 361827

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, and are wall clock time (not CPU 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
bsolo 3.0.16UNSAT 0.127979 0.132332

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/web/
uclid_pb_benchmarks/normalized-blast-tlan2.ucl.opb
MD5SUM4e47a51846328cc5c7e86accfdb9dc80
Bench CategorySATUNSAT-SMALLINT-LIN (no optimisation, small integers, 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.12098
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables2221
Total number of constraints3050
Number of constraints which are clauses2330
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints720
Minimum length of a constraint1
Maximum length of a constraint19
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 641
Number of bits of the biggest number in a constraint 10
Biggest sum of numbers in a constraint 2174
Number of bits of the biggest sum of numbers12
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data (download as text)

0.00/0.00	c bsolo beta version 3.0.16 - 04/04/2007 : 1458 GMT
0.00/0.00	c Developed by Vasco Manquinho IST/UTL - INESC-ID
0.00/0.00	c type "bsolo -h" for help
0.00/0.00	c Time Limit set via environment variable PBTIMEOUT to 1800
0.00/0.00	c Time Limit set to 1800
0.00/0.00	c Memory Limit set to 1800 MB
0.00/0.00	c Instance file /tmp/evaluation/361827-1176985967/instance-361827-1176985967.opb
0.00/0.00	c File size is 193494 bytes.
0.01/0.03	c Highest Coefficient sum: 2174
0.01/0.03	c Parsing was ok!!
0.01/0.03	c Total parsing time: 0.033 s
0.01/0.03	c Var: 2221 Constr: 3050 2330/0/720 Lit: 19088 Watch. Lit: 6881
0.01/0.03	c Obj. Vars: 0 (0 % of total variables)
0.01/0.08	c Pre-processing Time: 0.081 s
0.01/0.08	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.01/0.08	c        0   1731     2154    13655    6     6014   20367      0      0 0.08
0.01/0.08	c Switching off LPR mode.
0.09/0.13	c      100   1731     2254    14442    6     7598   22404    100   1063 0.09
0.09/0.13	c      250   1730     2404    15527    6     7883   24645    250   2212 0.11
0.09/0.13	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.09/0.13	c    2      341      8      375     2495    15993    341   2706 0.13
0.09/0.13	s UNSATISFIABLE
0.09/0.13	c Total time: 0.126 s

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

runsolver version 3.2.2 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node72/watcher-361827-1176985967 -o ROOT/results/node72/solver-361827-1176985967 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/361827-1176985967/instance-361827-1176985967.opb 

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): 3600 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.09 1.04 0.95 3/77 32124
/proc/meminfo: memFree=1770880/2055920 swapFree=4157116/4192956
[pid=32124] ppid=32122 vsize=19740 CPUtime=0
/proc/32124/stat : 32124 (bsolo3.0.16) R 32122 32124 31677 0 -1 4194304 367 0 0 0 0 0 0 0 18 0 1 0 174635138 20213760 335 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 2971259 0 0 4096 16384 0 0 0 17 1 0 0
/proc/32124/statm: 4935 336 282 324 0 3956 0

[startup+0.015035 s]
/proc/loadavg: 1.09 1.04 0.95 3/77 32124
/proc/meminfo: memFree=1770880/2055920 swapFree=4157116/4192956
[pid=32124] ppid=32122 vsize=4392 CPUtime=0.01
/proc/32124/stat : 32124 (bsolo3.0.16) R 32122 32124 31677 0 -1 4194304 453 0 0 0 1 0 0 0 18 0 1 0 174635138 4497408 421 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/32124/statm: 1098 421 298 324 0 119 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 4392

[startup+0.101043 s]
/proc/loadavg: 1.09 1.04 0.95 3/77 32124
/proc/meminfo: memFree=1770880/2055920 swapFree=4157116/4192956
[pid=32124] ppid=32122 vsize=5160 CPUtime=0.09
/proc/32124/stat : 32124 (bsolo3.0.16) R 32122 32124 31677 0 -1 4194304 744 0 0 0 9 0 0 0 18 0 1 0 174635138 5283840 664 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/32124/statm: 1290 664 311 324 0 359 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 5160

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

Child status: 0
Real time (s): 0.132332
CPU time (s): 0.127979
CPU user time (s): 0.120981
CPU system time (s): 0.006998
CPU usage (%): 96.7105
Max. virtual memory (cumulated for all children) (KiB): 5160

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.120981
system time used= 0.006998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 746
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= 12
involuntary context switches= 19

runsolver used 0.001999 second user time and 0.008998 second system time

The end

Launcher Data (download as text)

Begin job on node72 on Thu Apr 19 12:32:47 UTC 2007

IDJOB= 361827
IDBENCH= 1474
IDSOLVER= 163
FILE ID= node72/361827-1176985967

PBS_JOBID= 4630418

Free space on /tmp= 66404 MiB

SOLVER NAME= bsolo 3.0.16
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/SATUNSAT-SMALLINT/web/uclid_pb_benchmarks/normalized-blast-tlan2.ucl.opb
COMMAND LINE= bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/361827-1176985967/instance-361827-1176985967.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node72/watcher-361827-1176985967 -o ROOT/results/node72/solver-361827-1176985967 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/361827-1176985967/instance-361827-1176985967.opb            

META MD5SUM SOLVER= b11bf0769a124f73ad50b0fdfcd50482
MD5SUM BENCH=  4e47a51846328cc5c7e86accfdb9dc80

RANDOM SEED= 285786068

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node72.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.222
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.222
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:       1771224 kB
Buffers:         28368 kB
Cached:         181568 kB
SwapCached:      16912 kB
Active:          84080 kB
Inactive:       149820 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1771224 kB
SwapTotal:     4192956 kB
SwapFree:      4157116 kB
Dirty:            4600 kB
Writeback:           0 kB
Mapped:          30976 kB
Slab:            36256 kB
Committed_AS:  2769964 kB
PageTables:       1796 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= 66404 MiB

End job on node72 on Thu Apr 19 12:32:47 UTC 2007