Trace number 2682704

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
PB/CT 0.1 fixedUNSAT 0.240962 0.24082

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/web/
uclid_pb_benchmarks/normalized-37s.smv.opb
MD5SUMc32b20024d9dbe3bb08a79a9b8e2d75c
Bench CategoryDEC-SMALLINT (no optimisation, small integers)
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.023995
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables1190
Total number of constraints3183
Number of constraints which are clauses3055
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints128
Minimum length of a constraint1
Maximum length of a constraint11
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 43
Number of bits of the biggest number in a constraint 6
Biggest sum of numbers in a constraint 136
Number of bits of the biggest sum of numbers8
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data 

0.00/0.00	c PB/CT 0.1.1 http://www.residual.se/pbct
0.00/0.00	c Based on OpenSMT/CT 20091015
0.03/0.04	c constraints 128/0 clauses 2897/0 units 68
0.03/0.04	c vars 1190
0.09/0.18	c 0.160975 16.3398 89 333
0.20/0.23	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-2682704-1277476459/watcher-2682704-1277476459 -o /tmp/evaluation-result-2682704-1277476459/solver-2682704-1277476459 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2682704-1277476459.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): 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: 1.00 0.94 0.57 3/106 29848
/proc/meminfo: memFree=1804572/2059040 swapFree=4140556/4192956
[pid=29848] ppid=29846 vsize=2136 CPUtime=0
/proc/29848/stat : 29848 (pbct) R 29846 29848 29393 0 -1 4202496 246 0 0 0 0 0 0 0 20 0 1 0 88941232 2187264 165 1992294400 134512640 136421960 4290241696 18446744073709551615 135378148 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/29848/statm: 534 165 144 467 0 65 0

[startup+0.0373781 s]
/proc/loadavg: 1.00 0.94 0.57 3/106 29848
/proc/meminfo: memFree=1804572/2059040 swapFree=4140556/4192956
[pid=29848] ppid=29846 vsize=2268 CPUtime=0.03
/proc/29848/stat : 29848 (pbct) R 29846 29848 29393 0 -1 4202496 301 0 0 0 3 0 0 0 20 0 1 0 88941232 2322432 220 1992294400 134512640 136421960 4290241696 18446744073709551615 135829965 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/29848/statm: 567 220 146 467 0 98 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 2268

[startup+0.101363 s]
/proc/loadavg: 1.00 0.94 0.57 3/106 29848
/proc/meminfo: memFree=1804572/2059040 swapFree=4140556/4192956
[pid=29848] ppid=29846 vsize=9208 CPUtime=0.09
/proc/29848/stat : 29848 (pbct) R 29846 29848 29393 0 -1 4202496 2022 0 0 0 8 1 0 0 20 0 1 0 88941232 9428992 1941 1992294400 134512640 136421960 4290241696 18446744073709551615 135811817 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/29848/statm: 2302 1942 193 467 0 1833 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 9208

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

[startup+0.201369 s]
/proc/loadavg: 1.00 0.94 0.57 3/106 29848
/proc/meminfo: memFree=1804572/2059040 swapFree=4140556/4192956
[pid=29848] ppid=29846 vsize=16076 CPUtime=0.2
/proc/29848/stat : 29848 (pbct) R 29846 29848 29393 0 -1 4202496 3833 0 0 0 18 2 0 0 20 0 1 0 88941232 16461824 3596 1992294400 134512640 136421960 4290241696 18446744073709551615 134654884 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/29848/statm: 4019 3596 236 467 0 3550 0
Current children cumulated CPU time (s) 0.2
Current children cumulated vsize (KiB) 16076

Child status: 0
Real time (s): 0.24082
CPU time (s): 0.240962
CPU user time (s): 0.217966
CPU system time (s): 0.022996
CPU usage (%): 100.059
Max. virtual memory (cumulated for all children) (KiB): 16076

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.217966
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= 3834
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= 1
involuntary context switches= 1

runsolver used 0.003999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node030 at 2010-06-25 16:34:19
IDJOB=2682704
IDBENCH=1458
IDSOLVER=1192
FILE ID=node030/2682704-1277476459
PBS_JOBID= 11190513
Free space on /tmp= 62492 MiB

SOLVER NAME= PB/CT 0.1 fixed
BENCH NAME= PB06//final/normalized-PB06/SATUNSAT-SMALLINT/web/uclid_pb_benchmarks/normalized-37s.smv.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2682704-1277476459/watcher-2682704-1277476459 -o /tmp/evaluation-result-2682704-1277476459/solver-2682704-1277476459 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2682704-1277476459.opb

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

MD5SUM BENCH= c32b20024d9dbe3bb08a79a9b8e2d75c
RANDOM SEED=277347293

node030.alineos.net Linux 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009

/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.244
cache size	: 2048 KB
physical id	: 0
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 0
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 6000.48
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.244
cache size	: 2048 KB
physical id	: 3
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 6
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5599.52
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1804976 kB
Buffers:         42012 kB
Cached:         107160 kB
SwapCached:       5752 kB
Active:          65028 kB
Inactive:        97924 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1804976 kB
SwapTotal:     4192956 kB
SwapFree:      4140556 kB
Dirty:            2264 kB
Writeback:           0 kB
AnonPages:       11912 kB
Mapped:          12244 kB
Slab:            69192 kB
PageTables:       4100 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   180920 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264948 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 62492 MiB
End job on node030 at 2010-06-25 16:34:19