Trace number 314229

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 2004? 0.001998 0.00516293

General information on the benchmark

Nameindustrial/anbulagan/
hard-unsat/partial-5-11-u.cnf
MD5SUM8e22d84b1ae625d44fbf300a32374a2d
Bench CategoryINDUST (industrial instances)
Best result obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark
Satisfiable
(Un)Satisfiability was proved
Number of variables164158
Number of clauses730719
Sum of the clauses size1660140
Maximum clause length10
Minimum clause length1
Number of clauses of size 112474
Number of clauses of size 2600009
Number of clauses of size 387256
Number of clauses of size 43440
Number of clauses of size 513760
Number of clauses of size over 513780

Solver Data (download as text)

0.00/0.00	
0.00/0.00	c Computed by /tmp/evaluation/314229-1176898509/kcnfs-2004   V. 03/02/12
0.00/0.00	c readcnf :: Number of variables cannot exceed 20000
0.00/0.00	s UNKNOWN (Rejected)
0.00/0.00	c Computation time not available !!
0.00/0.00	c Execution time not available !!
0.00/0.00	c Size of search tree : 0 node
0.00/0.00

Verifier Data (download as text)

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

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node5/watcher-314229-1176898509 -o ROOT/results/node5/solver-314229-1176898509 -C 1200 -W 2400 -M 1800 --output-limit 1,15 --use-pty /tmp/evaluation/314229-1176898509/kcnfs-2004 /tmp/evaluation/314229-1176898509/instance-314229-1176898509.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
Using a pseudo terminal to collect output from the solver
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.92 0.97 0.92 3/77 21773
/proc/meminfo: memFree=1572928/2055920 swapFree=4148144/4192956
[pid=21773] ppid=21771 vsize=0 CPUtime=0
/proc/21773/stat : 21773 (kcnfs-2004) Z 21771 21773 20760 0 -1 12 68 0 0 0 0 0 0 0 15 0 1 0 165888579 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 0 18446744071563351923 0 0 17 1 0 0
/proc/21773/statm: 0 0 0 0 0 0 0

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

Child status: 0
Real time (s): 0.00516293
CPU time (s): 0.001998
CPU user time (s): 0.000999
CPU system time (s): 0.000999
CPU usage (%): 38.699
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.002999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node5 on Wed Apr 18 12:15:09 UTC 2007

IDJOB= 314229
IDBENCH= 20386
IDSOLVER= 114
FILE ID= node5/314229-1176898509

PBS_JOBID= 4595148

Free space on /tmp= 66426 MiB

SOLVER NAME= KCNFS 2004
BENCH NAME= HOME/pub/bench/SAT07/industrial/anbulagan/hard-unsat/partial-5-11-u.cnf
COMMAND LINE= /tmp/evaluation/314229-1176898509/kcnfs-2004 /tmp/evaluation/314229-1176898509/instance-314229-1176898509.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node5/watcher-314229-1176898509 -o ROOT/results/node5/solver-314229-1176898509 -C 1200 -W 2400 -M 1800 --output-limit 1,15 --use-pty /tmp/evaluation/314229-1176898509/kcnfs-2004 /tmp/evaluation/314229-1176898509/instance-314229-1176898509.cnf            

META MD5SUM SOLVER= 23f87ccf1c743ff5b6146b444e216cd3
MD5SUM BENCH=  8e22d84b1ae625d44fbf300a32374a2d

RANDOM SEED= 798054384

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node5.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.232
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.232
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:       1573400 kB
Buffers:         21172 kB
Cached:         393408 kB
SwapCached:      12800 kB
Active:          94040 kB
Inactive:       346820 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1573400 kB
SwapTotal:     4192956 kB
SwapFree:      4148144 kB
Dirty:           15880 kB
Writeback:           0 kB
Mapped:          29800 kB
Slab:            27288 kB
Committed_AS:  8603860 kB
PageTables:       1720 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= 66426 MiB

End job on node5 on Wed Apr 18 12:15:09 UTC 2007