Trace number 2684568

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
borg-pb 10.05.30UNSAT 1.2838 1.52957

General information on the benchmark

Name/DEC-SMALLINT-LIN/oliveras/j30/
normalized-j301_4-unsat.opb
MD5SUMb699e923b3d3f7ecfda0dc818d16dffb
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.043992
Has Objective FunctionNO
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables3844
Total number of constraints11854
Number of constraints which are clauses11610
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints244
Minimum length of a constraint1
Maximum length of a constraint13
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 15
Number of bits of the biggest number in a constraint 4
Biggest sum of numbers in a constraint 99
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.98/1.28	c DEBUG: probabilities of action success (DCM model):
0.98/1.28	c        pb/competition_2010/bsolo_pb10-l1   : 0.2446 0.3106 0.3432 0.4493 0.5331 0.5649 0.6331
0.98/1.28	c        pb/competition_2010/bsolo_pb10-l2   : 0.2220 0.2840 0.3077 0.3819 0.4261 0.4617 0.5493
0.98/1.28	c        pb/competition_2010/bsolo_pb10-l3   : 0.2079 0.2803 0.3237 0.4112 0.4599 0.4979 0.5927
0.98/1.28	c        pb/competition_2010/wbo1.4a         : 0.3403 0.4826 0.5859 0.7308 0.8018 0.8464 0.9114
0.98/1.28	c        pb/competition_2010/wbo1.4b         : 0.2130 0.3046 0.4491 0.6693 0.7698 0.8150 0.8796
0.98/1.28	c        pb/other/clasp-1.3.3                : 0.4078 0.5945 0.6711 0.8373 0.8906 0.9054 0.9586
0.98/1.28	c        pb/other/sat4j-pb-v20090829         : 0.2634 0.4175 0.5149 0.6419 0.7125 0.7655 0.8315
0.98/1.28	c        pb/other/sat4j-pb-v20090829-cutting : 0.2190 0.3670 0.4173 0.5593 0.5959 0.6405 0.7110
1.02/1.38	c DETAIL: running [u'HOME/etc/solvers/other/clasp-1.3.3/clasp-1.3.3-x86-linux', u'--seed=800932178', u'HOME/instance-2684568-1278580292.opb'] for 0:00:10
1.11/1.46	s UNSATISFIABLE

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-2684568-1278580292/watcher-2684568-1278580292 -o /tmp/evaluation-result-2684568-1278580292/solver-2684568-1278580292 -C 1800 -W 2000 -M 1800 solver HOME/instance-2684568-1278580292.opb 2112850730 

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.20 1.05 1.02 3/106 321
/proc/meminfo: memFree=1504408/2059040 swapFree=4165016/4192956
[pid=321] ppid=319 vsize=12400 CPUtime=0
/proc/321/stat : 321 (python) R 319 321 32082 0 -1 4194304 254 0 0 0 0 0 0 0 18 0 1 0 26236422 12697600 62 1992294400 4194304 4196484 140734996860624 18446744073709551615 242166611591 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/321/statm: 3955 64 50 1 0 33 0

[startup+0.0829929 s]
/proc/loadavg: 1.20 1.05 1.02 3/106 321
/proc/meminfo: memFree=1504408/2059040 swapFree=4165016/4192956
[pid=321] ppid=319 vsize=31504 CPUtime=0.06
/proc/321/stat : 321 (python) S 319 321 32082 0 -1 4202496 2231 0 0 0 4 2 0 0 17 0 1 0 26236422 32260096 1247 1992294400 4194304 4196484 140734873529952 18446744073709551615 242171533312 0 2147483391 16781312 2 18446744071699379390 0 0 17 0 0 0 0
/proc/321/statm: 7876 1247 458 1 0 748 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 31504

[startup+0.105588 s]
/proc/loadavg: 1.20 1.05 1.02 3/106 321
/proc/meminfo: memFree=1504408/2059040 swapFree=4165016/4192956
[pid=321] ppid=319 vsize=36072 CPUtime=0.09
/proc/321/stat : 321 (python) R 319 321 32082 0 -1 4202496 2348 0 0 0 6 3 0 0 17 0 1 0 26236422 36937728 1359 1992294400 4194304 4196484 140734873529952 18446744073709551615 47333841950656 0 0 16781312 2 0 0 0 17 0 0 0 0
/proc/321/statm: 9018 1363 466 1 0 856 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 36072

