Trace number 1718822

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
march_hi hiUNSAT 0.490924 0.491433

General information on the benchmark

Nameindustrial/babic/xinetd/
xinetd_vc56703.cnf
MD5SUM09053ffc48c8fbc3352a0ce4d89c2bbb
Bench CategoryAPPLICATION (applications instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.217966
Satisfiable
(Un)Satisfiability was proved
Number of variables110923
Number of clauses286428
Sum of the clauses size694958
Maximum clause length3
Minimum clause length1
Number of clauses of size 113085
Number of clauses of size 2138156
Number of clauses of size 3135187
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 50

Solver Data 

0.39/0.48	c main():: ***                                   [ march satisfiability solver ]                                   ***
0.39/0.48	c main()::  **                Copyright (C) 2001-2009 M.J.H. Heule, J.E. van Zwieten, and M. Dufour                 **
0.39/0.48	c main()::   *  This program may be redistributed and/or modified under the terms of the GNU Gereral Public License  *
0.39/0.48	c main()::
0.39/0.48	c initFormula():: searching for DIMACS p-line....
0.39/0.48	c initFormula():: the DIMACS p-line indicates a CNF of 110923 variables and 286428 clauses.
0.39/0.48	c parseCNF():: parsing....
0.39/0.48	c parseCNF():: the CNF contains 13085 unary clauses.
0.39/0.48	c runParser():: parsing was successful, warming up engines...
0.39/0.48	c runParser():: conflicting unary clauses, so instance is unsatisfiable!
0.39/0.48	s UNSATISFIABLE

Verifier Data 

No possible verification on an UNSAT instance

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1718822-1240640197/watcher-1718822-1240640197 -o /tmp/evaluation-result-1718822-1240640197/solver-1718822-1240640197 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/march_hi HOME/instance-1718822-1240640197.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): 1800 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.93 0.98 0.99 3/64 19179
/proc/meminfo: memFree=1203048/2055920 swapFree=4180840/4192956
[pid=19179] ppid=19177 vsize=5908 CPUtime=0
/proc/19179/stat : 19179 (march_hi) R 19177 19179 18809 0 -1 4194304 606 0 0 0 0 0 0 0 18 0 1 0 92046537 6049792 591 1992294400 134512640 135197378 4294956224 18446744073709551615 134568480 0 0 4096 0 0 0 0 17 1 0 0
/proc/19179/statm: 1477 594 58 167 0 1308 0

[startup+0.007732 s]
/proc/loadavg: 0.93 0.98 0.99 3/64 19179
/proc/meminfo: memFree=1203048/2055920 swapFree=4180840/4192956
[pid=19179] ppid=19177 vsize=6700 CPUtime=0
/proc/19179/stat : 19179 (march_hi) R 19177 19179 18809 0 -1 4194304 879 0 0 0 0 0 0 0 18 0 1 0 92046537 6860800 864 1992294400 134512640 135197378 4294956224 18446744073709551615 134697414 0 0 4096 0 0 0 0 17 1 0 0
/proc/19179/statm: 1675 868 58 167 0 1506 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 6700

[startup+0.101749 s]
/proc/loadavg: 0.93 0.98 0.99 3/64 19179
/proc/meminfo: memFree=1203048/2055920 swapFree=4180840/4192956
[pid=19179] ppid=19177 vsize=12756 CPUtime=0.09
/proc/19179/stat : 19179 (march_hi) R 19177 19179 18809 0 -1 4194304 2747 0 0 0 8 1 0 0 18 0 1 0 92046537 13062144 2732 1992294400 134512640 135197378 4294956224 18446744073709551615 134697414 0 0 4096 0 0 0 0 17 1 0 0
/proc/19179/statm: 3189 2732 58 167 0 3020 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 12756

[startup+0.301784 s]
/proc/loadavg: 0.93 0.98 0.99 3/64 19179
/proc/meminfo: memFree=1203048/2055920 swapFree=4180840/4192956
[pid=19179] ppid=19177 vsize=15000 CPUtime=0.29
/proc/19179/stat : 19179 (march_hi) R 19177 19179 18809 0 -1 4194304 3470 0 0 0 27 2 0 0 19 0 1 0 92046537 15360000 3455 1992294400 134512640 135197378 4294956224 18446744073709551615 134697414 0 0 4096 0 0 0 0 17 1 0 0
/proc/19179/statm: 3750 3455 58 167 0 3581 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 15000

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

[startup+0.401803 s]
/proc/loadavg: 0.93 0.98 0.99 3/64 19179
/proc/meminfo: memFree=1203048/2055920 swapFree=4180840/4192956
[pid=19179] ppid=19177 vsize=28416 CPUtime=0.39
/proc/19179/stat : 19179 (march_hi) R 19177 19179 18809 0 -1 4194304 3894 0 0 0 37 2 0 0 20 0 1 0 92046537 29097984 3877 1992294400 134512640 135197378 4294956224 18446744073709551615 134697414 0 0 4096 0 0 0 0 17 1 0 0
/proc/19179/statm: 7104 3880 60 167 0 6935 0
Current children cumulated CPU time (s) 0.39
Current children cumulated vsize (KiB) 28416

Child status: 20
Real time (s): 0.491433
CPU time (s): 0.490924
CPU user time (s): 0.440932
CPU system time (s): 0.049992
CPU usage (%): 99.8964
Max. virtual memory (cumulated for all children) (KiB): 28416

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

runsolver used 0.003999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node60 at 2009-04-25 08:16:38
IDJOB=1718822
IDBENCH=20516
IDSOLVER=521
FILE ID=node60/1718822-1240640197
PBS_JOBID= 9186404
Free space on /tmp= 66404 MiB

SOLVER NAME= march_hi hi
BENCH NAME= SAT07/industrial/babic/xinetd/xinetd_vc56703.cnf
COMMAND LINE= HOME/march_hi BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1718822-1240640197/watcher-1718822-1240640197 -o /tmp/evaluation-result-1718822-1240640197/solver-1718822-1240640197 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/march_hi HOME/instance-1718822-1240640197.cnf

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

MD5SUM BENCH= 09053ffc48c8fbc3352a0ce4d89c2bbb
RANDOM SEED=1608141671

node60.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.256
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.256
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:       1203528 kB
Buffers:         75824 kB
Cached:         691740 kB
SwapCached:       6548 kB
Active:         215032 kB
Inactive:       561656 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1203528 kB
SwapTotal:     4192956 kB
SwapFree:      4180840 kB
Dirty:            6056 kB
Writeback:           0 kB
Mapped:          14072 kB
Slab:            61624 kB
Committed_AS:   305264 kB
PageTables:       1448 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= 66404 MiB
End job on node60 at 2009-04-25 08:16:38