Trace number 357671

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
Pueblo 1.4SAT 0.955853 0.958188

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/
prestwich/armies/normalized-army8.9bt.opb
MD5SUM41a419a7ef36b132b62f2564e794a725
Bench CategorySATUNSAT-SMALLINT-LIN (no optimisation, small integers, 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.048991
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables220
Total number of constraints470
Number of constraints which are clauses333
Number of constraints which are cardinality constraints (but not clauses)2
Number of constraints which are nor clauses,nor cardinality constraints135
Minimum length of a constraint1
Maximum length of a constraint64
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 9
Number of bits of the biggest number in a constraint 4
Biggest sum of numbers in a constraint 73
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 (download as text)

0.00/0.00	c Pueblo version 1.4 (September 2005)
0.00/0.00	c Developed @ University of Michigan, Ann Arbor, MI
0.00/0.00	c  by Hossein Sheini
0.00/0.01	c starting to Solve
0.00/0.01	c #variables read: 220 - #constraints read: 469
0.89/0.95	c total time              : 0.95 s
0.89/0.95	s SATISFIABLE
0.89/0.95	v x1 -x3 -x5 x7 x9 x11 -x13 -x15 -x17 -x19 -x21 -x23 x25 x27 -x29 -x31 x33 -x35 -x37 -x39 -x41 -x43 -x45 -x47 x49 -x51 -x53 x55 -x57
0.89/0.95	v -x59 -x61 -x63 -x65 -x67 -x69 -x71 -x73 -x75 -x77 -x79 -x81 -x83 -x85 -x87 -x89 -x91 -x93 -x95 -x97 -x99 -x101 -x103 -x105 -x107
0.89/0.95	v -x109 -x111 -x113 -x115 -x117 -x119 -x121 -x123 -x125 -x127 -x2 -x4 -x6 -x8 -x10 -x12 -x14 -x16 -x18 -x20 -x22 -x24 -x26 -x28
0.89/0.95	v -x30 -x32 -x34 -x36 -x38 -x40 -x42 -x44 -x46 -x48 -x50 -x52 -x54 -x56 -x58 -x60 -x62 -x64 -x66 -x68 -x70 -x72 -x74 -x76 x78 -x80
0.89/0.95	v -x82 -x84 -x86 -x88 -x90 -x92 x94 x96 -x98 x100 x102 -x104 -x106 -x108 -x110 x112 -x114 x116 x118 -x120 -x122 -x124 x126 -x128
0.89/0.95	v x130 -x129 x132 -x131 x134 -x133 x136 -x135 -x138 x137 -x140 x139 -x142 x141 -x144 x143 x146 -x145 -x148 x147 -x150 x149 x152
0.89/0.95	v -x151 x154 -x153 x156 -x155 -x158 x157 -x160 x159 x162 -x161 -x164 x163 x166 -x165 x168 -x167 -x170 x169 -x172 x171 -x174 x173
0.89/0.95	v -x176 -x175 x178 -x177 -x180 -x179 x182 -x181 x184 -x183 x186 -x185 x188 -x187 x190 -x189 -x192 x191 -x194 x193 -x196 x195
0.89/0.95	v -x198 x197 -x200 x199 -x202 x201 -x204 x203 -x206 -x205 -x208 -x207 -x210 -x209 x212 -x211 x214 -x213 x216 -x215 -x218 x217
0.89/0.95	v -x220 x219

Verifier Data (download as text)

OK	0

Conversion Script Data (download as text)

/tmp/evaluation/357671-1176831411/instance-357671-1176831411.opb is already a linear file

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node4/watcher-357671-1176831411 -o ROOT/results/node4/solver-357671-1176831411 -C 1800 -W 3600 -M 1800 --output-limit 1,15 Pueblo /tmp/evaluation/357671-1176831411/instance-357671-1176831411.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: 0.86 0.98 0.99 3/77 24403
/proc/meminfo: memFree=1382168/2055920 swapFree=4153892/4192956
[pid=24403] ppid=24401 vsize=2552 CPUtime=0
/proc/24403/stat : 24403 (Pueblo) R 24401 24403 23396 0 -1 4194304 264 0 0 0 0 0 0 0 18 0 1 0 159178828 2613248 234 18446744073709551615 134512640 134579096 4294956672 18446744073709551615 10756108 0 0 4096 0 0 0 0 17 1 0 0
/proc/24403/statm: 638 234 199 16 0 77 0

[startup+0.00863494 s]
/proc/loadavg: 0.86 0.98 0.99 3/77 24403
/proc/meminfo: memFree=1382168/2055920 swapFree=4153892/4192956
[pid=24403] ppid=24401 vsize=2552 CPUtime=0
/proc/24403/stat : 24403 (Pueblo) R 24401 24403 23396 0 -1 4194304 275 0 0 0 0 0 0 0 18 0 1 0 159178828 2613248 245 18446744073709551615 134512640 134579096 4294956672 18446744073709551615 11054807 0 0 4096 0 0 0 0 17 1 0 0
/proc/24403/statm: 638 245 199 16 0 77 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 2552

[startup+0.101644 s]
/proc/loadavg: 0.86 0.98 0.99 3/77 24403
/proc/meminfo: memFree=1382168/2055920 swapFree=4153892/4192956
[pid=24403] ppid=24401 vsize=2816 CPUtime=0.09
/proc/24403/stat : 24403 (Pueblo) R 24401 24403 23396 0 -1 4194304 348 0 0 0 9 0 0 0 18 0 1 0 159178828 2883584 318 18446744073709551615 134512640 134579096 4294956672 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/24403/statm: 704 318 205 16 0 143 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2816

[startup+0.301663 s]
/proc/loadavg: 0.86 0.98 0.99 3/77 24403
/proc/meminfo: memFree=1382168/2055920 swapFree=4153892/4192956
[pid=24403] ppid=24401 vsize=2944 CPUtime=0.29
/proc/24403/stat : 24403 (Pueblo) R 24401 24403 23396 0 -1 4194304 368 0 0 0 29 0 0 0 19 0 1 0 159178828 3014656 338 18446744073709551615 134512640 134579096 4294956672 18446744073709551615 134556363 0 0 4096 0 0 0 0 17 1 0 0
/proc/24403/statm: 736 338 205 16 0 175 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 2944

[startup+0.702701 s]
/proc/loadavg: 0.86 0.98 0.99 3/77 24403
/proc/meminfo: memFree=1382168/2055920 swapFree=4153892/4192956
[pid=24403] ppid=24401 vsize=2944 CPUtime=0.69
/proc/24403/stat : 24403 (Pueblo) R 24401 24403 23396 0 -1 4194304 377 0 0 0 69 0 0 0 22 0 1 0 159178828 3014656 347 18446744073709551615 134512640 134579096 4294956672 18446744073709551615 134527718 0 0 4096 0 0 0 0 17 1 0 0
/proc/24403/statm: 736 347 205 16 0 175 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 2944

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

[startup+0.90272 s]
/proc/loadavg: 0.86 0.98 0.99 3/77 24403
/proc/meminfo: memFree=1382168/2055920 swapFree=4153892/4192956
[pid=24403] ppid=24401 vsize=2944 CPUtime=0.89
/proc/24403/stat : 24403 (Pueblo) R 24401 24403 23396 0 -1 4194304 381 0 0 0 89 0 0 0 24 0 1 0 159178828 3014656 351 18446744073709551615 134512640 134579096 4294956672 18446744073709551615 134527818 0 0 4096 0 0 0 0 17 1 0 0
/proc/24403/statm: 736 351 205 16 0 175 0
Current children cumulated CPU time (s) 0.89
Current children cumulated vsize (KiB) 2944

Child status: 10
Real time (s): 0.958188
CPU time (s): 0.955853
CPU user time (s): 0.953854
CPU system time (s): 0.001999
CPU usage (%): 99.7563
Max. virtual memory (cumulated for all children) (KiB): 2944

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.953854
system time used= 0.001999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 389
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= 13
involuntary context switches= 5

runsolver used 0.004999 second user time and 0.007998 second system time

The end

Launcher Data (download as text)

Begin job on node4 on Tue Apr 17 17:36:51 UTC 2007

IDJOB= 357671
IDBENCH= 1159
IDSOLVER= 165
FILE ID= node4/357671-1176831411

PBS_JOBID= 4586353

Free space on /tmp= 66495 MiB

SOLVER NAME= Pueblo 1.4
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/prestwich/armies/normalized-army8.9bt.opb
COMMAND LINE= Pueblo /tmp/evaluation/357671-1176831411/instance-357671-1176831411.opb
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node4/convwatcher-357671-1176831411 -o ROOT/results/node4/conversion-357671-1176831411 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/357671-1176831411/instance-357671-1176831411.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node4/watcher-357671-1176831411 -o ROOT/results/node4/solver-357671-1176831411 -C 1800 -W 3600 -M 1800 --output-limit 1,15  Pueblo /tmp/evaluation/357671-1176831411/instance-357671-1176831411.opb

META MD5SUM SOLVER= 9ebec3e8d890fdeefad01654ad9b68b7
MD5SUM BENCH=  41a419a7ef36b132b62f2564e794a725

RANDOM SEED= 845251636

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node4.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.218
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.218
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:       1382576 kB
Buffers:         38480 kB
Cached:         557996 kB
SwapCached:       2672 kB
Active:         394576 kB
Inactive:       225816 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1382576 kB
SwapTotal:     4192956 kB
SwapFree:      4153892 kB
Dirty:            2508 kB
Writeback:           0 kB
Mapped:          31228 kB
Slab:            38460 kB
Committed_AS:  5221704 kB
PageTables:       1820 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= 66495 MiB

End job on node4 on Tue Apr 17 17:36:52 UTC 2007