Trace number 2685324

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.3298 1.5009

General information on the benchmark

Name/DEC-SMALLINT-LIN/oliveras/j90/
normalized-j9010_6-unsat.opb
MD5SUM62425b8c99d21d88f86cd1929c3b9760
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.236963
Has Objective FunctionNO
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables16744
Total number of constraints52975
Number of constraints which are clauses52611
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints364
Minimum length of a constraint1
Maximum length of a constraint72
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 41
Number of bits of the biggest number in a constraint 6
Biggest sum of numbers in a constraint 413
Number of bits of the biggest sum of numbers9
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.21	c DEBUG: probabilities of action success (DCM model):
0.98/1.21	c        pb/competition_2010/bsolo_pb10-l1   : 0.2446 0.3106 0.3432 0.4493 0.5331 0.5649 0.6331
0.98/1.21	c        pb/competition_2010/bsolo_pb10-l2   : 0.2220 0.2840 0.3077 0.3819 0.4261 0.4617 0.5493
0.98/1.21	c        pb/competition_2010/bsolo_pb10-l3   : 0.2079 0.2803 0.3237 0.4112 0.4599 0.4979 0.5927
0.98/1.21	c        pb/competition_2010/wbo1.4a         : 0.3403 0.4826 0.5859 0.7308 0.8018 0.8464 0.9114
0.98/1.21	c        pb/competition_2010/wbo1.4b         : 0.2130 0.3046 0.4491 0.6693 0.7698 0.8150 0.8796
0.98/1.21	c        pb/other/clasp-1.3.3                : 0.4078 0.5945 0.6711 0.8373 0.8906 0.9054 0.9586
0.98/1.21	c        pb/other/sat4j-pb-v20090829         : 0.2634 0.4175 0.5149 0.6419 0.7125 0.7655 0.8315
0.98/1.21	c        pb/other/sat4j-pb-v20090829-cutting : 0.2190 0.3670 0.4173 0.5593 0.5959 0.6405 0.7110
0.98/1.24	c DETAIL: running [u'HOME/etc/solvers/other/clasp-1.3.3/clasp-1.3.3-x86-linux', u'--seed=1138799159', u'HOME/instance-2685324-1278580589.opb'] for 0:00:10
1.17/1.43	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-2685324-1278580589/watcher-2685324-1278580589 -o /tmp/evaluation-result-2685324-1278580589/solver-2685324-1278580589 -C 1800 -W 2000 -M 1800 solver HOME/instance-2685324-1278580589.opb 673479575 

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.93 0.98 0.99 2/106 31954
/proc/meminfo: memFree=1776556/2059040 swapFree=4140568/4192956
[pid=31954] ppid=31952 vsize=16708 CPUtime=0
/proc/31954/stat : 31954 (python) R 31952 31954 31092 0 -1 4202496 724 0 0 0 0 0 0 0 19 0 1 0 26262270 17108992 489 1992294400 4194304 4196484 140735890428256 18446744073709551615 264069381746 0 0 16781312 2 0 0 0 17 1 0 0 0
/proc/31954/statm: 4177 493 272 1 0 273 0

[startup+0.0901421 s]
/proc/loadavg: 0.93 0.98 0.99 2/106 31954
/proc/meminfo: memFree=1776556/2059040 swapFree=4140568/4192956
[pid=31954] ppid=31952 vsize=33564 CPUtime=0.08
/proc/31954/stat : 31954 (python) R 31952 31954 31092 0 -1 4202496 2253 0 0 0 4 4 0 0 17 0 1 0 26262270 34369536 1266 1992294400 4194304 4196484 140737089846624 18446744073709551615 47818265064096 0 0 16781312 2 0 0 0 17 0 0 0 0
/proc/31954/statm: 8391 1266 461 1 0 748 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 33564

