Trace number 2656970

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.981849 0.981817

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/web/
uclid_pb_benchmarks/normalized-22s.smv.opb
MD5SUM3fb2d144eb047d6ea626acdee43b1069
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.152976
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables5985
Total number of constraints15365
Number of constraints which are clauses14013
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints1352
Minimum length of a constraint1
Maximum length of a constraint15
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 165
Number of bits of the biggest number in a constraint 8
Biggest sum of numbers in a constraint 546
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 

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-2656970-1276336619.opb
0.00/0.00	c File size is 572647 bytes.
0.00/0.10	c Highest Coefficient sum: 546
0.00/0.10	c Parsing was ok!!
0.00/0.10	c Total parsing time: 0.101 s
0.10/0.11	c Var: 5985 Constr: 15365 14013/0/1352 Lit: 52791 Watch. Lit: 32147
0.10/0.11	c Obj. Vars: 0 (0 % of total variables)
0.89/0.98	c CONFLICT DETECTED at PROBING!!!
0.89/0.98	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.89/0.98	c    0        0      0        0    15365    52791      0      0 0.98
0.89/0.98	s UNSATISFIABLE
0.89/0.98	c Total time: 0.979 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-2656970-1276336619/watcher-2656970-1276336619 -o /tmp/evaluation-result-2656970-1276336619/solver-2656970-1276336619 -C 1800 -W 2000 -M 1800 bsolo_pb10 -t1800 -l2 HOME/instance-2656970-1276336619.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.92 0.98 0.99 3/106 11190
/proc/meminfo: memFree=1615004/2059040 swapFree=4192956/4192956
[pid=11190] ppid=11188 vsize=11488 CPUtime=0
/proc/11190/stat : 11190 (bsolo_pb10) R 11188 11190 11138 0 -1 4202496 342 0 0 0 0 0 0 0 20 0 1 0 9263534 11763712 261 1992294400 134512640 137138936 4288530912 18446744073709551615 136506715 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/11190/statm: 2872 261 176 642 0 2088 0

[startup+0.103676 s]
/proc/loadavg: 0.92 0.98 0.99 3/106 11190
/proc/meminfo: memFree=1615004/2059040 swapFree=4192956/4192956
[pid=11190] ppid=11188 vsize=12852 CPUtime=0.1
/proc/11190/stat : 11190 (bsolo_pb10) R 11188 11190 11138 0 -1 4202496 966 0 0 0 10 0 0 0 20 0 1 0 9263534 13160448 745 1992294400 134512640 137138936 4288530912 18446744073709551615 136500283 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/11190/statm: 3213 745 180 642 0 2569 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 12852

[startup+0.201695 s]
/proc/loadavg: 0.92 0.98 0.99 3/106 11190
/proc/meminfo: memFree=1615004/2059040 swapFree=4192956/4192956
[pid=11190] ppid=11188 vsize=14340 CPUtime=0.19
/proc/11190/stat : 11190 (bsolo_pb10) R 11188 11190 11138 0 -1 4202496 1340 0 0 0 19 0 0 0 20 0 1 0 9263534 14684160 1119 1992294400 134512640 137138936 4288530912 18446744073709551615 134542187 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/11190/statm: 3585 1119 184 642 0 2941 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 14340

[startup+0.301715 s]
/proc/loadavg: 0.92 0.98 0.99 3/106 11190
/proc/meminfo: memFree=1615004/2059040 swapFree=4192956/4192956
[pid=11190] ppid=11188 vsize=14340 CPUtime=0.29
/proc/11190/stat : 11190 (bsolo_pb10) R 11188 11190 11138 0 -1 4202496 1347 0 0 0 29 0 0 0 20 0 1 0 9263534 14684160 1126 1992294400 134512640 137138936 4288530912 18446744073709551615 134542770 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/11190/statm: 3585 1126 184 642 0 2941 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 14340

[startup+0.701801 s]
/proc/loadavg: 0.92 0.98 0.99 3/106 11190
/proc/meminfo: memFree=1615004/2059040 swapFree=4192956/4192956
[pid=11190] ppid=11188 vsize=14340 CPUtime=0.69
/proc/11190/stat : 11190 (bsolo_pb10) R 11188 11190 11138 0 -1 4202496 1371 0 0 0 69 0 0 0 21 0 1 0 9263534 14684160 1150 1992294400 134512640 137138936 4288530912 18446744073709551615 134542805 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/11190/statm: 3585 1150 184 642 0 2941 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 14340

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

[startup+0.800823 s]
/proc/loadavg: 0.92 0.98 0.99 3/106 11190
/proc/meminfo: memFree=1615004/2059040 swapFree=4192956/4192956
[pid=11190] ppid=11188 vsize=14340 CPUtime=0.79
/proc/11190/stat : 11190 (bsolo_pb10) R 11188 11190 11138 0 -1 4202496 1371 0 0 0 79 0 0 0 21 0 1 0 9263534 14684160 1150 1992294400 134512640 137138936 4288530912 18446744073709551615 134543180 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/11190/statm: 3585 1150 184 642 0 2941 0
Current children cumulated CPU time (s) 0.79
Current children cumulated vsize (KiB) 14340

[startup+0.900844 s]
/proc/loadavg: 0.92 0.98 0.99 3/106 11190
/proc/meminfo: memFree=1615004/2059040 swapFree=4192956/4192956
[pid=11190] ppid=11188 vsize=14472 CPUtime=0.89
/proc/11190/stat : 11190 (bsolo_pb10) R 11188 11190 11138 0 -1 4202496 1377 0 0 0 89 0 0 0 21 0 1 0 9263534 14819328 1156 1992294400 134512640 137138936 4288530912 18446744073709551615 136521014 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/11190/statm: 3618 1156 184 642 0 2974 0
Current children cumulated CPU time (s) 0.89
Current children cumulated vsize (KiB) 14472

Child status: 0
Real time (s): 0.981817
CPU time (s): 0.981849
CPU user time (s): 0.973851
CPU system time (s): 0.007998
CPU usage (%): 100.003
Max. virtual memory (cumulated for all children) (KiB): 14472

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.973851
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= 1390
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= 12

runsolver used 0.005999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node010 at 2010-06-12 11:56:59
IDJOB=2656970
IDBENCH=1477
IDSOLVER=1162
FILE ID=node010/2656970-1276336619
PBS_JOBID= 11173181
Free space on /tmp= 62500 MiB

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

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

MD5SUM BENCH= 3fb2d144eb047d6ea626acdee43b1069
RANDOM SEED=810201577

node010.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.267
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.53
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.267
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:       1615532 kB
Buffers:        103152 kB
Cached:         211496 kB
SwapCached:          0 kB
Active:         149872 kB
Inactive:       223924 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1615532 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            4652 kB
Writeback:           8 kB
AnonPages:       59032 kB
Mapped:          15404 kB
Slab:            48036 kB
PageTables:       4128 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   182624 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= 62496 MiB
End job on node010 at 2010-06-12 11:57:00