Trace number 2656948

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.198968 0.198213

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/web/
uclid_pb_benchmarks/normalized-ooo.rf6.ucl.opb
MD5SUMebf7767da9a4e6eacd2d0c2c5ada19f1
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.040993
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables1804
Total number of constraints4931
Number of constraints which are clauses4707
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints224
Minimum length of a constraint1
Maximum length of a constraint9
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 19
Number of bits of the biggest number in a constraint 5
Biggest sum of numbers in a constraint 64
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 

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-2656948-1276332699.opb
0.00/0.00	c File size is 142675 bytes.
0.00/0.02	c Highest Coefficient sum: 64
0.00/0.02	c Parsing was ok!!
0.00/0.02	c Total parsing time: 0.023 s
0.00/0.02	c Var: 1804 Constr: 4931 4707/0/224 Lit: 12923 Watch. Lit: 10094
0.00/0.02	c Obj. Vars: 0 (0 % of total variables)
0.09/0.17	c Pre-processing Time: 0.175 s
0.09/0.17	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.09/0.17	c        0   1011     2787     7982    2     5913    4886      0      0 0.17
0.09/0.17	c Switching off lower bounding mode.
0.09/0.19	c Backtracks by Clause: 82
0.09/0.19	c Backtracks by PB constraint: 12
0.09/0.19	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.09/0.19	c    0       94     57      576     2937     8955    150    479 0.20
0.09/0.19	s UNSATISFIABLE
0.09/0.19	c Total time: 0.196 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-2656948-1276332699/watcher-2656948-1276332699 -o /tmp/evaluation-result-2656948-1276332699/solver-2656948-1276332699 -C 1800 -W 2000 -M 1800 bsolo_pb10 -t1800 -l2 HOME/instance-2656948-1276332699.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: 1.00 1.00 1.00 3/106 10165
/proc/meminfo: memFree=1862132/2059040 swapFree=4136452/4192956
[pid=10165] ppid=10163 vsize=11068 CPUtime=0
/proc/10165/stat : 10165 (bsolo_pb10) R 10163 10165 9226 0 -1 4202496 344 0 0 0 0 0 0 0 20 0 1 0 8873975 11333632 263 1992294400 134512640 137138936 4292950784 18446744073709551615 136577166 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/10165/statm: 2767 264 176 642 0 2088 0

[startup+0.0306781 s]
/proc/loadavg: 1.00 1.00 1.00 3/106 10165
/proc/meminfo: memFree=1862132/2059040 swapFree=4136452/4192956
[pid=10165] ppid=10163 vsize=11740 CPUtime=0.02
/proc/10165/stat : 10165 (bsolo_pb10) R 10163 10165 9226 0 -1 4202496 598 0 0 0 2 0 0 0 20 0 1 0 8873975 12021760 482 1992294400 134512640 137138936 4292950784 18446744073709551615 135984545 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/10165/statm: 2935 482 184 642 0 2291 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 11740

[startup+0.100686 s]
/proc/loadavg: 1.00 1.00 1.00 3/106 10165
/proc/meminfo: memFree=1862132/2059040 swapFree=4136452/4192956
[pid=10165] ppid=10163 vsize=11740 CPUtime=0.09
/proc/10165/stat : 10165 (bsolo_pb10) R 10163 10165 9226 0 -1 4202496 604 0 0 0 9 0 0 0 20 0 1 0 8873975 12021760 488 1992294400 134512640 137138936 4292950784 18446744073709551615 134541989 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/10165/statm: 2935 488 184 642 0 2291 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 11740

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

Child status: 0
Real time (s): 0.198213
CPU time (s): 0.198968
CPU user time (s): 0.19097
CPU system time (s): 0.007998
CPU usage (%): 100.381
Max. virtual memory (cumulated for all children) (KiB): 11740

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.19097
system time used= 0.007998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 629
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= 2

runsolver used 0.003999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node001 at 2010-06-12 10:51:39
IDJOB=2656948
IDBENCH=1452
IDSOLVER=1162
FILE ID=node001/2656948-1276332699
PBS_JOBID= 11173164
Free space on /tmp= 62392 MiB

SOLVER NAME= bsolo 3.2 Card
BENCH NAME= PB06//final/normalized-PB06/SATUNSAT-SMALLINT/web/uclid_pb_benchmarks/normalized-ooo.rf6.ucl.opb
COMMAND LINE= bsolo_pb10 -tTIMEOUT -l2 BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2656948-1276332699/watcher-2656948-1276332699 -o /tmp/evaluation-result-2656948-1276332699/solver-2656948-1276332699 -C 1800 -W 2000 -M 1800  bsolo_pb10 -t1800 -l2 HOME/instance-2656948-1276332699.opb

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

MD5SUM BENCH= ebf7767da9a4e6eacd2d0c2c5ada19f1
RANDOM SEED=2060394246

node001.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.202
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.40
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.202
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.46
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1862536 kB
Buffers:         15676 kB
Cached:         109936 kB
SwapCached:      16744 kB
Active:         110460 kB
Inactive:        34792 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1862536 kB
SwapTotal:     4192956 kB
SwapFree:      4136452 kB
Dirty:            4112 kB
Writeback:           8 kB
AnonPages:       10796 kB
Mapped:           9168 kB
Slab:            29524 kB
PageTables:       4060 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   180724 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= 62388 MiB
End job on node001 at 2010-06-12 10:51:40