Trace number 2685160

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
bsolo 3.2 ClUNSAT 0.242962 0.24283

General information on the benchmark

Name/DEC-SMALLINT-LIN/oliveras/j90/
normalized-j9012_2-unsat.opb
MD5SUMe779a123dad7c0bfc06fe135207f182b
Bench CategoryDEC-SMALLINT-LIN (no optimisation, small integers, linear constraints)
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.18997
Has Objective FunctionNO
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables12922
Total number of constraints40512
Number of constraints which are clauses40232
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints280
Minimum length of a constraint1
Maximum length of a constraint69
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 102
Number of bits of the biggest number in a constraint 7
Biggest sum of numbers in a constraint 504
Number of bits of the biggest sum of numbers9
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 bsolo beta version 3.2 - 23/05/2010 : 1630 GMT
0.00/0.00	c Developed by Vasco Manquinho and José Santos IST/UTL - INESC-ID
0.00/0.00	c type "bsolo -h" for help
0.00/0.00	c Time Limit set via environment variable PBTIMEOUT to 1800
0.00/0.00	c Time Limit set to 1800
0.00/0.00	c Learning Strategy: Clause Learning
0.00/0.00	c Instance file HOME/instance-2685160-1278439886.opb
0.00/0.00	c File size is 1242684 bytes.
0.19/0.21	c Highest Coefficient sum: 504
0.19/0.21	c Parsing was ok!!
0.19/0.21	c Total parsing time: 0.21 s
0.19/0.23	c Var: 12922 Constr: 40512 40232/0/280 Lit: 104895 Watch. Lit: 91198
0.19/0.23	c Obj. Vars: 0 (0 % of total variables)
0.19/0.24	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.19/0.24	c    0        0      0        0    40512   104895      0      0 0.24
0.19/0.24	s UNSATISFIABLE
0.19/0.24	c Total time: 0.24 s

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-2685160-1278439886/watcher-2685160-1278439886 -o /tmp/evaluation-result-2685160-1278439886/solver-2685160-1278439886 -C 1800 -W 2000 -M 1800 bsolo_pb10 -t1800 -l1 HOME/instance-2685160-1278439886.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.86 0.97 0.97 3/106 20983
/proc/meminfo: memFree=1392760/2059040 swapFree=4192956/4192956
[pid=20983] ppid=20981 vsize=12148 CPUtime=0
/proc/20983/stat : 20983 (bsolo_pb10) R 20981 20983 19731 0 -1 4202496 367 0 0 0 0 0 0 0 15 0 1 0 12199238 12439552 285 1992294400 134512640 137138936 4288958336 18446744073709551615 136506715 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/20983/statm: 3037 285 177 642 0 2089 0

[startup+0.0721509 s]
/proc/loadavg: 0.86 0.97 0.97 3/106 20983
/proc/meminfo: memFree=1392760/2059040 swapFree=4192956/4192956
[pid=20983] ppid=20981 vsize=13964 CPUtime=0.06
/proc/20983/stat : 20983 (bsolo_pb10) R 20981 20983 19731 0 -1 4202496 923 0 0 0 6 0 0 0 18 0 1 0 12199238 14299136 841 1992294400 134512640 137138936 4288958336 18446744073709551615 136525315 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/20983/statm: 3491 841 273 642 0 2543 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 13964

[startup+0.101151 s]
/proc/loadavg: 0.86 0.97 0.97 3/106 20983
/proc/meminfo: memFree=1392760/2059040 swapFree=4192956/4192956
[pid=20983] ppid=20981 vsize=14788 CPUtime=0.09
/proc/20983/stat : 20983 (bsolo_pb10) R 20981 20983 19731 0 -1 4202496 1145 0 0 0 9 0 0 0 18 0 1 0 12199238 15142912 1063 1992294400 134512640 137138936 4288958336 18446744073709551615 134531572 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/20983/statm: 3697 1064 315 642 0 2749 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 14788

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

[startup+0.201159 s]
/proc/loadavg: 0.86 0.97 0.97 3/106 20983
/proc/meminfo: memFree=1392760/2059040 swapFree=4192956/4192956
[pid=20983] ppid=20981 vsize=16896 CPUtime=0.19
/proc/20983/stat : 20983 (bsolo_pb10) R 20981 20983 19731 0 -1 4202496 1833 0 0 0 19 0 0 0 18 0 1 0 12199238 17301504 1751 1992294400 134512640 137138936 4288958336 18446744073709551615 134599769 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/20983/statm: 4224 1751 457 642 0 3276 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 16896

Child status: 0
Real time (s): 0.24283
CPU time (s): 0.242962
CPU user time (s): 0.227965
CPU system time (s): 0.014997
CPU usage (%): 100.054
Max. virtual memory (cumulated for all children) (KiB): 16896

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.227965
system time used= 0.014997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2734
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.008998 second system time

The end

Launcher Data 

Begin job on node031 at 2010-07-06 20:11:26
IDJOB=2685160
IDBENCH=74866
IDSOLVER=1163
FILE ID=node031/2685160-1278439886
PBS_JOBID= 11233447
Free space on /tmp= 62560 MiB

SOLVER NAME= bsolo 3.2 Cl
BENCH NAME= PB10/normalized-PB10/DEC-SMALLINT-LIN/oliveras/j90/normalized-j9012_2-unsat.opb
COMMAND LINE= bsolo_pb10 -tTIMEOUT -l1 BENCHNAME
CONVERSION SCRIPT= PBconversionToLinear BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2685160-1278439886/watcher-2685160-1278439886 -o /tmp/evaluation-result-2685160-1278439886/solver-2685160-1278439886 -C 1800 -W 2000 -M 1800  bsolo_pb10 -t1800 -l1 HOME/instance-2685160-1278439886.opb

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

MD5SUM BENCH= e779a123dad7c0bfc06fe135207f182b
RANDOM SEED=694092573

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


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1393536 kB
Buffers:        108200 kB
Cached:         416284 kB
SwapCached:          0 kB
Active:         252404 kB
Inactive:       332668 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1393536 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            6120 kB
Writeback:           0 kB
AnonPages:       60432 kB
Mapped:          14548 kB
Slab:            58360 kB
PageTables:       4120 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   180012 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264964 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

CONVERSION COMMAND LINE= PBconversionToLinear HOME/instance-2685160-1278439886.opb

Free space on /tmp at the end= 62556 MiB
End job on node031 at 2010-07-06 20:11:27