Trace number 2684543

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.043992 0.046773

General information on the benchmark

Name/DEC-SMALLINT-LIN/oliveras/j30/
normalized-j308_1-unsat.opb
MD5SUM995e772deeb96bffa12f22a89aafb659
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.033994
Has Objective FunctionNO
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables2728
Total number of constraints8382
Number of constraints which are clauses8210
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints172
Minimum length of a constraint1
Maximum length of a constraint17
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 32
Number of bits of the biggest number in a constraint 6
Biggest sum of numbers in a constraint 143
Number of bits of the biggest sum of numbers8
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-2684543-1278432543.opb
0.00/0.00	c File size is 231611 bytes.
0.02/0.04	c Highest Coefficient sum: 143
0.02/0.04	c Parsing was ok!!
0.02/0.04	c Total parsing time: 0.038 s
0.02/0.04	c Var: 2728 Constr: 8382 8210/0/172 Lit: 20083 Watch. Lit: 18093
0.02/0.04	c Obj. Vars: 0 (0 % of total variables)
0.02/0.04	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.02/0.04	c    0        0      0        0     8382    20083      0      0 0.04
0.02/0.04	s UNSATISFIABLE
0.02/0.04	c Total time: 0.042 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-2684543-1278432543/watcher-2684543-1278432543 -o /tmp/evaluation-result-2684543-1278432543/solver-2684543-1278432543 -C 1800 -W 2000 -M 1800 bsolo_pb10 -t1800 -l2 HOME/instance-2684543-1278432543.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.00 0.00 0.00 2/106 20951
/proc/meminfo: memFree=1491848/2059040 swapFree=4192956/4192956
[pid=20951] ppid=20949 vsize=11028 CPUtime=0
/proc/20951/stat : 20951 (bsolo_pb10) R 20949 20951 20855 0 -1 4202496 332 0 0 0 0 0 0 0 19 0 1 0 11467957 11292672 251 1992294400 134512640 137138936 4286648352 18446744073709551615 136506715 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/20951/statm: 2757 251 172 642 0 2056 0

[startup+0.0282511 s]
/proc/loadavg: 0.00 0.00 0.00 2/106 20951
/proc/meminfo: memFree=1491848/2059040 swapFree=4192956/4192956
[pid=20951] ppid=20949 vsize=11580 CPUtime=0.02
/proc/20951/stat : 20951 (bsolo_pb10) R 20949 20951 20855 0 -1 4202496 495 0 0 0 2 0 0 0 19 0 1 0 11467957 11857920 414 1992294400 134512640 137138936 4286648352 18446744073709551615 136577166 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/20951/statm: 2895 415 202 642 0 2194 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 11580

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

[startup+0.0282511 s]
/proc/loadavg: 0.00 0.00 0.00 2/106 20951
/proc/meminfo: memFree=1491848/2059040 swapFree=4192956/4192956
[pid=20951] ppid=20949 vsize=11580 CPUtime=0.02
/proc/20951/stat : 20951 (bsolo_pb10) R 20949 20951 20855 0 -1 4202496 495 0 0 0 2 0 0 0 19 0 1 0 11467957 11857920 414 1992294400 134512640 137138936 4286648352 18446744073709551615 136577166 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/20951/statm: 2895 415 202 642 0 2194 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 11580

Child status: 0
Real time (s): 0.046773
CPU time (s): 0.043992
CPU user time (s): 0.041993
CPU system time (s): 0.001999
CPU usage (%): 94.0543
Max. virtual memory (cumulated for all children) (KiB): 11580

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.041993
system time used= 0.001999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 780
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= 2
involuntary context switches= 0

runsolver used 0.005999 second user time and 0.004999 second system time

The end

Launcher Data 

Begin job on node004 at 2010-07-06 18:09:03
IDJOB=2684543
IDBENCH=72932
IDSOLVER=1162
FILE ID=node004/2684543-1278432543
PBS_JOBID= 11233466
Free space on /tmp= 62436 MiB

SOLVER NAME= bsolo 3.2 Card
BENCH NAME= PB10/normalized-PB10/DEC-SMALLINT-LIN/oliveras/j30/normalized-j308_1-unsat.opb
COMMAND LINE= bsolo_pb10 -tTIMEOUT -l2 BENCHNAME
CONVERSION SCRIPT= PBconversionToLinear BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2684543-1278432543/watcher-2684543-1278432543 -o /tmp/evaluation-result-2684543-1278432543/solver-2684543-1278432543 -C 1800 -W 2000 -M 1800  bsolo_pb10 -t1800 -l2 HOME/instance-2684543-1278432543.opb

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

MD5SUM BENCH= 995e772deeb96bffa12f22a89aafb659
RANDOM SEED=490962738

node004.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.219
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.43
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.219
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:       1492500 kB
Buffers:        103700 kB
Cached:         330988 kB
SwapCached:          0 kB
Active:         166992 kB
Inactive:       327424 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1492500 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            4484 kB
Writeback:           0 kB
AnonPages:       59744 kB
Mapped:          14412 kB
Slab:            50344 kB
PageTables:       4172 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   182548 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264948 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

CONVERSION COMMAND LINE= PBconversionToLinear HOME/instance-2684543-1278432543.opb

Free space on /tmp at the end= 62432 MiB
End job on node004 at 2010-07-06 18:09:03