Trace number 2669142

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.1Wrong UNSAT 2.09868 2.09872

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/web/www.ps.uni-sb.de/
~walser/benchmarks/ppp-problems/normalized-ppp:1-9,16-19.opb
MD5SUM732cdc3fa8b0bf0f47e882c13d928a6d
Bench CategoryDEC-SMALLINT (no optimisation, small integers)
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 benchmark1552.26
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables4626
Total number of constraints30747
Number of constraints which are clauses29724
Number of constraints which are cardinality constraints (but not clauses)945
Number of constraints which are nor clauses,nor cardinality constraints78
Minimum length of a constraint3
Maximum length of a constraint29
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 10
Number of bits of the biggest number in a constraint 4
Biggest sum of numbers in a constraint 101
Number of bits of the biggest sum of numbers7
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 http://www.residual.se/pbct
0.00/0.00	c Based on OpenSMT/CT 20091015
0.39/0.47	c constraints 1023/0 clauses 29724/0 units 0
0.39/0.47	c vars 4626
1.59/1.63	c 1.52977 102.336 0 0
1.99/2.08	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-2669142-1276435565/watcher-2669142-1276435565 -o /tmp/evaluation-result-2669142-1276435565/solver-2669142-1276435565 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2669142-1276435565.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: 0.93 1.00 0.99 3/106 26927
/proc/meminfo: memFree=1873464/2059040 swapFree=4135652/4192956
[pid=26927] ppid=26925 vsize=2340 CPUtime=0
/proc/26927/stat : 26927 (pbct) R 26925 26927 25934 0 -1 4202496 296 0 0 0 0 0 0 0 23 0 1 0 19160477 2396160 218 1992294400 134512640 136485738 4287509840 18446744073709551615 135850441 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/26927/statm: 585 219 156 482 0 101 0

[startup+0.0979159 s]
/proc/loadavg: 0.93 1.00 0.99 3/106 26927
/proc/meminfo: memFree=1873464/2059040 swapFree=4135652/4192956
[pid=26927] ppid=26925 vsize=2872 CPUtime=0.09
/proc/26927/stat : 26927 (pbct) R 26925 26927 25934 0 -1 4202496 438 0 0 0 9 0 0 0 23 0 1 0 19160477 2940928 360 1992294400 134512640 136485738 4287509840 18446744073709551615 134539969 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/26927/statm: 718 360 156 482 0 234 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2872

[startup+0.100917 s]
/proc/loadavg: 0.93 1.00 0.99 3/106 26927
/proc/meminfo: memFree=1873464/2059040 swapFree=4135652/4192956
[pid=26927] ppid=26925 vsize=2872 CPUtime=0.09
/proc/26927/stat : 26927 (pbct) R 26925 26927 25934 0 -1 4202496 439 0 0 0 9 0 0 0 23 0 1 0 19160477 2940928 361 1992294400 134512640 136485738 4287509840 18446744073709551615 135857078 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/26927/statm: 718 361 156 482 0 234 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2872

[startup+0.300937 s]
/proc/loadavg: 0.93 1.00 0.99 3/106 26927
/proc/meminfo: memFree=1873464/2059040 swapFree=4135652/4192956
[pid=26927] ppid=26925 vsize=3400 CPUtime=0.29
/proc/26927/stat : 26927 (pbct) R 26925 26927 25934 0 -1 4202496 556 0 0 0 29 0 0 0 23 0 1 0 19160477 3481600 478 1992294400 134512640 136485738 4287509840 18446744073709551615 135332318 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/26927/statm: 850 478 156 482 0 366 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 3400

[startup+0.700978 s]
/proc/loadavg: 0.93 1.00 0.99 3/106 26927
/proc/meminfo: memFree=1873464/2059040 swapFree=4135652/4192956
[pid=26927] ppid=26925 vsize=24936 CPUtime=0.69
/proc/26927/stat : 26927 (pbct) R 26925 26927 25934 0 -1 4202496 6203 0 0 0 66 3 0 0 25 0 1 0 19160477 25534464 5705 1992294400 134512640 136485738 4287509840 18446744073709551615 134616329 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/26927/statm: 6234 5706 191 482 0 5750 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 24936