[startup+0.300586 s]
/proc/loadavg: 1.20 1.05 1.02 3/106 321
/proc/meminfo: memFree=1504408/2059040 swapFree=4165016/4192956
[pid=321] ppid=319 vsize=70576 CPUtime=0.2
/proc/321/stat : 321 (python) S 319 321 32082 0 -1 4202496 3908 0 0 0 14 6 0 0 17 0 1 0 26236422 72269824 2788 1992294400 4194304 4196484 140734873529952 18446744073709551615 242171533312 0 2147483391 16781312 2 18446744071699379390 0 0 17 0 0 0 0
/proc/321/statm: 17644 2788 692 1 0 2131 0
Current children cumulated CPU time (s) 0.2
Current children cumulated vsize (KiB) 70576

[startup+0.700582 s]
/proc/loadavg: 1.20 1.05 1.02 3/106 321
/proc/meminfo: memFree=1504408/2059040 swapFree=4165016/4192956
[pid=321] ppid=319 vsize=103528 CPUtime=0.55
/proc/321/stat : 321 (python) R 319 321 32082 0 -1 4202496 5880 930 0 0 36 19 0 0 18 0 1 0 26236422 106012672 4232 1992294400 4194304 4196484 140734873529952 18446744073709551615 47333842591766 0 0 16781312 2 0 0 0 17 0 0 0 0
/proc/321/statm: 25882 4232 1026 1 0 3223 0
Current children cumulated CPU time (s) 0.55
Current children cumulated vsize (KiB) 103528

[startup+1.50057 s]
/proc/loadavg: 1.20 1.05 1.02 3/107 327
/proc/meminfo: memFree=1484188/2059040 swapFree=4165016/4192956
[pid=321] ppid=319 vsize=134092 CPUtime=1.23
/proc/321/stat : 321 (python) R 319 321 32082 0 -1 4202496 13868 2565 0 0 87 33 1 2 18 0 1 0 26236422 137310208 6271 1992294400 4194304 4196484 140734873529952 18446744073709551615 47333842516480 0 0 16781312 0 0 0 0 17 1 0 0 0
/proc/321/statm: 33523 6271 1135 1 0 5160 0
Current children cumulated CPU time (s) 1.23
Current children cumulated vsize (KiB) 134092

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

Child status: 20
Real time (s): 1.52957
CPU time (s): 1.2838
CPU user time (s): 0.91686
CPU system time (s): 0.366944
CPU usage (%): 83.9321
Max. virtual memory (cumulated for all children) (KiB): 134092

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

runsolver used 0.004999 second user time and 0.013997 second system time

The end

Launcher Data 

Begin job on node047 at 2010-07-08 11:11:32
IDJOB=2684568
IDBENCH=73011
IDSOLVER=1178
FILE ID=node047/2684568-1278580292
PBS_JOBID= 11240079
Free space on /tmp= 62492 MiB

SOLVER NAME= borg-pb 10.05.30
BENCH NAME= PB10/normalized-PB10/DEC-SMALLINT-LIN/oliveras/j30/normalized-j301_4-unsat.opb
COMMAND LINE= solver BENCHNAME RANDOMSEED 
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2684568-1278580292/watcher-2684568-1278580292 -o /tmp/evaluation-result-2684568-1278580292/solver-2684568-1278580292 -C 1800 -W 2000 -M 1800  solver HOME/instance-2684568-1278580292.opb 2112850730 

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

MD5SUM BENCH= b699e923b3d3f7ecfda0dc818d16dffb
RANDOM SEED=2112850730

node047.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.248
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.49
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.248
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.53
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1504812 kB
Buffers:         97148 kB
Cached:         329684 kB
SwapCached:       1388 kB
Active:         204284 kB
Inactive:       255928 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1504812 kB
SwapTotal:     4192956 kB
SwapFree:      4165016 kB
Dirty:           21880 kB
Writeback:           0 kB
AnonPages:       31864 kB
Mapped:          13500 kB
Slab:            72060 kB
PageTables:       4076 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   179384 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= 62472 MiB
End job on node047 at 2010-07-08 11:11:34