Trace number 359377

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.16SAT 0.080986 0.0948529

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/
namasivayam/tsp/normalized-t3002.11tsp11.1900581321.opb
MD5SUMe4bbe52e30b63463eee488a367080b13
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.020996
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables231
Total number of constraints2707
Number of constraints which are clauses2684
Number of constraints which are cardinality constraints (but not clauses)22
Number of constraints which are nor clauses,nor cardinality constraints1
Minimum length of a constraint2
Maximum length of a constraint110
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 25
Number of bits of the biggest number in a constraint 5
Biggest sum of numbers in a constraint 627
Number of bits of the biggest sum of numbers10
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.01	c bsolo beta version 3.0.16 - 04/04/2007 : 1458 GMT
0.00/0.01	c Developed by Vasco Manquinho IST/UTL - INESC-ID
0.00/0.01	c type "bsolo -h" for help
0.00/0.01	c Time Limit set via environment variable PBTIMEOUT to 1800
0.00/0.01	c Time Limit set to 1800
0.00/0.01	c Memory Limit set to 1800 MB
0.00/0.01	c Instance file /tmp/evaluation/359377-1176927189/instance-359377-1176927189.opb
0.00/0.01	c File size is 83379 bytes.
0.00/0.03	c Highest Coefficient sum: 627
0.00/0.03	c Parsing was ok!!
0.00/0.03	c Total parsing time: 0.016 s
0.00/0.03	c Var: 231 Constr: 2707 2684/22/1 Lit: 8338 Watch. Lit: 5706
0.00/0.03	c Obj. Vars: 0 (0 % of total variables)
0.00/0.04	c Pre-processing Time: 0.027 s
0.00/0.04	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.04	c        0    231     2586     8096    3     5474    1880      0      0 0.03
0.00/0.04	c Switching off LPR mode.
0.00/0.09	c      101    231     2687    12540    4     5677    2069    101   2805 0.04
0.00/0.09	c      251    231     2837    19763    6     5977    2276    251   5122 0.05
0.00/0.09	v -x1 -x12 -x2 -x13 -x3 -x14 -x4 -x15 -x5 x16 x6 -x17 -x7 -x18 -x8 -x19 -x9 -x20 -x10 -x21 -x11 -x22 -x23 -x24 -x25 -x26 -x27 -x28
0.00/0.09	v -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
0.00/0.09	v -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
0.00/0.09	v -x81 -x82 -x83 -x84 -x85 -x86 -x87 -x88 x89 -x90 -x91 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99 -x100 -x101 -x102 -x103 -x104 -x105
0.00/0.09	v x106 -x107 -x108 -x109 -x110 -x111 -x112 -x113 -x114 -x115 -x116 -x117 -x118 -x119 -x120 x121 x132 -x142 -x152 -x162 -x172
0.00/0.09	v -x182 -x192 -x202 -x212 -x222 -x122 -x143 -x153 -x163 -x173 -x183 -x193 x203 -x213 -x223 -x123 -x133 -x154 -x164 -x174 -x184
0.00/0.09	v x194 -x204 -x214 -x224 -x124 -x134 x144 -x165 -x175 -x185 -x195 -x205 -x215 -x225 -x125 -x135 -x145 -x155 x176 -x186 -x196
0.00/0.09	v -x206 -x216 -x226 -x126 -x136 -x146 -x156 -x166 -x187 -x197 -x207 -x217 x227 x127 -x137 -x147 -x157 -x167 -x177 -x198 -x208
0.00/0.09	v -x218 -x228 -x128 -x138 -x148 -x158 x168 -x178 -x188 -x209 -x219 -x229 -x129 -x139 -x149 -x159 -x169 -x179 -x189 -x199 x220
0.00/0.09	v -x230 -x130 -x140 -x150 x160 -x170 -x180 -x190 -x200 -x210 -x231 -x131 -x141 -x151 -x161 -x171 -x181 x191 -x201 -x211 -x221
0.00/0.09	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.00/0.09	c    2      465    172     1973     3051    28975    465   6118 0.08
0.00/0.09	s SATISFIABLE
0.00/0.09	c Total time: 0.076 s

Verifier Data (download as text)

OK	0

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node42/watcher-359377-1176927189 -o ROOT/results/node42/solver-359377-1176927189 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/359377-1176927189/instance-359377-1176927189.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.85 0.97 0.99 3/77 759
/proc/meminfo: memFree=1871656/2055920 swapFree=4104704/4192956
[pid=759] ppid=757 vsize=3780 CPUtime=0
/proc/759/stat : 759 (bsolo3.0.16) D 757 759 31919 0 -1 4194304 216 0 3 0 0 0 0 0 18 0 1 0 140630795 3870720 187 18446744073709551615 134512640 135841103 4294956640 18446744073709551615 13270704 0 0 4096 0 18446744071563479169 0 0 17 1 0 0
/proc/759/statm: 945 187 160 324 0 14 0

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

Child status: 0
Real time (s): 0.0948529
CPU time (s): 0.080986
CPU user time (s): 0.073988
CPU system time (s): 0.006998
CPU usage (%): 85.3806
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.073988
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= 605
page faults= 4
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 16
involuntary context switches= 0

runsolver used 0.002999 second user time and 0.009998 second system time

The end

Launcher Data (download as text)

Begin job on node42 on Wed Apr 18 20:13:09 UTC 2007

IDJOB= 359377
IDBENCH= 1287
IDSOLVER= 163
FILE ID= node42/359377-1176927189

PBS_JOBID= 4605628

Free space on /tmp= 66445 MiB

SOLVER NAME= bsolo 3.0.16
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/namasivayam/tsp/normalized-t3002.11tsp11.1900581321.opb
COMMAND LINE= bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/359377-1176927189/instance-359377-1176927189.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node42/watcher-359377-1176927189 -o ROOT/results/node42/solver-359377-1176927189 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/359377-1176927189/instance-359377-1176927189.opb            

META MD5SUM SOLVER= b11bf0769a124f73ad50b0fdfcd50482
MD5SUM BENCH=  e4bbe52e30b63463eee488a367080b13

RANDOM SEED= 430217250

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node42.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.277
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	: 5914.62
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.277
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:       1872256 kB
Buffers:         25588 kB
Cached:          76152 kB
SwapCached:      17124 kB
Active:          73468 kB
Inactive:        59544 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1872256 kB
SwapTotal:     4192956 kB
SwapFree:      4104704 kB
Dirty:            4612 kB
Writeback:           0 kB
Mapped:          39472 kB
Slab:            36104 kB
Committed_AS:  2967332 kB
PageTables:       1912 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= 66445 MiB

End job on node42 on Wed Apr 18 20:13:09 UTC 2007