[startup+1.50106 s]
/proc/loadavg: 0.93 1.00 0.99 2/107 26928
/proc/meminfo: memFree=1832412/2059040 swapFree=4135652/4192956
[pid=26927] ppid=26925 vsize=101284 CPUtime=1.49
/proc/26927/stat : 26927 (pbct) R 26925 26927 25934 0 -1 4202496 26396 0 0 0 140 9 0 0 25 0 1 0 19160477 103714816 24129 1992294400 134512640 136485738 4287509840 18446744073709551615 134948208 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/26927/statm: 25321 24129 208 482 0 24837 0
Current children cumulated CPU time (s) 1.49
Current children cumulated vsize (KiB) 101284

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

[startup+1.9011 s]
/proc/loadavg: 0.93 1.00 0.99 2/107 26928
/proc/meminfo: memFree=1832412/2059040 swapFree=4135652/4192956
[pid=26927] ppid=26925 vsize=98084 CPUtime=1.89
/proc/26927/stat : 26927 (pbct) R 26925 26927 25934 0 -1 4202496 27353 0 0 0 179 10 0 0 25 0 1 0 19160477 100438016 23590 1992294400 134512640 136485738 4287509840 18446744073709551615 135839991 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/26927/statm: 24521 23590 242 482 0 24037 0
Current children cumulated CPU time (s) 1.89
Current children cumulated vsize (KiB) 98084

[startup+2.00111 s]
/proc/loadavg: 0.93 1.00 0.99 2/107 26928
/proc/meminfo: memFree=1832412/2059040 swapFree=4135652/4192956
[pid=26927] ppid=26925 vsize=98084 CPUtime=1.99
/proc/26927/stat : 26927 (pbct) R 26925 26927 25934 0 -1 4202496 27353 0 0 0 189 10 0 0 25 0 1 0 19160477 100438016 23590 1992294400 134512640 136485738 4287509840 18446744073709551615 134720130 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/26927/statm: 24521 23590 242 482 0 24037 0
Current children cumulated CPU time (s) 1.99
Current children cumulated vsize (KiB) 98084

Child status: 0
Real time (s): 2.09872
CPU time (s): 2.09868
CPU user time (s): 1.9807
CPU system time (s): 0.117982
CPU usage (%): 99.9979
Max. virtual memory (cumulated for all children) (KiB): 102008

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.9807
system time used= 0.117982
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 27354
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= 2
involuntary context switches= 4

runsolver used 0.005999 second user time and 0.021996 second system time

The end

Launcher Data

Begin job on node002 at 2010-06-13 15:26:05
IDJOB=2669142
IDBENCH=1498
IDSOLVER=1170
FILE ID=node002/2669142-1276435565
PBS_JOBID= 11173318
Free space on /tmp= 62396 MiB

SOLVER NAME= PB/CT 0.1
BENCH NAME= PB06//final/normalized-PB06/SATUNSAT-SMALLINT/web/www.ps.uni-sb.de/~walser/benchmarks/ppp-problems/normalized-ppp:1-9,16-19.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2669142-1276435565/watcher-2669142-1276435565 -o /tmp/evaluation-result-2669142-1276435565/solver-2669142-1276435565 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2669142-1276435565.opb

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

MD5SUM BENCH= 732cdc3fa8b0bf0f47e882c13d928a6d
RANDOM SEED=1417033941

node002.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.242
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.242
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.36
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1873868 kB
Buffers:         20092 kB
Cached:          88828 kB
SwapCached:       9840 kB
Active:          19968 kB
Inactive:       100892 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1873868 kB
SwapTotal:     4192956 kB
SwapFree:      4135652 kB
Dirty:            3188 kB
Writeback:           0 kB
AnonPages:       10796 kB
Mapped:           9128 kB
Slab:            42348 kB
PageTables:       4020 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   181596 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= 62396 MiB
End job on node002 at 2010-06-13 15:26:07