Trace number 320059

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
KCNFS SMP? (exit code) 0.12498 0.126374

General information on the benchmark

Nameindustrial/grieu/
vmpc_26.cnf
MD5SUM7e9eba7a609bdbcf7c3a7e0f5c07ab04
Bench CategoryINDUST (industrial instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark15.6526
Satisfiable
(Un)Satisfiability was proved
Number of variables676
Number of clauses86424
Sum of the clauses size226590
Maximum clause length26
Minimum clause length2
Number of clauses of size 10
Number of clauses of size 233878
Number of clauses of size 352494
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 552

Solver Data (download as text)

0.00/0.00	
0.00/0.00	c Computed by /tmp/evaluation/320059-1173040400/kcnfs-smp   V. 1.2
0.00/0.00	c reading file ... done
0.09/0.12	c this formula cannot be solved by kcnfs-smp
0.09/0.12

Verifier Data (download as text)

ERROR: Unexpected answer ! (SATISFIABLE/UNSATISFIABLE expected)
Got answer:

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node39/watcher-320059-1173040400 -o ROOT/results/node39/solver-320059-1173040400 -C 1200 -W 2400 -M 1800 --output-limit 1,15 /tmp/evaluation/320059-1173040400/kcnfs-smp /tmp/evaluation/320059-1173040400/instance-320059-1173040400.cnf 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1230 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2400 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.91 0.95 0.90 2/64 13705
/proc/meminfo: memFree=1414488/2055920 swapFree=4184064/4192956
[pid=13705] ppid=13703 vsize=180916 CPUtime=0
/proc/13705/stat : 13705 (kcnfs-smp) R 13703 13705 12416 0 -1 4194304 124 0 0 0 0 0 0 0 18 0 1 0 323995868 185257984 109 18446744073709551615 134512640 135172044 4294956704 18446744073709551615 134820679 0 0 4096 0 0 0 0 17 1 0 0
/proc/13705/statm: 45229 110 48 160 0 45067 0

[startup+0.00847794 s]
/proc/loadavg: 0.91 0.95 0.90 2/64 13705
/proc/meminfo: memFree=1414488/2055920 swapFree=4184064/4192956
[pid=13705] ppid=13703 vsize=181180 CPUtime=0
/proc/13705/stat : 13705 (kcnfs-smp) R 13703 13705 12416 0 -1 4194304 184 0 0 0 0 0 0 0 18 0 1 0 323995868 185528320 169 18446744073709551615 134512640 135172044 4294956704 18446744073709551615 134820679 0 0 4096 0 0 0 0 17 1 0 0
/proc/13705/statm: 45295 170 48 160 0 45133 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 181180

[startup+0.101495 s]
/proc/loadavg: 0.91 0.95 0.90 2/64 13705
/proc/meminfo: memFree=1414488/2055920 swapFree=4184064/4192956
[pid=13705] ppid=13703 vsize=186724 CPUtime=0.09
/proc/13705/stat : 13705 (kcnfs-smp) R 13703 13705 12416 0 -1 4194304 1576 0 0 0 9 0 0 0 18 0 1 0 323995868 191205376 1561 18446744073709551615 134512640 135172044 4294956704 18446744073709551615 134820679 0 0 4096 0 0 0 0 17 1 0 0
/proc/13705/statm: 46681 1561 48 160 0 46519 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 186724

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

Child status: 1
Real time (s): 0.126374
CPU time (s): 0.12498
CPU user time (s): 0.116982
CPU system time (s): 0.007998
CPU usage (%): 98.8968
Max. virtual memory (cumulated for all children) (KiB): 186724

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

The end

Launcher Data (download as text)

Begin job on node39 on Sun Mar  4 20:33:20 UTC 2007

IDJOB= 320059
IDBENCH= 20494
IDSOLVER= 112
FILE ID= node39/320059-1173040400

PBS_JOBID= 4012458

Free space on /tmp= 66541 MiB

SOLVER NAME= KCNFS SMP
BENCH NAME= HOME/pub/bench/SAT07/industrial/grieu/vmpc_26.cnf
COMMAND LINE= /tmp/evaluation/320059-1173040400/kcnfs-smp /tmp/evaluation/320059-1173040400/instance-320059-1173040400.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node39/watcher-320059-1173040400 -o ROOT/results/node39/solver-320059-1173040400 -C 1200 -W 2400 -M 1800 --output-limit 1,15  /tmp/evaluation/320059-1173040400/kcnfs-smp /tmp/evaluation/320059-1173040400/instance-320059-1173040400.cnf            

META MD5SUM SOLVER= 23f87ccf1c743ff5b6146b444e216cd3
MD5SUM BENCH=  7e9eba7a609bdbcf7c3a7e0f5c07ab04

RANDOM SEED= 229368884

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node39.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.285
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.285
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:       1414960 kB
Buffers:         38604 kB
Cached:         528444 kB
SwapCached:       2928 kB
Active:         189904 kB
Inactive:       390172 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1414960 kB
SwapTotal:     4192956 kB
SwapFree:      4184064 kB
Dirty:            4344 kB
Writeback:           0 kB
Mapped:          18920 kB
Slab:            46912 kB
Committed_AS:   755644 kB
PageTables:       1420 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= 66541 MiB

End job on node39 on Sun Mar  4 20:33:20 UTC 2007