Trace number 2656915

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 CardUNSAT 0.137978 0.136839

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/
aloul/FPGA_SAT05/normalized-chnl30_31_pb.cnf.cr.opb
MD5SUM4d7adbd65e64509ef53d6e98bf824cab
Bench CategoryDEC-SMALLINT (no optimisation, small integers)
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.090985
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables1860
Total number of constraints122
Number of constraints which are clauses62
Number of constraints which are cardinality constraints (but not clauses)60
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint30
Maximum length of a constraint31
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 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 32
Number of bits of the biggest sum of numbers6
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: Cardinality Constraint Learning
0.00/0.00	c Instance file HOME/instance-2656915-1276326328.opb
0.00/0.00	c File size is 32382 bytes.
0.00/0.00	c Highest Coefficient sum: 32
0.00/0.00	c Parsing was ok!!
0.00/0.00	c Total parsing time: 0.005 s
0.00/0.00	c Var: 1860 Constr: 122 62/60/0 Lit: 3720 Watch. Lit: 1984
0.00/0.00	c Obj. Vars: 0 (0 % of total variables)
0.00/0.05	c Pre-processing Time: 0.048 s
0.00/0.05	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.05	c        0   1860      122     3720   30     1984   18620      0      0 0.05
0.00/0.05	c Switching off lower bounding mode.
0.09/0.13	c      100   1860      253    31632  125     7858   20483    131    806 0.12
0.09/0.13	c Backtracks by Clause: 74
0.09/0.13	c Backtracks by PB constraint: 39
0.09/0.13	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.09/0.13	c    1      117     85     3848      280    36209    158    860 0.14
0.09/0.13	s UNSATISFIABLE
0.09/0.13	c Total time: 0.136 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-2656915-1276326328/watcher-2656915-1276326328 -o /tmp/evaluation-result-2656915-1276326328/solver-2656915-1276326328 -C 1800 -W 2000 -M 1800 bsolo_pb10 -t1800 -l2 HOME/instance-2656915-1276326328.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.91 0.98 0.99 3/106 10150
/proc/meminfo: memFree=1866816/2059040 swapFree=4136620/4192956
[pid=10150] ppid=10148 vsize=11072 CPUtime=0
/proc/10150/stat : 10150 (bsolo_pb10) R 10148 10150 9238 0 -1 4202496 401 0 0 0 0 0 0 0 17 0 1 0 8234392 11337728 311 1992294400 134512640 137138936 4294733952 18446744073709551615 136570369 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/10150/statm: 2768 311 184 642 0 2124 0

[startup+0.093324 s]
/proc/loadavg: 0.91 0.98 0.99 3/106 10150
/proc/meminfo: memFree=1866816/2059040 swapFree=4136620/4192956
[pid=10150] ppid=10148 vsize=11452 CPUtime=0.09
/proc/10150/stat : 10150 (bsolo_pb10) R 10148 10150 9238 0 -1 4202496 507 0 0 0 9 0 0 0 17 0 1 0 8234392 11726848 417 1992294400 134512640 137138936 4294733952 18446744073709551615 136504096 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/10150/statm: 2863 417 192 642 0 2219 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 11452

[startup+0.101326 s]
/proc/loadavg: 0.91 0.98 0.99 3/106 10150
/proc/meminfo: memFree=1866816/2059040 swapFree=4136620/4192956
[pid=10150] ppid=10148 vsize=11452 CPUtime=0.09
/proc/10150/stat : 10150 (bsolo_pb10) R 10148 10150 9238 0 -1 4202496 520 0 0 0 9 0 0 0 17 0 1 0 8234392 11726848 430 1992294400 134512640 137138936 4294733952 18446744073709551615 136297620 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/10150/statm: 2863 430 192 642 0 2219 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 11452

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

Child status: 0
Real time (s): 0.136839
CPU time (s): 0.137978
CPU user time (s): 0.134979
CPU system time (s): 0.002999
CPU usage (%): 100.832
Max. virtual memory (cumulated for all children) (KiB): 11452

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.134979
system time used= 0.002999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 562
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.002999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node012 at 2010-06-12 09:05:28
IDJOB=2656915
IDBENCH=1417
IDSOLVER=1162
FILE ID=node012/2656915-1276326328
PBS_JOBID= 11173159
Free space on /tmp= 62412 MiB

SOLVER NAME= bsolo 3.2 Card
BENCH NAME= PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/FPGA_SAT05/normalized-chnl30_31_pb.cnf.cr.opb
COMMAND LINE= bsolo_pb10 -tTIMEOUT -l2 BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2656915-1276326328/watcher-2656915-1276326328 -o /tmp/evaluation-result-2656915-1276326328/solver-2656915-1276326328 -C 1800 -W 2000 -M 1800  bsolo_pb10 -t1800 -l2 HOME/instance-2656915-1276326328.opb

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

MD5SUM BENCH= 4d7adbd65e64509ef53d6e98bf824cab
RANDOM SEED=2130862367

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


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1867468 kB
Buffers:          6880 kB
Cached:         102480 kB
SwapCached:      16524 kB
Active:          75124 kB
Inactive:        53708 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1867468 kB
SwapTotal:     4192956 kB
SwapFree:      4136620 kB
Dirty:            3948 kB
Writeback:           0 kB
AnonPages:       10808 kB
Mapped:           9168 kB
Slab:            40980 kB
PageTables:       3972 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   181344 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= 62408 MiB
End job on node012 at 2010-06-12 09:05:29