Trace number 320835

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
minisat SAT 2007 (with assertions)UNSAT 0.638902 0.641267

General information on the benchmark

Nameindustrial/babic/
xinetd/itox_vc965.cnf
MD5SUM867a6f6420a887007f0529947c09f327
Bench CategoryINDUST (industrial instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.236963
Satisfiable
(Un)Satisfiability was proved
Number of variables115769
Number of clauses338946
Sum of the clauses size884379
Maximum clause length3
Minimum clause length1
Number of clauses of size 17057
Number of clauses of size 2118345
Number of clauses of size 3213544
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.00/0.00	c This is MiniSat 2.0 (Feb 1 2007, SAT-Competition version)
0.00/0.00	c ============================[ Problem Statistics ]=============================
0.00/0.00	c |                                                                             |
0.00/0.00	c |  Number of variables:  115941                                               |
0.00/0.00	c |  Number of clauses:    338946                                               |
0.59/0.63	c |  Parsing time:         0.59         s                                       |
0.59/0.63	c Solved by unit propagation
0.59/0.63	s UNSATISFIABLE

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/node25/watcher-320835-1176324651 -o ROOT/results/node25/solver-320835-1176324651 -C 1200 -W 2400 -M 1800 --output-limit 1,15 /tmp/evaluation/320835-1176324651/minisat /tmp/evaluation/320835-1176324651/instance-320835-1176324651.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.97 0.96 3/64 16057
/proc/meminfo: memFree=308480/2055920 swapFree=4192812/4192956
[pid=16057] ppid=16055 vsize=2504 CPUtime=0
/proc/16057/stat : 16057 (minisat) R 16055 16057 14968 0 -1 4194304 531 0 0 0 0 0 0 0 18 0 1 0 80382236 2564096 515 18446744073709551615 134512640 135078472 4294956592 18446744073709551615 134553294 0 0 4096 3 0 0 0 17 1 0 0
/proc/16057/statm: 626 518 58 138 0 485 0

[startup+0.0440661 s]
/proc/loadavg: 0.92 0.97 0.96 3/64 16057
/proc/meminfo: memFree=308480/2055920 swapFree=4192812/4192956
[pid=16057] ppid=16055 vsize=14316 CPUtime=0.03
/proc/16057/stat : 16057 (minisat) R 16055 16057 14968 0 -1 4194304 2806 0 0 0 2 1 0 0 18 0 1 0 80382236 14659584 2791 18446744073709551615 134512640 135078472 4294956592 18446744073709551615 134553503 0 0 4096 3 0 0 0 17 1 0 0
/proc/16057/statm: 3579 2794 58 138 0 3438 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 14316

[startup+0.101075 s]
/proc/loadavg: 0.92 0.97 0.96 3/64 16057
/proc/meminfo: memFree=308480/2055920 swapFree=4192812/4192956
[pid=16057] ppid=16055 vsize=17816 CPUtime=0.08
/proc/16057/stat : 16057 (minisat) R 16055 16057 14968 0 -1 4194304 3721 0 0 0 7 1 0 0 18 0 1 0 80382236 18243584 3705 18446744073709551615 134512640 135078472 4294956592 18446744073709551615 134707275 0 0 4096 3 0 0 0 17 1 0 0
/proc/16057/statm: 4454 3706 58 138 0 4313 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 17816

[startup+0.301109 s]
/proc/loadavg: 0.92 0.97 0.96 3/64 16057
/proc/meminfo: memFree=308480/2055920 swapFree=4192812/4192956
[pid=16057] ppid=16055 vsize=26516 CPUtime=0.28
/proc/16057/stat : 16057 (minisat) R 16055 16057 14968 0 -1 4194304 5852 0 0 0 26 2 0 0 19 0 1 0 80382236 27152384 5836 18446744073709551615 134512640 135078472 4294956592 18446744073709551615 134532681 0 0 4096 3 0 0 0 17 1 0 0
/proc/16057/statm: 6629 5836 58 138 0 6488 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 26516

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

[startup+0.501144 s]
/proc/loadavg: 0.92 0.97 0.96 3/64 16057
/proc/meminfo: memFree=308480/2055920 swapFree=4192812/4192956
[pid=16057] ppid=16055 vsize=29584 CPUtime=0.49
/proc/16057/stat : 16057 (minisat) R 16055 16057 14968 0 -1 4194304 6503 0 0 0 46 3 0 0 21 0 1 0 80382236 30294016 6487 18446744073709551615 134512640 135078472 4294956592 18446744073709551615 134707275 0 0 4096 3 0 0 0 17 1 0 0
/proc/16057/statm: 7396 6487 58 138 0 7255 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 29584

[startup+0.60116 s]
/proc/loadavg: 0.92 0.97 0.96 3/64 16057
/proc/meminfo: memFree=308480/2055920 swapFree=4192812/4192956
[pid=16057] ppid=16055 vsize=33808 CPUtime=0.59
/proc/16057/stat : 16057 (minisat) R 16055 16057 14968 0 -1 4194304 7739 0 0 0 56 3 0 0 22 0 1 0 80382236 34619392 7723 18446744073709551615 134512640 135078472 4294956592 18446744073709551615 134707275 0 0 4096 3 0 0 0 17 1 0 0
/proc/16057/statm: 8452 7723 58 138 0 8311 0
Current children cumulated CPU time (s) 0.59
Current children cumulated vsize (KiB) 33808

Child status: 20
Real time (s): 0.641267
CPU time (s): 0.638902
CPU user time (s): 0.593909
CPU system time (s): 0.044993
CPU usage (%): 99.6312
Max. virtual memory (cumulated for all children) (KiB): 33808

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

runsolver used 0.003999 second user time and 0.003999 second system time

The end

Launcher Data (download as text)

Begin job on node25 on Wed Apr 11 20:50:52 UTC 2007

IDJOB= 320835
IDBENCH= 20513
IDSOLVER= 109
FILE ID= node25/320835-1176324651

PBS_JOBID= 4516702

Free space on /tmp= 66558 MiB

SOLVER NAME= minisat SAT 2007
BENCH NAME= HOME/pub/bench/SAT07/industrial/babic/xinetd/itox_vc965.cnf
COMMAND LINE= /tmp/evaluation/320835-1176324651/minisat /tmp/evaluation/320835-1176324651/instance-320835-1176324651.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node25/watcher-320835-1176324651 -o ROOT/results/node25/solver-320835-1176324651 -C 1200 -W 2400 -M 1800 --output-limit 1,15  /tmp/evaluation/320835-1176324651/minisat /tmp/evaluation/320835-1176324651/instance-320835-1176324651.cnf            

META MD5SUM SOLVER= 120abd248b069e44985635f055606c5a
MD5SUM BENCH=  867a6f6420a887007f0529947c09f327

RANDOM SEED= 48188895

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node25.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.261
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.261
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:        308968 kB
Buffers:         42300 kB
Cached:        1455468 kB
SwapCached:          0 kB
Active:         649408 kB
Inactive:       863920 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        308968 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            7248 kB
Writeback:           0 kB
Mapped:          25700 kB
Slab:           219676 kB
Committed_AS:   138128 kB
PageTables:       1472 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= 66558 MiB

End job on node25 on Wed Apr 11 20:50:52 UTC 2007