Trace number 1884569

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
pbclasp 2009-04-24SAT 0.055991 0.0566069

General information on the benchmark

Name/PURE-SAT/SAT09/
CRAFTED/ramseycube/Q3inK08.opb
MD5SUM5c56a56b4fe6be286b693fbfdefb5f08
Bench CategoryPURE-SAT (instances containing only clauses)
Best result obtained on this benchmarkSAT
Best value of the objective obtained on this benchmark0
Best CPU time to get the best result obtained on this benchmark0.022996
Has Objective FunctionNO
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables28
Total number of constraints1680
Number of constraints which are clauses1680
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 constraint12
Maximum length of a constraint12
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 11
Number of bits of the biggest number in a constraint 4
Biggest sum of numbers in a constraint 23
Number of bits of the biggest sum of numbers5
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data 

0.00/0.01	c no optimisation-statement found. DEC-category assumed.
0.00/0.05	s SATISFIABLE
0.00/0.05	v x1 x2 x3 x4 -x5 -x6 -x7 -x8 -x9 -x10 -x11 -x12 -x13 -x14 -x15 -x16 x17 x18 -x19 -x20 -x21 -x22 x23 x24 -x25 -x26 -x27 -x28

Verifier Data 

OK	0

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1884569-1245259557/watcher-1884569-1245259557 -o /tmp/evaluation-result-1884569-1245259557/solver-1884569-1245259557 -C 1800 -W 2000 -M 1800 perl HOME/pbclasp HOME/instance-1884569-1245259557.opb HOME HOME 

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.92 0.98 0.91 3/64 11864
/proc/meminfo: memFree=1847552/2055920 swapFree=4181884/4192956
[pid=11864] ppid=11862 vsize=3672 CPUtime=0
/proc/11864/stat : 11864 (perl) R 11862 11864 11599 0 -1 4194304 54 0 0 0 0 0 0 0 20 0 1 0 193552567 3760128 38 1992294400 4194304 4206940 548682068784 18446744073709551615 259412522377 0 0 4096 0 0 0 0 17 1 0 0
/proc/11864/statm: 918 40 31 3 0 8 0

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

Child status: 0
Real time (s): 0.0566069
CPU time (s): 0.055991
CPU user time (s): 0.043993
CPU system time (s): 0.011998
CPU usage (%): 98.912
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.043993
system time used= 0.011998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1759
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= 84
involuntary context switches= 6

runsolver used 0.001999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node42 at 2009-06-17 19:25:57
IDJOB=1884569
IDBENCH=71970
IDSOLVER=687
FILE ID=node42/1884569-1245259557
PBS_JOBID= 9372411
Free space on /tmp= 66148 MiB

SOLVER NAME= pbclasp 2009-04-24
BENCH NAME= PB09/normalized-PB09/PURE-SAT/SAT09/CRAFTED/ramseycube/Q3inK08.opb
COMMAND LINE= perl HOME/pbclasp BENCHNAME HOME TMPDIR
CONVERSION SCRIPT= PBconversionToLinear BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1884569-1245259557/watcher-1884569-1245259557 -o /tmp/evaluation-result-1884569-1245259557/solver-1884569-1245259557 -C 1800 -W 2000 -M 1800  perl HOME/pbclasp HOME/instance-1884569-1245259557.opb HOME HOME

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

MD5SUM BENCH= 5c56a56b4fe6be286b693fbfdefb5f08
RANDOM SEED=1361667287

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

/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.214
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.214
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:       1848096 kB
Buffers:         32280 kB
Cached:          94076 kB
SwapCached:       5156 kB
Active:          35944 kB
Inactive:        98560 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1848096 kB
SwapTotal:     4192956 kB
SwapFree:      4181884 kB
Dirty:            4796 kB
Writeback:           0 kB
Mapped:          14336 kB
Slab:            59432 kB
Committed_AS:   198848 kB
PageTables:       1392 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

CONVERSION COMMAND LINE= PBconversionToLinear HOME/instance-1884569-1245259557.opb

Free space on /tmp at the end= 66144 MiB
End job on node42 at 2009-06-17 19:25:58