Trace number 1796476

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
SatElite + ReVivAl 0.23 2009-03-18UNSAT 0.129979 0.130824

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.129979
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.00/0.00	c revival is preprocessing the formula...Proved UNSATISFIABLE by ReVivAl !!
0.09/0.12	(polynomial instance)
0.09/0.12	done !
0.09/0.12	c Now, SatElite...
0.09/0.12	c Parsing...
0.09/0.12	c ==============================================================================
0.09/0.12	c |           |     ORIGINAL     |              LEARNT              |          |
0.09/0.12	c | Conflicts | Clauses Literals |   Limit Clauses Literals  Lit/Cl | Progress |
0.09/0.12	c ==============================================================================
0.09/0.12	c |         0 |       0        0 |       0       0        0     nan |  0.000 % |
0.09/0.12	c starts                :        0
0.09/0.12	c conflicts             :        0   (nan /sec)
0.09/0.12	c reduce learnts        :        0   (nan /sec)
0.09/0.12	c decisions             :        0   (nan /sec)
0.09/0.13	c propagations          :        0   (nan /sec)
0.09/0.13	c inspects              :        0   (nan /sec)
0.09/0.13	c memory used           : 0.671875 MB
0.09/0.13	c CPU time              :        0 s
0.09/0.13	c 
0.09/0.13	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-1796476-1242076411/watcher-1796476-1242076411 -o /tmp/evaluation-result-1796476-1242076411/solver-1796476-1242076411 -C 1200 -W 1800 -M 1800 HOME/run.sh HOME/instance-1796476-1242076411.cnf HOME 

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
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.92 0.98 0.99 3/65 2591
/proc/meminfo: memFree=1367976/2055920 swapFree=4156884/4192956
[pid=2591] ppid=2589 vsize=5360 CPUtime=0
/proc/2591/stat : 2591 (run.sh) S 2589 2591 2366 0 -1 4194304 287 0 0 0 0 0 0 0 20 0 1 0 235670573 5488640 237 1992294400 4194304 4889804 548682068784 18446744073709551615 251279237956 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/2591/statm: 1340 237 196 169 0 51 0
[pid=2592] ppid=2591 vsize=2124 CPUtime=0
/proc/2592/stat : 2592 (revival) R 2591 2591 2366 0 -1 4194304 261 0 0 0 0 0 0 0 21 0 1 0 235670574 2174976 227 1992294400 134512640 134537284 4294956368 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/2592/statm: 531 234 81 6 0 169 0

[startup+0.054017 s]
/proc/loadavg: 0.92 0.98 0.99 3/65 2591
/proc/meminfo: memFree=1367976/2055920 swapFree=4156884/4192956
[pid=2591] ppid=2589 vsize=5360 CPUtime=0
/proc/2591/stat : 2591 (run.sh) S 2589 2591 2366 0 -1 4194304 287 0 0 0 0 0 0 0 20 0 1 0 235670573 5488640 237 1992294400 4194304 4889804 548682068784 18446744073709551615 251279237956 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/2591/statm: 1340 237 196 169 0 51 0
[pid=2592] ppid=2591 vsize=19632 CPUtime=0.04
/proc/2592/stat : 2592 (revival) R 2591 2591 2366 0 -1 4194304 4253 0 0 0 3 1 0 0 21 0 1 0 235670574 20103168 4214 1992294400 134512640 134537284 4294956368 18446744073709551615 134527481 0 0 4096 0 0 0 0 17 1 0 0
/proc/2592/statm: 4908 4215 82 6 0 4546 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 24992

[startup+0.102023 s]
/proc/loadavg: 0.92 0.98 0.99 3/65 2591
/proc/meminfo: memFree=1367976/2055920 swapFree=4156884/4192956
[pid=2591] ppid=2589 vsize=5360 CPUtime=0
/proc/2591/stat : 2591 (run.sh) S 2589 2591 2366 0 -1 4194304 287 0 0 0 0 0 0 0 20 0 1 0 235670573 5488640 237 1992294400 4194304 4889804 548682068784 18446744073709551615 251279237956 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/2591/statm: 1340 237 196 169 0 51 0
[pid=2592] ppid=2591 vsize=24448 CPUtime=0.09
/proc/2592/stat : 2592 (revival) R 2591 2591 2366 0 -1 4194304 5345 0 0 0 7 2 0 0 21 0 1 0 235670574 25034752 5306 1992294400 134512640 134537284 4294956368 18446744073709551615 4478587 0 0 4096 0 0 0 0 17 1 0 0
/proc/2592/statm: 6112 5307 82 6 0 5750 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 29808

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

Child status: 20
Real time (s): 0.130824
CPU time (s): 0.129979
CPU user time (s): 0.099984
CPU system time (s): 0.029995
CPU usage (%): 99.3541
Max. virtual memory (cumulated for all children) (KiB): 29808

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

runsolver used 0.003999 second user time and 0.004999 second system time

The end

Launcher Data 

Begin job on node92 at 2009-05-11 23:13:32
IDJOB=1796476
IDBENCH=20516
IDSOLVER=647
FILE ID=node92/1796476-1242076411
PBS_JOBID= 9277593
Free space on /tmp= 66404 MiB

SOLVER NAME= SatElite + ReVivAl 0.23 2009-03-18
BENCH NAME= SAT07/industrial/babic/xinetd/xinetd_vc56703.cnf
COMMAND LINE= HOME/run.sh BENCHNAME TMPDIR
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1796476-1242076411/watcher-1796476-1242076411 -o /tmp/evaluation-result-1796476-1242076411/solver-1796476-1242076411 -C 1200 -W 1800 -M 1800  HOME/run.sh HOME/instance-1796476-1242076411.cnf HOME

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

MD5SUM BENCH= 09053ffc48c8fbc3352a0ce4d89c2bbb
RANDOM SEED=128199859

node92.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.245
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.245
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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1368392 kB
Buffers:         57576 kB
Cached:         548824 kB
SwapCached:      30760 kB
Active:         464684 kB
Inactive:       174044 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1368392 kB
SwapTotal:     4192956 kB
SwapFree:      4156884 kB
Dirty:            6388 kB
Writeback:           0 kB
Mapped:          14168 kB
Slab:            34636 kB
Committed_AS:   569888 kB
PageTables:       1460 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 node92 at 2009-05-11 23:13:32