Trace number 2667744

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.1SAT 0.330949 0.33153

General information on the benchmark

Namenormalized-PB07/SATUNSAT-SMALLINT-NLC/submittedPB07/
manquinho/dbsg/normalized-dbsg_50_10_1_5.opb
MD5SUMd459040c9ffced94019673ccd5842e6c
Bench CategoryDEC-SMALLINT-NLC (no optimisation, small integers, non linear constraints)
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 benchmark0.013997
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables100
Total number of constraints152
Number of constraints which are clauses50
Number of constraints which are cardinality constraints (but not clauses)1
Number of constraints which are nor clauses,nor cardinality constraints101
Minimum length of a constraint2
Maximum length of a constraint100
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 5
Number of bits of the biggest number in a constraint 3
Biggest sum of numbers in a constraint 100
Number of bits of the biggest sum of numbers7
Number of products (including duplicates)1220
Sum of products size (including duplicates)2440
Number of different products610
Sum of products size1220

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.00/0.01	c constraints 712/0 clauses 660/0 units 0
0.00/0.01	c vars 100
0.19/0.24	c 0.232964 21.4102 8 733
0.19/0.24	s SATISFIABLE
0.19/0.24	v -x1 -x2 -x3 -x4 -x5 -x6 -x7 -x8 -x9 -x10 -x11 -x12 -x13 -x14 -x15 -x16 -x17 -x18 -x19 -x20 x21 x22 x23 x24 x25 -x26 -x27 -x28 -x29 -x30 -x31 -x32 -x33 -x34 -x35 -x36 -x37 -x38 -x39 -x40 -x41 -x42 -x43 -x44 -x45 -x46 -x47 -x48 -x49 -x50 -x51 -x52 -x53 -x54 -x55 -x56 -x57 x58 x59 -x60 -x61 x62 -x63 -x64 -x65 x66 -x67 -x68 -x69 -x70 -x71 -x72 -x73 -x74 -x75 -x76 -x77 -x78 -x79 -x80 -x81 -x82 -x83 x84 -x85 -x86 -x87 -x88 -x89 -x90 -x91 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99 -x100

Verifier Data 

OK	0

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2667744-1276679458/watcher-2667744-1276679458 -o /tmp/evaluation-result-2667744-1276679458/solver-2667744-1276679458 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2667744-1276679458.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.92 0.98 1.00 3/106 16628
/proc/meminfo: memFree=1755560/2059040 swapFree=4175448/4192956
[pid=16628] ppid=16626 vsize=2340 CPUtime=0
/proc/16628/stat : 16628 (pbct) R 16626 16628 16046 0 -1 4202496 294 0 0 0 0 0 0 0 25 0 1 0 9239573 2396160 217 1992294400 134512640 136485738 4288234352 18446744073709551615 135850441 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/16628/statm: 585 217 156 482 0 101 0

[startup+0.04256 s]
/proc/loadavg: 0.92 0.98 1.00 3/106 16628
/proc/meminfo: memFree=1755560/2059040 swapFree=4175448/4192956
[pid=16628] ppid=16626 vsize=6164 CPUtime=0.03
/proc/16628/stat : 16628 (pbct) R 16626 16628 16046 0 -1 4202496 1225 0 0 0 3 0 0 0 25 0 1 0 9239573 6311936 1148 1992294400 134512640 136485738 4288234352 18446744073709551615 135850441 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/16628/statm: 1541 1150 196 482 0 1057 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 6164

[startup+0.101566 s]
/proc/loadavg: 0.92 0.98 1.00 3/106 16628
/proc/meminfo: memFree=1755560/2059040 swapFree=4175448/4192956
[pid=16628] ppid=16626 vsize=10344 CPUtime=0.09
/proc/16628/stat : 16628 (pbct) R 16626 16628 16046 0 -1 4202496 2239 0 0 0 9 0 0 0 25 0 1 0 9239573 10592256 2162 1992294400 134512640 136485738 4288234352 18446744073709551615 135850441 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/16628/statm: 2586 2162 196 482 0 2102 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 10344

[startup+0.301587 s]
/proc/loadavg: 0.92 0.98 1.00 3/106 16628
/proc/meminfo: memFree=1755560/2059040 swapFree=4175448/4192956
[pid=16628] ppid=16626 vsize=20280 CPUtime=0.29
/proc/16628/stat : 16628 (pbct) R 16626 16628 16046 0 -1 4202496 5137 0 0 0 28 1 0 0 25 0 1 0 9239573 20766720 4717 1992294400 134512640 136485738 4288234352 18446744073709551615 134720130 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/16628/statm: 5070 4717 246 482 0 4586 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 20280

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

Child status: 0
Real time (s): 0.33153
CPU time (s): 0.330949
CPU user time (s): 0.312952
CPU system time (s): 0.017997
CPU usage (%): 99.8248
Max. virtual memory (cumulated for all children) (KiB): 20280

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.312952
system time used= 0.017997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 5138
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 node083 at 2010-06-16 11:10:59
IDJOB=2667744
IDBENCH=48332
IDSOLVER=1170
FILE ID=node083/2667744-1276679458
PBS_JOBID= 11172557
Free space on /tmp= 62552 MiB

SOLVER NAME= PB/CT 0.1
BENCH NAME= PB07/normalized-PB07/SATUNSAT-SMALLINT-NLC/submittedPB07/manquinho/dbsg/normalized-dbsg_50_10_1_5.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2667744-1276679458/watcher-2667744-1276679458 -o /tmp/evaluation-result-2667744-1276679458/solver-2667744-1276679458 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2667744-1276679458.opb

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

MD5SUM BENCH= d459040c9ffced94019673ccd5842e6c
RANDOM SEED=682917699

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


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1756088 kB
Buffers:         56340 kB
Cached:         113784 kB
SwapCached:      13528 kB
Active:          90932 kB
Inactive:       134956 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1756088 kB
SwapTotal:     4192956 kB
SwapFree:      4175448 kB
Dirty:            2108 kB
Writeback:           8 kB
AnonPages:       42260 kB
Mapped:          14320 kB
Slab:            55360 kB
PageTables:       4080 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   181012 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= 62552 MiB
End job on node083 at 2010-06-16 11:10:59