Trace number 458369

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 NameAnswerCPU timeWall clock time
PBS4_v2 2007-03-23UNSAT 0.286955 0.287118

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/web/
uclid_pb_benchmarks/normalized-cache.inv10.ucl.opb
MD5SUM449faf6379a77b0035cc1474243ef90a
Bench CategorySATUNSAT-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.203968
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables8937
Total number of constraints26319
Number of constraints which are clauses26047
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints272
Minimum length of a constraint1
Maximum length of a constraint9
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 17
Number of bits of the biggest number in a constraint 5
Biggest sum of numbers in a constraint 62
Number of bits of the biggest sum of numbers6
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data (download as text)

0.00/0.00	c PBS v4 by Bashar Al-Rawi & Fadi Aloul
0.00/0.00	c Solving /tmp/evaluation/458369-1178622130/instance-458369-1178622130.opb ......
0.19/0.28	c done parsing opb.
0.19/0.28	s UNSATISFIABLE
0.19/0.28	c Total Run Time					0.014998

Verifier Data (download as text)

ERROR: no interpretation found !

Conversion Script Data (download as text)

/tmp/evaluation/458369-1178622130/instance-458369-1178622130.opb is already a linear file

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node70/watcher-458369-1178622130 -o ROOT/results/node70/solver-458369-1178622130 -C 1800 -W 3600 -M 1800 --output-limit 1,15 PBS4_SAT07v2 /tmp/evaluation/458369-1178622130/instance-458369-1178622130.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): 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.92 0.98 0.99 3/64 25169
/proc/meminfo: memFree=1528456/2055920 swapFree=4183880/4192956
[pid=25169] ppid=25167 vsize=2580 CPUtime=0
/proc/25169/stat : 25169 (PBS4_SAT07v2) R 25167 25169 23753 0 -1 4194304 423 0 0 0 0 0 0 0 18 0 1 0 301750373 2641920 405 18446744073709551615 134512640 135410602 4294956672 18446744073709551615 134588504 0 0 4096 16384 0 0 0 17 1 0 0
/proc/25169/statm: 645 405 86 219 0 422 0

[startup+0.055708 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 25169
/proc/meminfo: memFree=1528456/2055920 swapFree=4183880/4192956
[pid=25169] ppid=25167 vsize=2960 CPUtime=0.05
/proc/25169/stat : 25169 (PBS4_SAT07v2) R 25167 25169 23753 0 -1 4194304 544 0 0 0 5 0 0 0 18 0 1 0 301750373 3031040 526 18446744073709551615 134512640 135410602 4294956672 18446744073709551615 134588793 0 0 4096 16384 0 0 0 17 1 0 0
/proc/25169/statm: 740 526 86 219 0 517 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 2960

[startup+0.101712 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 25169
/proc/meminfo: memFree=1528456/2055920 swapFree=4183880/4192956
[pid=25169] ppid=25167 vsize=3408 CPUtime=0.09
/proc/25169/stat : 25169 (PBS4_SAT07v2) R 25167 25169 23753 0 -1 4194304 666 0 0 0 9 0 0 0 18 0 1 0 301750373 3489792 599 18446744073709551615 134512640 135410602 4294956672 18446744073709551615 134588793 0 0 4096 16384 0 0 0 17 1 0 0
/proc/25169/statm: 852 599 86 219 0 629 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3408

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

[startup+0.201723 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 25169
/proc/meminfo: memFree=1528456/2055920 swapFree=4183880/4192956
[pid=25169] ppid=25167 vsize=4596 CPUtime=0.19
/proc/25169/stat : 25169 (PBS4_SAT07v2) R 25167 25169 23753 0 -1 4194304 950 0 0 0 19 0 0 0 18 0 1 0 301750373 4706304 786 18446744073709551615 134512640 135410602 4294956672 18446744073709551615 134784927 0 0 4096 16384 0 0 0 17 1 0 0
/proc/25169/statm: 1149 786 86 219 0 926 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 4596

Child status: 0
Real time (s): 0.287118
CPU time (s): 0.286955
CPU user time (s): 0.276957
CPU system time (s): 0.009998
CPU usage (%): 99.9432
Max. virtual memory (cumulated for all children) (KiB): 4596

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

runsolver used 0.001999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node70 on Tue May  8 11:02:10 UTC 2007

IDJOB= 458369
IDBENCH= 1446
IDSOLVER= 200
FILE ID= node70/458369-1178622130

PBS_JOBID= 5218248

Free space on /tmp= 66562 MiB

SOLVER NAME= PBS4_v2 2007-03-23
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/SATUNSAT-SMALLINT/web/uclid_pb_benchmarks/normalized-cache.inv10.ucl.opb
COMMAND LINE= PBS4_SAT07v2 /tmp/evaluation/458369-1178622130/instance-458369-1178622130.opb
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node70/convwatcher-458369-1178622130 -o ROOT/results/node70/conversion-458369-1178622130 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/458369-1178622130/instance-458369-1178622130.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node70/watcher-458369-1178622130 -o ROOT/results/node70/solver-458369-1178622130 -C 1800 -W 3600 -M 1800 --output-limit 1,15  PBS4_SAT07v2 /tmp/evaluation/458369-1178622130/instance-458369-1178622130.opb

META MD5SUM SOLVER= 18cd8c68a4d3bfb01f29079966475a33
MD5SUM BENCH=  449faf6379a77b0035cc1474243ef90a

RANDOM SEED= 283699853

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node70.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.218
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.218
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:       1528800 kB
Buffers:         33712 kB
Cached:         390476 kB
SwapCached:       2988 kB
Active:         161524 kB
Inactive:       275240 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1528800 kB
SwapTotal:     4192956 kB
SwapFree:      4183880 kB
Dirty:            3168 kB
Writeback:           0 kB
Mapped:          18684 kB
Slab:            76392 kB
Committed_AS:  7591712 kB
PageTables:       1404 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= 66562 MiB

End job on node70 on Tue May  8 11:02:11 UTC 2007