Trace number 2685242

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
wbo 1.4aUNSAT 0.25296 0.253004

General information on the benchmark

Name/DEC-SMALLINT-LIN/oliveras/j90/
normalized-j9014_1-unsat.opb
MD5SUM55b8067ae8df952812934475200b69c4
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.25296
Has Objective FunctionNO
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables16198
Total number of constraints50975
Number of constraints which are clauses50623
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints352
Minimum length of a constraint1
Maximum length of a constraint90
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 51
Number of bits of the biggest number in a constraint 6
Biggest sum of numbers in a constraint 588
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 wbo 1.4 beta - 20100517
0.00/0.00	c Parsing opb file format. File HOME/instance-2685242-1278440336.opb.
0.00/0.00	c Instance file HOME/instance-2685242-1278440336.opb
0.00/0.00	c File size is 1660095 bytes.
0.19/0.25	c Highest Coefficient sum: 588
0.19/0.25	c ============================[ Problem Statistics ]=============================
0.19/0.25	c |                                                                             |
0.19/0.25	c |  Parsing time:          0.24         s                                      |
0.19/0.25	c |  Number Variables:      16198                                               |
0.19/0.25	c |  Number Clauses:        50623                                               |
0.19/0.25	c |  Number Cardinality:    0                                                   |
0.19/0.25	c |  Number PB Constraints: 352                                                 |
0.19/0.25	c core #1
0.19/0.25	c Memory used           : 7.72 MB
0.19/0.25	c CPU time              : 0.242963 s
0.19/0.25	c 
0.19/0.25	s UNSATISFIABLE
0.19/0.25	c Total CPU time: 0.243962 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-2685242-1278440336/watcher-2685242-1278440336 -o /tmp/evaluation-result-2685242-1278440336/solver-2685242-1278440336 -C 1800 -W 2000 -M 1800 wbo1.4a -file-format=opb -time-limit=1800 HOME/instance-2685242-1278440336.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.08 1.05 1.00 3/106 25007
/proc/meminfo: memFree=1754900/2059040 swapFree=4192956/4192956
[pid=25007] ppid=25005 vsize=4632 CPUtime=0
/proc/25007/stat : 25007 (wbo1.4a) R 25005 25007 24253 0 -1 4202496 369 0 0 0 0 0 0 0 15 0 1 0 12247418 4743168 287 1992294400 134512640 135751879 4290681616 18446744073709551615 134613727 0 0 4096 3 0 0 0 17 1 0 0 0
/proc/25007/statm: 1158 287 139 303 0 447 0

[startup+0.038183 s]
/proc/loadavg: 1.08 1.05 1.00 3/106 25007
/proc/meminfo: memFree=1754900/2059040 swapFree=4192956/4192956
[pid=25007] ppid=25005 vsize=5952 CPUtime=0.03
/proc/25007/stat : 25007 (wbo1.4a) R 25005 25007 24253 0 -1 4202496 735 0 0 0 3 0 0 0 17 0 1 0 12247418 6094848 653 1992294400 134512640 135751879 4290681616 18446744073709551615 134560809 0 0 4096 3 0 0 0 17 1 0 0 0
/proc/25007/statm: 1488 653 186 303 0 777 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 5952

[startup+0.101189 s]
/proc/loadavg: 1.08 1.05 1.00 3/106 25007
/proc/meminfo: memFree=1754900/2059040 swapFree=4192956/4192956
[pid=25007] ppid=25005 vsize=6664 CPUtime=0.09
/proc/25007/stat : 25007 (wbo1.4a) R 25005 25007 24253 0 -1 4202496 1004 0 0 0 9 0 0 0 17 0 1 0 12247418 6823936 922 1992294400 134512640 135751879 4290681616 18446744073709551615 135161858 0 0 4096 3 0 0 0 17 1 0 0 0
/proc/25007/statm: 1707 926 293 303 0 996 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 6664

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

[startup+0.201201 s]
/proc/loadavg: 1.08 1.05 1.00 3/106 25007
/proc/meminfo: memFree=1754900/2059040 swapFree=4192956/4192956
[pid=25007] ppid=25005 vsize=8728 CPUtime=0.19
/proc/25007/stat : 25007 (wbo1.4a) R 25005 25007 24253 0 -1 4202496 1661 0 0 0 19 0 0 0 17 0 1 0 12247418 8937472 1579 1992294400 134512640 135751879 4290681616 18446744073709551615 135225260 0 0 4096 3 0 0 0 17 1 0 0 0
/proc/25007/statm: 2182 1579 462 303 0 1471 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 8728

Child status: 0
Real time (s): 0.253004
CPU time (s): 0.25296
CPU user time (s): 0.243962
CPU system time (s): 0.008998
CPU usage (%): 99.9826
Max. virtual memory (cumulated for all children) (KiB): 8728

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

runsolver used 0.003999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node001 at 2010-07-06 20:18:56
IDJOB=2685242
IDBENCH=75100
IDSOLVER=1160
FILE ID=node001/2685242-1278440336
PBS_JOBID= 11233469
Free space on /tmp= 62472 MiB

SOLVER NAME= wbo 1.4a
BENCH NAME= PB10/normalized-PB10/DEC-SMALLINT-LIN/oliveras/j90/normalized-j9014_1-unsat.opb
COMMAND LINE= wbo1.4a -file-format=opb -time-limit=TIMEOUT BENCHNAME
CONVERSION SCRIPT= PBconversionToLinear BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2685242-1278440336/watcher-2685242-1278440336 -o /tmp/evaluation-result-2685242-1278440336/solver-2685242-1278440336 -C 1800 -W 2000 -M 1800  wbo1.4a -file-format=opb -time-limit=1800 HOME/instance-2685242-1278440336.opb

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

MD5SUM BENCH= 55b8067ae8df952812934475200b69c4
RANDOM SEED=658759208

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.215
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.215
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:       1755676 kB
Buffers:         20176 kB
Cached:         146240 kB
SwapCached:          0 kB
Active:         128684 kB
Inactive:        98104 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1755676 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            6388 kB
Writeback:           0 kB
AnonPages:       60348 kB
Mapped:          14520 kB
Slab:            54788 kB
PageTables:       4160 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   180548 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-2685242-1278440336.opb

Free space on /tmp at the end= 62468 MiB
End job on node001 at 2010-07-06 20:18:56