Trace number 459371

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-23Signal 0.002998 0.005301

General information on the benchmark

Namenormalized-PB07/PURE-SAT/SAT07/
crafted/spence/medium/s57-100.opb
MD5SUM903ade4eaec463fe861cf04665956f28
Bench CategoryPURE-SAT (instances containing only clauses)
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 benchmark1.48477
Has Objective FunctionNO
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables57
Total number of constraints124
Number of constraints which are clauses124
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint3
Maximum length of a constraint3
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 2
Number of bits of the biggest number in a constraint 2
Biggest sum of numbers in a constraint 5
Number of bits of the biggest sum of numbers3
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/459371-1178653555/instance-459371-1178653555.opb ......

Verifier Data (download as text)

ERROR: no interpretation found !

Conversion Script Data (download as text)

/tmp/evaluation/459371-1178653555/instance-459371-1178653555.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/node33/watcher-459371-1178653555 -o ROOT/results/node33/solver-459371-1178653555 -C 1800 -W 3600 -M 1800 --output-limit 1,15 PBS4_SAT07v2 /tmp/evaluation/459371-1178653555/instance-459371-1178653555.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: 3.08 1.83 1.32 3/77 9009
/proc/meminfo: memFree=1905760/2055920 swapFree=4147924/4192956
[pid=9009] ppid=9007 vsize=0 CPUtime=0
/proc/9009/stat : 9009 (PBS4_SAT07v2) Z 9007 9009 7759 0 -1 4195852 218 0 0 0 0 0 0 0 15 0 1 0 313271045 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 16384 18446744071563351923 0 0 17 1 0 0
/proc/9009/statm: 0 0 0 0 0 0 0

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

Child ended because it received signal 11 (SIGSEGV)
Real time (s): 0.005301
CPU time (s): 0.002998
CPU user time (s): 0.000999
CPU system time (s): 0.001999
CPU usage (%): 56.5554
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.000999
system time used= 0.001999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 218
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.002999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node33 on Tue May  8 19:45:55 UTC 2007

IDJOB= 459371
IDBENCH= 47832
IDSOLVER= 200
FILE ID= node33/459371-1178653555

PBS_JOBID= 5218385

Free space on /tmp= 66562 MiB

SOLVER NAME= PBS4_v2 2007-03-23
BENCH NAME= HOME/pub/bench/PB07/normalized-PB07/PURE-SAT/SAT07/crafted/spence/medium/s57-100.opb
COMMAND LINE= PBS4_SAT07v2 /tmp/evaluation/459371-1178653555/instance-459371-1178653555.opb
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node33/convwatcher-459371-1178653555 -o ROOT/results/node33/conversion-459371-1178653555 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/459371-1178653555/instance-459371-1178653555.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

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

META MD5SUM SOLVER= 18cd8c68a4d3bfb01f29079966475a33
MD5SUM BENCH=  903ade4eaec463fe861cf04665956f28

RANDOM SEED= 625586858

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node33.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.272
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.272
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:       1906232 kB
Buffers:          2004 kB
Cached:          30696 kB
SwapCached:      13676 kB
Active:          80720 kB
Inactive:         4908 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1906232 kB
SwapTotal:     4192956 kB
SwapFree:      4147924 kB
Dirty:            2820 kB
Writeback:           0 kB
Mapped:          60072 kB
Slab:            49360 kB
Committed_AS:  5268688 kB
PageTables:       2064 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 node33 on Tue May  8 19:45:56 UTC 2007