Trace number 320949

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
tinisat 2007-02-08UNSAT 0.58191 0.582057

General information on the benchmark

Nameindustrial/babic/xinetd/
xinetd_vc56703.cnf
MD5SUM09053ffc48c8fbc3352a0ce4d89c2bbb
Bench CategoryINDUST (industrial instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.193969
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 (download as text)

0.29/0.38	c Tinisat 0.22
0.29/0.38	c solving /tmp/evaluation/320949-1176325654/instance-320949-1176325654.cnf
0.29/0.38	c 110923 variables, 286428 clauses
0.49/0.57	s UNSATISFIABLE
0.49/0.57	c 0 decisions, 1 conflicts, 0 restarts
0.49/0.57	c solved in 0.57s

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node60/watcher-320949-1176325654 -o ROOT/results/node60/solver-320949-1176325654 -C 1200 -W 2400 -M 1800 --output-limit 1,15 /tmp/evaluation/320949-1176325654/tinisat /tmp/evaluation/320949-1176325654/instance-320949-1176325654.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.97 3/64 20662
/proc/meminfo: memFree=954048/2055920 swapFree=4184868/4192956
[pid=20662] ppid=20660 vsize=2956 CPUtime=0
/proc/20662/stat : 20662 (tinisat) R 20660 20662 19386 0 -1 4194304 103 0 0 0 0 0 0 0 18 0 1 0 80475417 3026944 88 18446744073709551615 134512640 134966189 4294956592 18446744073709551615 134629133 0 0 4096 0 0 0 0 17 1 0 0
/proc/20662/statm: 739 88 48 110 0 626 0

[startup+0.0942619 s]
/proc/loadavg: 0.91 0.95 0.97 3/64 20662
/proc/meminfo: memFree=954048/2055920 swapFree=4184868/4192956
[pid=20662] ppid=20660 vsize=4276 CPUtime=0.08
/proc/20662/stat : 20662 (tinisat) R 20660 20662 19386 0 -1 4194304 568 0 0 0 8 0 0 0 18 0 1 0 80475417 4378624 553 18446744073709551615 134512640 134966189 4294956592 18446744073709551615 134612771 0 0 4096 0 0 0 0 17 1 0 0
/proc/20662/statm: 1069 553 48 110 0 956 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 4276

[startup+0.101263 s]
/proc/loadavg: 0.91 0.95 0.97 3/64 20662
/proc/meminfo: memFree=954048/2055920 swapFree=4184868/4192956
[pid=20662] ppid=20660 vsize=4408 CPUtime=0.09
/proc/20662/stat : 20662 (tinisat) R 20660 20662 19386 0 -1 4194304 600 0 0 0 9 0 0 0 18 0 1 0 80475417 4513792 585 18446744073709551615 134512640 134966189 4294956592 18446744073709551615 134612771 0 0 4096 0 0 0 0 17 1 0 0
/proc/20662/statm: 1102 585 48 110 0 989 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 4408

[startup+0.301283 s]
/proc/loadavg: 0.91 0.95 0.97 3/64 20662
/proc/meminfo: memFree=954048/2055920 swapFree=4184868/4192956
[pid=20662] ppid=20660 vsize=7180 CPUtime=0.29
/proc/20662/stat : 20662 (tinisat) R 20660 20662 19386 0 -1 4194304 1589 0 0 0 29 0 0 0 19 0 1 0 80475417 7352320 1574 18446744073709551615 134512640 134966189 4294956592 18446744073709551615 134612771 0 0 4096 0 0 0 0 17 1 0 0
/proc/20662/statm: 1795 1574 48 110 0 1682 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 7180

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

[startup+0.501302 s]
/proc/loadavg: 0.91 0.95 0.97 3/64 20662
/proc/meminfo: memFree=954048/2055920 swapFree=4184868/4192956
[pid=20662] ppid=20660 vsize=31252 CPUtime=0.49
/proc/20662/stat : 20662 (tinisat) R 20660 20662 19386 0 -1 4194304 5913 0 0 0 47 2 0 0 20 0 1 0 80475417 32002048 5897 18446744073709551615 134512640 134966189 4294956592 18446744073709551615 134778326 0 0 4096 0 0 0 0 17 1 0 0
/proc/20662/statm: 7846 5898 51 110 0 7733 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 31252

Child status: 20
Real time (s): 0.582057
CPU time (s): 0.58191
CPU user time (s): 0.541917
CPU system time (s): 0.039993
CPU usage (%): 99.9747
Max. virtual memory (cumulated for all children) (KiB): 31252

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.541917
system time used= 0.039993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 7828
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.000999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node60 on Wed Apr 11 21:07:34 UTC 2007

IDJOB= 320949
IDBENCH= 20516
IDSOLVER= 100
FILE ID= node60/320949-1176325654

PBS_JOBID= 4516722

Free space on /tmp= 66559 MiB

SOLVER NAME= tinisat 2007-02-08
BENCH NAME= HOME/pub/bench/SAT07/industrial/babic/xinetd/xinetd_vc56703.cnf
COMMAND LINE= /tmp/evaluation/320949-1176325654/tinisat /tmp/evaluation/320949-1176325654/instance-320949-1176325654.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node60/watcher-320949-1176325654 -o ROOT/results/node60/solver-320949-1176325654 -C 1200 -W 2400 -M 1800 --output-limit 1,15  /tmp/evaluation/320949-1176325654/tinisat /tmp/evaluation/320949-1176325654/instance-320949-1176325654.cnf            

META MD5SUM SOLVER= 15788d06198cf45d0201cced774790cd
MD5SUM BENCH=  09053ffc48c8fbc3352a0ce4d89c2bbb

RANDOM SEED= 102855013

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node60.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.214
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.214
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:        954520 kB
Buffers:         49180 kB
Cached:         837624 kB
SwapCached:       2160 kB
Active:         348592 kB
Inactive:       547992 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        954520 kB
SwapTotal:     4192956 kB
SwapFree:      4184868 kB
Dirty:            5512 kB
Writeback:           0 kB
Mapped:          16864 kB
Slab:           190816 kB
Committed_AS:   131860 kB
PageTables:       1464 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= 66559 MiB

End job on node60 on Wed Apr 11 21:07:35 UTC 2007