Trace number 308459

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
CMUSAT 2007-02-08UNSAT 0.276957 0.278736

General information on the benchmark

Namerandom/2+p/p0.7/v5500/
unif2p-p0.7-v5500-c14685-S1110066181-15-UNSAT.cnf
MD5SUM02ac0323b8681994481799266f6a3a32
Bench CategoryRANDOM (random instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.172972
Satisfiable
(Un)Satisfiability was proved
Number of variables5496
Number of clauses14684
Sum of the clauses size39647
Maximum clause length3
Minimum clause length2
Number of clauses of size 10
Number of clauses of size 24405
Number of clauses of size 310279
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 Pre-processing provided 0 assignments
0.00/0.00	c |  Number of variables:  5500                                                 |
0.00/0.02	c |  Number of clauses:    14684                                                |
0.20/0.27	c |  Parsing time:         0.02         sec                                       |
0.20/0.27	c #varS 5500 #clauseS 12474
0.20/0.27	c REMAP internally 1
0.20/0.27	c After remapping new number of variables: 3911
0.20/0.27	c DBreduced=0 GV=101[0]  GL=12575[ 12474,101] Prune=301 decisions=200 restart=0 est=1.96181e-05 DB Impl=36542[0]  
0.20/0.27	c DBreduced=0 GV=151[0]  GL=12624[ 12474,150] Prune=441 decisions=290 restart=1 est=0.204571 DB Impl=55197[0]  
0.20/0.27	c DBreduced=0 GV=227[0]  GL=12700[ 12474,226] Prune=639 decisions=412 restart=2 est=0.205186 DB Impl=83685[0]  
0.20/0.27	c DBreduced=0 GV=338[0]  GL=12811[ 12474,337] Prune=908 decisions=570 restart=3 est=0.204682 DB Impl=123881[0]  
0.20/0.27	c DBreduced=0 GV=507[0]  GL=12977[ 12474,503] Prune=1314 decisions=807 restart=4 est=0.742054 DB Impl=191091[0]  
0.20/0.27	c DBreduced=0 GV=760[0]  GL=13228[ 12474,754] Prune=1915 decisions=1155 restart=5 est=1.61093 DB Impl=292438[0]  
0.20/0.27	c #Total time (in seconds): 0.272958
0.20/0.27	c #Memory used (in MB): 4.02344
0.20/0.27	c 
0.20/0.27	s UNSATISFIABLE

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node65/watcher-308459-1172520755 -o ROOT/results/node65/solver-308459-1172520755 -C 1200 -M 1800 --output-limit 1,15 /tmp/evaluation/308459-1172520755/cmusat /tmp/evaluation/308459-1172520755/instance-308459-1172520755.cnf 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1230 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.88 0.98 0.99 3/64 18633
/proc/meminfo: memFree=1912392/2055920 swapFree=4172316/4192956
[pid=18633] ppid=18631 vsize=2936 CPUtime=0
/proc/18633/stat : 18633 (cmusat) R 18631 18633 17947 0 -1 4194304 390 0 0 0 0 0 0 0 18 0 1 0 272033079 3006464 373 18446744073709551615 134512640 135508737 4294956720 18446744073709551615 134514306 0 0 4096 35 0 0 0 17 1 0 0
/proc/18633/statm: 734 373 96 243 0 488 0

[startup+0.106816 s]
/proc/loadavg: 0.88 0.98 0.99 3/64 18633
/proc/meminfo: memFree=1912392/2055920 swapFree=4172316/4192956
[pid=18633] ppid=18631 vsize=3988 CPUtime=0.1
/proc/18633/stat : 18633 (cmusat) R 18631 18633 17947 0 -1 4194304 948 0 0 0 10 0 0 0 18 0 1 0 272033079 4083712 603 18446744073709551615 134512640 135508737 4294956720 18446744073709551615 134589601 0 0 4096 35 0 0 0 17 1 0 0
/proc/18633/statm: 997 603 113 243 0 751 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 3988

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

[startup+0.208832 s]
/proc/loadavg: 0.88 0.98 0.99 3/64 18633
/proc/meminfo: memFree=1912392/2055920 swapFree=4172316/4192956
[pid=18633] ppid=18631 vsize=3988 CPUtime=0.2
/proc/18633/stat : 18633 (cmusat) R 18631 18633 17947 0 -1 4194304 957 0 0 0 20 0 0 0 19 0 1 0 272033079 4083712 612 18446744073709551615 134512640 135508737 4294956720 18446744073709551615 134582500 0 0 4096 35 0 0 0 17 1 0 0
/proc/18633/statm: 997 612 118 243 0 751 0
Current children cumulated CPU time (s) 0.2
Current children cumulated vsize (KiB) 3988

Child status: 20
Real time (s): 0.278736
CPU time (s): 0.276957
CPU user time (s): 0.272958
CPU system time (s): 0.003999
CPU usage (%): 99.3617
Max. virtual memory (cumulated for all children) (KiB): 3988

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.272958
system time used= 0.003999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 985
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.003999 second user time and 0.003999 second system time

The end

Launcher Data (download as text)

Begin job on node65 on Mon Feb 26 20:12:35 UTC 2007

IDJOB= 308459
IDBENCH= 20232
IDSOLVER= 121
FILE ID= node65/308459-1172520755

PBS_JOBID= 3971791

Free space on /tmp= 66559 MiB

SOLVER NAME= CMUSAT 2007-02-08
BENCH NAME= HOME/pub/bench/SAT07/random/2+p/p0.7/v5500/unif2p-p0.7-v5500-c14685-S1110066181-15-UNSAT.cnf
COMMAND LINE= /tmp/evaluation/308459-1172520755/cmusat /tmp/evaluation/308459-1172520755/instance-308459-1172520755.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node65/watcher-308459-1172520755 -o ROOT/results/node65/solver-308459-1172520755 -C 1200 -M 1800 --output-limit 1,15  /tmp/evaluation/308459-1172520755/cmusat /tmp/evaluation/308459-1172520755/instance-308459-1172520755.cnf            

META MD5SUM SOLVER= af990fb12f8926fdd756b397adb3b5cf
MD5SUM BENCH=  02ac0323b8681994481799266f6a3a32

RANDOM SEED= 293750423

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node65.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.259
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.259
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:       1912800 kB
Buffers:         20912 kB
Cached:          73812 kB
SwapCached:      14756 kB
Active:          36488 kB
Inactive:        80160 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1912800 kB
SwapTotal:     4192956 kB
SwapFree:      4172316 kB
Dirty:            2796 kB
Writeback:           0 kB
Mapped:          15768 kB
Slab:            12456 kB
Committed_AS:   614848 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= 66559 MiB

End job on node65 on Mon Feb 26 20:12:36 UTC 2007