Trace number 308295

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.865867 0.865995

General information on the benchmark

Namerandom/2+p/p0.7/v3500/
unif2p-p0.7-v3500-c9345-S977957999-02-UNSAT.cnf
MD5SUM18f840e49f7b6014abf7c03df24e3402
Bench CategoryRANDOM (random instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.369942
Satisfiable
(Un)Satisfiability was proved
Number of variables3498
Number of clauses9344
Sum of the clauses size25229
Maximum clause length3
Minimum clause length2
Number of clauses of size 10
Number of clauses of size 22803
Number of clauses of size 36541
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:  3500                                                 |
0.00/0.01	c |  Number of clauses:    9344                                                 |
0.81/0.86	c |  Parsing time:         0.01         sec                                       |
0.81/0.86	c #varS 3500 #clauseS 7926
0.81/0.86	c REMAP internally 1
0.81/0.86	c After remapping new number of variables: 2498
0.81/0.86	c DBreduced=0 GV=101[0]  GL=8027[ 7926,101] Prune=300 decisions=199 restart=0 est=1.60321e-05 DB Impl=34412[0]  
0.81/0.86	c DBreduced=0 GV=151[0]  GL=8077[ 7926,151] Prune=423 decisions=272 restart=1 est=0.000160282 DB Impl=48901[0]  
0.81/0.86	c DBreduced=0 GV=226[0]  GL=8151[ 7926,225] Prune=615 decisions=389 restart=2 est=1.48171 DB Impl=72874[0]  
0.81/0.86	c DBreduced=0 GV=340[0]  GL=8263[ 7926,337] Prune=890 decisions=550 restart=3 est=2.72234 DB Impl=106713[0]  
0.81/0.86	c DBreduced=0 GV=507[0]  GL=8429[ 7926,503] Prune=1278 decisions=771 restart=4 est=2.76436 DB Impl=157022[0]  
0.81/0.86	c DBreduced=0 GV=761[0]  GL=8683[ 7926,757] Prune=1865 decisions=1104 restart=5 est=2.76279 DB Impl=234954[0]  
0.81/0.86	c DBreduced=0 GV=1140[0]  GL=9061[ 7926,1135] Prune=2804 decisions=1664 restart=6 est=2.80234 DB Impl=354468[0]  
0.81/0.86	c DBreduced=0 GV=1709[0]  GL=9630[ 7926,1704] Prune=4116 decisions=2407 restart=7 est=2.80285 DB Impl=530218[0]  
0.81/0.86	c DBreduced=0 GV=2563[0]  GL=10481[ 7926,2555] Prune=6164 decisions=3601 restart=8 est=3.04269 DB Impl=791408[0]  
0.81/0.86	c DBreduced=1 GV=3845[0]  GL=11469[ 7926,3543] Prune=9019 decisions=5174 restart=9 est=3.12304 DB Impl=1195098[0]  
0.81/0.86	c #Total time (in seconds): 0.857869
0.81/0.86	c #Memory used (in MB): 4.07422
0.81/0.86	c 
0.81/0.86	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/node63/watcher-308295-1172518272 -o ROOT/results/node63/solver-308295-1172518272 -C 1200 -M 1800 --output-limit 1,15 /tmp/evaluation/308295-1172518272/cmusat /tmp/evaluation/308295-1172518272/instance-308295-1172518272.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.91 0.95 0.99 3/64 9052
/proc/meminfo: memFree=1929944/2055920 swapFree=4179036/4192956
[pid=9052] ppid=9050 vsize=2636 CPUtime=0
/proc/9052/stat : 9052 (cmusat) R 9050 9052 8487 0 -1 4194304 294 0 0 0 0 0 0 0 18 0 1 0 271784560 2699264 277 18446744073709551615 134512640 135508737 4294956720 18446744073709551615 135090869 0 0 4096 35 0 0 0 17 1 0 0
/proc/9052/statm: 659 278 96 243 0 413 0

[startup+0.10723 s]
/proc/loadavg: 0.91 0.95 0.99 3/64 9052
/proc/meminfo: memFree=1929944/2055920 swapFree=4179036/4192956
[pid=9052] ppid=9050 vsize=3476 CPUtime=0.1
/proc/9052/stat : 9052 (cmusat) R 9050 9052 8487 0 -1 4194304 533 0 0 0 10 0 0 0 18 0 1 0 271784560 3559424 516 18446744073709551615 134512640 135508737 4294956720 18446744073709551615 134590317 0 0 4096 35 0 0 0 17 1 0 0
/proc/9052/statm: 869 516 118 243 0 623 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 3476

[startup+0.515272 s]
/proc/loadavg: 0.91 0.95 0.99 3/64 9052
/proc/meminfo: memFree=1929944/2055920 swapFree=4179036/4192956
[pid=9052] ppid=9050 vsize=3740 CPUtime=0.51
/proc/9052/stat : 9052 (cmusat) R 9050 9052 8487 0 -1 4194304 594 0 0 0 51 0 0 0 21 0 1 0 271784560 3829760 577 18446744073709551615 134512640 135508737 4294956720 18446744073709551615 134589593 0 0 4096 35 0 0 0 17 1 0 0
/proc/9052/statm: 935 577 118 243 0 689 0
Current children cumulated CPU time (s) 0.51
Current children cumulated vsize (KiB) 3740

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

[startup+0.821305 s]
/proc/loadavg: 0.91 0.95 0.99 3/64 9052
/proc/meminfo: memFree=1929944/2055920 swapFree=4179036/4192956
[pid=9052] ppid=9050 vsize=4172 CPUtime=0.81
/proc/9052/stat : 9052 (cmusat) R 9050 9052 8487 0 -1 4194304 704 0 0 0 81 0 0 0 24 0 1 0 271784560 4272128 687 18446744073709551615 134512640 135508737 4294956720 18446744073709551615 135107896 0 0 4096 35 0 0 0 17 1 0 0
/proc/9052/statm: 1043 687 118 243 0 797 0
Current children cumulated CPU time (s) 0.81
Current children cumulated vsize (KiB) 4172

Child status: 20
Real time (s): 0.865995
CPU time (s): 0.865867
CPU user time (s): 0.857869
CPU system time (s): 0.007998
CPU usage (%): 99.9852
Max. virtual memory (cumulated for all children) (KiB): 4172

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

runsolver used 0.003999 second user time and 0.003999 second system time

The end

Launcher Data (download as text)

Begin job on node63 on Mon Feb 26 19:31:12 UTC 2007

IDJOB= 308295
IDBENCH= 20227
IDSOLVER= 121
FILE ID= node63/308295-1172518272

PBS_JOBID= 3971776

Free space on /tmp= 66558 MiB

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

META MD5SUM SOLVER= af990fb12f8926fdd756b397adb3b5cf
MD5SUM BENCH=  18f840e49f7b6014abf7c03df24e3402

RANDOM SEED= 448301504

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node63.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:       1930352 kB
Buffers:         20492 kB
Cached:          64216 kB
SwapCached:       7976 kB
Active:          34196 kB
Inactive:        64332 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1930352 kB
SwapTotal:     4192956 kB
SwapFree:      4179036 kB
Dirty:            2748 kB
Writeback:           0 kB
Mapped:          15276 kB
Slab:            13008 kB
Committed_AS:   625964 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= 66558 MiB

End job on node63 on Mon Feb 26 19:31:13 UTC 2007