Trace number 2656978

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.095985 0.0957821

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/web/
uclid_pb_benchmarks/normalized-elf.rf7.ucl.opb
MD5SUMe1d25793dfd9fddb01a4cb00dc3ff67b
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.019996
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables1328
Total number of constraints3349
Number of constraints which are clauses3165
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints184
Minimum length of a constraint1
Maximum length of a constraint11
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 33
Number of bits of the biggest number in a constraint 6
Biggest sum of numbers in a constraint 126
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-2656978-1276340921.opb
0.00/0.00	c File size is 98535 bytes.
0.00/0.01	c Highest Coefficient sum: 126
0.00/0.01	c Parsing was ok!!
0.00/0.01	c Total parsing time: 0.015 s
0.00/0.01	c Var: 1328 Constr: 3349 3165/0/184 Lit: 9133 Watch. Lit: 6892
0.00/0.01	c Obj. Vars: 0 (0 % of total variables)
0.03/0.09	c Pre-processing Time: 0.091 s
0.03/0.09	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.03/0.09	c        0    817     2032     6083    2     4328    4122      0      0 0.09
0.03/0.09	c Switching off lower bounding mode.
0.03/0.09	c Backtracks by Clause: 11
0.03/0.09	c Backtracks by PB constraint: 3
0.03/0.09	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.03/0.09	c    0       14     11       87     2056     6152     24    148 0.09
0.03/0.09	s UNSATISFIABLE
0.03/0.09	c Total time: 0.094 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-2656978-1276340921/watcher-2656978-1276340921 -o /tmp/evaluation-result-2656978-1276340921/solver-2656978-1276340921 -C 1800 -W 2000 -M 1800 bsolo_pb10 -t1800 -l2 HOME/instance-2656978-1276340921.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 11652
/proc/meminfo: memFree=1607564/2059040 swapFree=4192956/4192956
[pid=11652] ppid=11650 vsize=11028 CPUtime=0
/proc/11652/stat : 11652 (bsolo_pb10) R 11650 11652 11138 0 -1 4202496 345 0 0 0 0 0 0 0 20 0 1 0 9693747 11292672 264 1992294400 134512640 137138936 4293574640 18446744073709551615 136658918 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/11652/statm: 2757 265 177 642 0 2088 0

[startup+0.0335391 s]
/proc/loadavg: 0.92 0.98 0.99 3/106 11652
/proc/meminfo: memFree=1607564/2059040 swapFree=4192956/4192956
[pid=11652] ppid=11650 vsize=11472 CPUtime=0.03
/proc/11652/stat : 11652 (bsolo_pb10) R 11650 11652 11138 0 -1 4202496 510 0 0 0 3 0 0 0 20 0 1 0 9693747 11747328 404 1992294400 134512640 137138936 4293574640 18446744073709551615 136570369 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/11652/statm: 2868 404 184 642 0 2224 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 11472

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

[startup+0.0335391 s]
/proc/loadavg: 0.92 0.98 0.99 3/106 11652
/proc/meminfo: memFree=1607564/2059040 swapFree=4192956/4192956
[pid=11652] ppid=11650 vsize=11472 CPUtime=0.03
/proc/11652/stat : 11652 (bsolo_pb10) R 11650 11652 11138 0 -1 4202496 510 0 0 0 3 0 0 0 20 0 1 0 9693747 11747328 404 1992294400 134512640 137138936 4293574640 18446744073709551615 136570369 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/11652/statm: 2868 404 184 642 0 2224 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 11472

Child status: 0
Real time (s): 0.0957821
CPU time (s): 0.095985
CPU user time (s): 0.089986
CPU system time (s): 0.005999
CPU usage (%): 100.212
Max. virtual memory (cumulated for all children) (KiB): 11472

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

The end

Launcher Data 

Begin job on node010 at 2010-06-12 13:08:41
IDJOB=2656978
IDBENCH=1490
IDSOLVER=1162
FILE ID=node010/2656978-1276340921
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-elf.rf7.ucl.opb
COMMAND LINE= bsolo_pb10 -tTIMEOUT -l2 BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2656978-1276340921/watcher-2656978-1276340921 -o /tmp/evaluation-result-2656978-1276340921/solver-2656978-1276340921 -C 1800 -W 2000 -M 1800  bsolo_pb10 -t1800 -l2 HOME/instance-2656978-1276340921.opb

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

MD5SUM BENCH= e1d25793dfd9fddb01a4cb00dc3ff67b
RANDOM SEED=567125470

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:       1608092 kB
Buffers:        106896 kB
Cached:         214808 kB
SwapCached:          0 kB
Active:         149952 kB
Inactive:       231008 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1608092 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            4008 kB
Writeback:           8 kB
AnonPages:       59160 kB
Mapped:          15452 kB
Slab:            48260 kB
PageTables:       4024 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   180952 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 13:08:41