Trace number 319691

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 2006? (exit code) 0.115981 0.115346

General information on the benchmark

Nameindustrial/grieu/
vmpc_25.cnf
MD5SUMc5b44b10975f50cd32d40650a6a22d18
Bench CategoryINDUST (industrial instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark2.99054
Satisfiable
(Un)Satisfiability was proved
Number of variables625
Number of clauses76775
Sum of the clauses size201350
Maximum clause length25
Minimum clause length2
Number of clauses of size 10
Number of clauses of size 230075
Number of clauses of size 346650
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 550

Solver Data (download as text)

0.00/0.00	
0.00/0.00	c Computed by /tmp/evaluation/319691-1173034894/kcnfs-2006   V. 1.2
0.00/0.00	c reading file ... done
0.09/0.11	c this formula cannot been solved by kcnfs
0.09/0.11

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/node12/watcher-319691-1173034894 -o ROOT/results/node12/solver-319691-1173034894 -C 1200 -W 2400 -M 1800 --output-limit 1,15 /tmp/evaluation/319691-1173034894/kcnfs-2006 /tmp/evaluation/319691-1173034894/instance-319691-1173034894.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.92 0.98 0.94 3/83 5094
/proc/meminfo: memFree=816864/2055920 swapFree=4156596/4192956
[pid=5094] ppid=5092 vsize=180908 CPUtime=0
/proc/5094/stat : 5094 (kcnfs-2006) R 5092 5094 4282 0 -1 4194304 134 0 0 0 0 0 0 0 18 0 1 0 323443866 185249792 119 18446744073709551615 134512640 135163436 4294956704 18446744073709551615 134811879 0 0 4096 0 0 0 0 17 1 0 0
/proc/5094/statm: 45227 120 47 158 0 45067 0

[startup+0.105198 s]
/proc/loadavg: 0.92 0.98 0.94 3/83 5094
/proc/meminfo: memFree=816864/2055920 swapFree=4156596/4192956
[pid=5094] ppid=5092 vsize=186848 CPUtime=0.09
/proc/5094/stat : 5094 (kcnfs-2006) R 5092 5094 4282 0 -1 4194304 1590 0 0 0 9 0 0 0 18 0 1 0 323443866 191332352 1575 18446744073709551615 134512640 135163436 4294956704 18446744073709551615 134811879 0 0 4096 0 0 0 0 17 1 0 0
/proc/5094/statm: 46712 1575 47 158 0 46552 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 186848

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

[startup+0.105198 s]
/proc/loadavg: 0.92 0.98 0.94 3/83 5094
/proc/meminfo: memFree=816864/2055920 swapFree=4156596/4192956
[pid=5094] ppid=5092 vsize=186848 CPUtime=0.09
/proc/5094/stat : 5094 (kcnfs-2006) R 5092 5094 4282 0 -1 4194304 1590 0 0 0 9 0 0 0 18 0 1 0 323443866 191332352 1575 18446744073709551615 134512640 135163436 4294956704 18446744073709551615 134811879 0 0 4096 0 0 0 0 17 1 0 0
/proc/5094/statm: 46712 1575 47 158 0 46552 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 186848

Child status: 1
Real time (s): 0.115346
CPU time (s): 0.115981
CPU user time (s): 0.106983
CPU system time (s): 0.008998
CPU usage (%): 100.55
Max. virtual memory (cumulated for all children) (KiB): 186848

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.106983
system time used= 0.008998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1699
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= 2

runsolver used 0.003999 second user time and 0.002999 second system time

The end

Launcher Data (download as text)

Begin job on node12 on Sun Mar  4 19:01:34 UTC 2007

IDJOB= 319691
IDBENCH= 20485
IDSOLVER= 113
FILE ID= node12/319691-1173034894

PBS_JOBID= 4012241

Free space on /tmp= 66502 MiB

SOLVER NAME= KCNFS 2006
BENCH NAME= HOME/pub/bench/SAT07/industrial/grieu/vmpc_25.cnf
COMMAND LINE= /tmp/evaluation/319691-1173034894/kcnfs-2006 /tmp/evaluation/319691-1173034894/instance-319691-1173034894.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node12/watcher-319691-1173034894 -o ROOT/results/node12/solver-319691-1173034894 -C 1200 -W 2400 -M 1800 --output-limit 1,15  /tmp/evaluation/319691-1173034894/kcnfs-2006 /tmp/evaluation/319691-1173034894/instance-319691-1173034894.cnf            

META MD5SUM SOLVER= 23f87ccf1c743ff5b6146b444e216cd3
MD5SUM BENCH=  c5b44b10975f50cd32d40650a6a22d18

RANDOM SEED= 397269541

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node12.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:        817272 kB
Buffers:         49692 kB
Cached:        1087396 kB
SwapCached:      14832 kB
Active:         359596 kB
Inactive:       804216 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        817272 kB
SwapTotal:     4192956 kB
SwapFree:      4156596 kB
Dirty:            4244 kB
Writeback:           0 kB
Mapped:          34252 kB
Slab:            59984 kB
Committed_AS:  1537244 kB
PageTables:       1936 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= 66502 MiB

End job on node12 on Sun Mar  4 19:01:34 UTC 2007