[startup+0.100142 s]
/proc/loadavg: 0.93 0.98 0.99 2/106 31954
/proc/meminfo: memFree=1776556/2059040 swapFree=4140568/4192956
[pid=31954] ppid=31952 vsize=36072 CPUtime=0.08
/proc/31954/stat : 31954 (python) R 31952 31954 31092 0 -1 4202496 2337 0 0 0 4 4 0 0 17 0 1 0 26262270 36937728 1345 1992294400 4194304 4196484 140737089846624 18446744073709551615 47818265155520 0 0 16781312 2 0 0 0 17 0 0 0 0
/proc/31954/statm: 9018 1346 466 1 0 856 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 36072

[startup+0.300147 s]
/proc/loadavg: 0.93 0.98 0.99 2/106 31954
/proc/meminfo: memFree=1776556/2059040 swapFree=4140568/4192956
[pid=31954] ppid=31952 vsize=94540 CPUtime=0.27
/proc/31954/stat : 31954 (python) R 31952 31954 31092 0 -1 4202496 4655 0 0 0 16 11 0 0 17 0 1 0 26262270 96808960 3481 1992294400 4194304 4196484 140737089846624 18446744073709551615 264053215237 0 0 16781312 2 0 0 0 17 0 0 0 0
/proc/31954/statm: 23635 3481 1001 1 0 2523 0
Current children cumulated CPU time (s) 0.27
Current children cumulated vsize (KiB) 94540

[startup+0.700157 s]
/proc/loadavg: 0.93 0.98 0.99 2/106 31954
/proc/meminfo: memFree=1776556/2059040 swapFree=4140568/4192956
[pid=31954] ppid=31952 vsize=103528 CPUtime=0.57
/proc/31954/stat : 31954 (python) R 31952 31954 31092 0 -1 4202496 5884 929 0 0 36 21 0 0 18 0 1 0 26262270 106012672 4232 1992294400 4194304 4196484 140737089846624 18446744073709551615 47818265780098 0 0 16781312 2 0 0 0 17 0 0 0 0
/proc/31954/statm: 25882 4232 1026 1 0 3223 0
Current children cumulated CPU time (s) 0.57
Current children cumulated vsize (KiB) 103528

[startup+1.50018 s]
/proc/loadavg: 0.93 0.98 0.99 2/107 31959
/proc/meminfo: memFree=1756708/2059040 swapFree=4140568/4192956
[pid=31954] ppid=31952 vsize=0 CPUtime=1.3
/proc/31954/stat : 31954 (python) R 31952 31954 31092 0 -1 4202500 14932 3013 0 0 91 34 3 2 18 0 1 0 26262270 0 0 1992294400 0 0 0 0 0 0 0 16781312 0 18446744073709551615 0 0 17 0 0 0 0
/proc/31954/statm: 0 0 0 0 0 0 0
Current children cumulated CPU time (s) 1.3
Current children cumulated vsize (KiB) 0

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

Child status: 20
Real time (s): 1.5009
CPU time (s): 1.3298
CPU user time (s): 0.953854
CPU system time (s): 0.375942
CPU usage (%): 88.6001
Max. virtual memory (cumulated for all children) (KiB): 132036

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

runsolver used 0.007998 second user time and 0.012998 second system time

The end

Launcher Data

Begin job on node049 at 2010-07-08 11:16:29
IDJOB=2685324
IDBENCH=75341
IDSOLVER=1178
FILE ID=node049/2685324-1278580589
PBS_JOBID= 11240077
Free space on /tmp= 62480 MiB

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

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

MD5SUM BENCH= 62425b8c99d21d88f86cd1929c3b9760
RANDOM SEED=673479575

node049.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.266
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.266
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:       1776960 kB
Buffers:         22380 kB
Cached:         158684 kB
SwapCached:       6296 kB
Active:          99768 kB
Inactive:        95360 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1776960 kB
SwapTotal:     4192956 kB
SwapFree:      4140568 kB
Dirty:           23472 kB
Writeback:           0 kB
AnonPages:       12264 kB
Mapped:          12500 kB
Slab:            64688 kB
PageTables:       4136 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   182092 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264964 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 62460 MiB
End job on node049 at 2010-07-08 11:16:31