Trace number 454720

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, and are wall clock time (not CPU 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 NameAnswerObjective functionCPU timeWall clock time
PB-clasp 2007-03-23Wrong UNSAT 0.129979 0.137198

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/
manquinho/mis/normalized-mis_50_10_2.opb
MD5SUM8a07cc5cd91ca4bb254ab7dda2eb6992
Bench CategoryOPT-SMALLINT-NLC (optimisation, small integers, non linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark-12
Best CPU time to get the best result obtained on this benchmark0.18997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function -12
Optimality of the best value was proved YES
Number of variables50
Total number of constraints50
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints50
Minimum length of a constraint10
Maximum length of a constraint19
Number of terms in the objective function 50
Biggest coefficient in the objective function 1
Number of bits for the biggest coefficient in the objective function 1
Sum of the numbers in the objective function 50
Number of bits of the sum of numbers in the objective function 6
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 50
Number of bits of the biggest sum of numbers6
Number of products (including duplicates)616
Sum of products size (including duplicates)1232
Number of different products308
Sum of products size616

Solver Data (download as text)

0.00/0.00	Use of uninitialized value in addition (+) at /tmp/evaluation/454720-1178030194/pbclasp line 60,  line 2.
0.00/0.00	Use of uninitialized value in addition (+) at /tmp/evaluation/454720-1178030194/pbclasp line 63,  line 2.
0.00/0.00	Use of uninitialized value in array element at /tmp/evaluation/454720-1178030194/pbclasp line 65,  line 2.
0.00/0.00	Use of uninitialized value in pattern match (m//) at /tmp/evaluation/454720-1178030194/pbclasp line 77,  line 2.
0.00/0.07	Use of uninitialized value in addition (+) at /tmp/evaluation/454720-1178030194/pbclasp line 87,  line 2.
0.00/0.07	Use of uninitialized value in concatenation (.) or string at /tmp/evaluation/454720-1178030194/pbclasp line 103,  line 2.
0.06/0.13	s UNSATISFIABLE

Verifier Data (download as text)

ERROR: no interpretation found !

Conversion Script Data (download as text)

Linearizing /tmp/evaluation/454720-1178030194/instance-454720-1178030194.opb

Watcher Data (download as text)

runsolver version 3.2.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node24/watcher-454720-1178030194 -o ROOT/results/node24/solver-454720-1178030194 -C 1800 -W 3600 -M 1800 --output-limit 1,15 pbclasp instance-454720-1178030194.opb /tmp/evaluation/454720-1178030194/temp 

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): 3600 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.77 0.92 0.96 3/77 27815
/proc/meminfo: memFree=1849800/2055920 swapFree=4143588/4192956
[pid=27815] ppid=27813 vsize=12268 CPUtime=0
/proc/27815/stat : 27815 (pbclasp) D 27813 27815 19478 0 -1 4194304 350 0 0 0 0 0 0 0 18 0 1 0 250937461 12562432 317 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 237788428901 0 2147483391 4224 0 18446744072099855350 0 0 17 1 0 0
/proc/27815/statm: 3067 317 242 3 0 167 0

[startup+0.0124 s]
/proc/loadavg: 0.77 0.92 0.96 3/77 27815
/proc/meminfo: memFree=1849800/2055920 swapFree=4143588/4192956
[pid=27815] ppid=27813 vsize=12400 CPUtime=0
/proc/27815/stat : 27815 (pbclasp) S 27813 27815 19478 0 -1 4194304 488 0 0 0 0 0 0 0 16 0 1 0 250937461 12697600 440 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 237797159010 0 0 4224 16384 18446744071563648864 0 0 17 1 0 0
/proc/27815/statm: 3100 440 322 3 0 200 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 12400

[startup+0.102408 s]
/proc/loadavg: 0.77 0.92 0.96 3/77 27815
/proc/meminfo: memFree=1849800/2055920 swapFree=4143588/4192956
[pid=27815] ppid=27813 vsize=12400 CPUtime=0.06
/proc/27815/stat : 27815 (pbclasp) S 27813 27815 19478 0 -1 4194304 572 1589 0 0 0 0 5 1 16 0 1 0 250937461 12697600 462 18446744073709551615 4194304 4206940 548682069248 18446744073709551615 237797162900 0 0 4230 16384 18446744071563356171 0 0 17 0 0 0
/proc/27815/statm: 3100 462 342 3 0 200 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 12400

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

Child status: 0
Real time (s): 0.137198
CPU time (s): 0.129979
CPU user time (s): 0.107983
CPU system time (s): 0.021996
CPU usage (%): 94.7382
Max. virtual memory (cumulated for all children) (KiB): 12400

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

runsolver used 0.001999 second user time and 0.006998 second system time

The end

Launcher Data (download as text)

Begin job on node24 on Tue May  1 14:36:34 UTC 2007

IDJOB= 454720
IDBENCH= 48216
IDSOLVER= 158
FILE ID= node24/454720-1178030194

PBS_JOBID= 4728336

Free space on /tmp= 66564 MiB

SOLVER NAME= PB-clasp 2007-03-23
BENCH NAME= HOME/pub/bench/PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/manquinho/mis/normalized-mis_50_10_2.opb
COMMAND LINE= pbclasp instance-454720-1178030194.opb /tmp/evaluation/454720-1178030194/temp
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node24/convwatcher-454720-1178030194 -o ROOT/results/node24/conversion-454720-1178030194 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/454720-1178030194/instance-454720-1178030194.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node24/watcher-454720-1178030194 -o ROOT/results/node24/solver-454720-1178030194 -C 1800 -W 3600 -M 1800 --output-limit 1,15  pbclasp instance-454720-1178030194.opb /tmp/evaluation/454720-1178030194/temp

META MD5SUM SOLVER= 814f1745fa20958d8b352781cfa0403e
MD5SUM BENCH=  8a07cc5cd91ca4bb254ab7dda2eb6992

RANDOM SEED= 528096692

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node24.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.238
cache size	: 2048 KB
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 pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5914.62
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.238
cache size	: 2048 KB
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 pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1850144 kB
Buffers:         53160 kB
Cached:          66120 kB
SwapCached:      17060 kB
Active:         103808 kB
Inactive:        42796 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1850144 kB
SwapTotal:     4192956 kB
SwapFree:      4143588 kB
Dirty:            1280 kB
Writeback:           0 kB
Mapped:          34088 kB
Slab:            44608 kB
Committed_AS:  5265320 kB
PageTables:       1820 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66563 MiB

End job on node24 on Tue May  1 14:36:35 UTC 2007