Trace number 293170

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
adaptg2wsatp 2007-02-08SAT 1.11783 1.11983

General information on the benchmark

Namerandom/OnTreshold/5SAT/v120/
unif-k5-r21.3-v120-c2556-S340864765-13.SAT.shuffled.cnf
MD5SUM1a2d4f656ef1a93a804e74aaef307a73
Bench CategoryRANDOM (random instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.527919
Satisfiable
(Un)Satisfiability was proved
Number of variables120
Number of clauses2556
Sum of the clauses size12780
Maximum clause length5
Minimum clause length5
Number of clauses of size 10
Number of clauses of size 20
Number of clauses of size 30
Number of clauses of size 40
Number of clauses of size 52556
Number of clauses of size over 50

Solver Data (download as text)

1.02/1.11	c try 1 flip j 214498
1.02/1.11	c A solution is found
1.02/1.11	s SATISFIABLE
1.02/1.11	v -1 -2 3 4 5 -6 7 8 9 -10 11 12 13 -14 15 -16 -17 -18 19 -20 21 -22 23 24 -25 -26 27 -28 29 -30 31 -32 -33 -34 35 36 -37 38 -39 40 -41 42 43 44 -45 -46 -47 48 -49 -50 51 52 53 -54 -55 -56 -57 -58 -59 60 61 -62 63 -64 -65 66 67 -68 -69 -70 71 -72 73 74 -75 76 -77 -78 -79 -80 -81 -82 83 -84 -85 -86 -87 -88 -89 90 91 92 -93 94 -95 96 97 98 -99 -100 101 -102 103 104 105 106 -107 -108 -109 -110 111 112 113 -114 -115 116 117 118 -119 120 
1.02/1.11	v 0 
1.02/1.11	c Done (mycputime is 1.020 seconds)

Verifier Data (download as text)

OK

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node24/watcher-293170-1171766043 -o ROOT/results/node24/solver-293170-1171766043 -C 1200 -M 1800 --output-limit 1,15 /tmp/evaluation/293170-1171766043/adaptg2wsatp /tmp/evaluation/293170-1171766043/instance-293170-1171766043.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.98 0.99 3/77 29917
/proc/meminfo: memFree=340672/2055920 swapFree=4144024/4192956
[pid=29917] ppid=29915 vsize=222844 CPUtime=0
/proc/29917/stat : 29917 (adaptg2wsatp) R 29915 29917 28770 0 -1 4194304 95 0 0 0 0 0 0 0 18 0 1 0 196558593 228192256 79 18446744073709551615 134512640 134935456 4294956624 18446744073709551615 134588183 0 0 4096 0 0 0 0 17 1 0 0
/proc/29917/statm: 55711 79 38 103 0 55215 0

[startup+0.106916 s]
/proc/loadavg: 0.91 0.98 0.99 3/77 29917
/proc/meminfo: memFree=340672/2055920 swapFree=4144024/4192956
[pid=29917] ppid=29915 vsize=224684 CPUtime=0.1
/proc/29917/stat : 29917 (adaptg2wsatp) R 29915 29917 28770 0 -1 4194304 206 0 0 0 10 0 0 0 18 0 1 0 196558593 230076416 186 18446744073709551615 134512640 134935456 4294956624 18446744073709551615 134557172 0 0 4096 0 0 0 0 17 1 0 0
/proc/29917/statm: 56171 186 42 103 0 55675 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 224684

[startup+0.514959 s]
/proc/loadavg: 0.91 0.98 0.99 3/77 29917
/proc/meminfo: memFree=340672/2055920 swapFree=4144024/4192956
[pid=29917] ppid=29915 vsize=224684 CPUtime=0.51
/proc/29917/stat : 29917 (adaptg2wsatp) R 29915 29917 28770 0 -1 4194304 206 0 0 0 51 0 0 0 21 0 1 0 196558593 230076416 186 18446744073709551615 134512640 134935456 4294956624 18446744073709551615 134550520 0 0 4096 0 0 0 0 17 1 0 0
/proc/29917/statm: 56171 186 42 103 0 55675 0
Current children cumulated CPU time (s) 0.51
Current children cumulated vsize (KiB) 224684

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

[startup+0.820992 s]
/proc/loadavg: 0.91 0.98 0.99 3/77 29917
/proc/meminfo: memFree=340672/2055920 swapFree=4144024/4192956
[pid=29917] ppid=29915 vsize=224684 CPUtime=0.81
/proc/29917/stat : 29917 (adaptg2wsatp) R 29915 29917 28770 0 -1 4194304 206 0 0 0 81 0 0 0 24 0 1 0 196558593 230076416 186 18446744073709551615 134512640 134935456 4294956624 18446744073709551615 134552361 0 0 4096 0 0 0 0 17 1 0 0
/proc/29917/statm: 56171 186 42 103 0 55675 0
Current children cumulated CPU time (s) 0.81
Current children cumulated vsize (KiB) 224684

[startup+1.02501 s]
/proc/loadavg: 0.91 0.98 0.99 3/77 29917
/proc/meminfo: memFree=340672/2055920 swapFree=4144024/4192956
[pid=29917] ppid=29915 vsize=224684 CPUtime=1.02
/proc/29917/stat : 29917 (adaptg2wsatp) R 29915 29917 28770 0 -1 4194304 206 0 0 0 102 0 0 0 25 0 1 0 196558593 230076416 186 18446744073709551615 134512640 134935456 4294956624 18446744073709551615 134550557 0 0 4096 0 0 0 0 17 1 0 0
/proc/29917/statm: 56171 186 42 103 0 55675 0
Current children cumulated CPU time (s) 1.02
Current children cumulated vsize (KiB) 224684

Child status: 10
Real time (s): 1.11983
CPU time (s): 1.11783
CPU user time (s): 1.11683
CPU system time (s): 0.000999
CPU usage (%): 99.821
Max. virtual memory (cumulated for all children) (KiB): 224684

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.11683
system time used= 0.000999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 218
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.002999 second user time and 0.010998 second system time

The end

Launcher Data (download as text)

Begin job on node24 on Sun Feb 18 02:34:03 UTC 2007

IDJOB= 293170
IDBENCH= 19857
IDSOLVER= 125
FILE ID= node24/293170-1171766043

PBS_JOBID= 3839487

Free space on /tmp= 66558 MiB

SOLVER NAME= adaptg2wsatp 2007-02-08
BENCH NAME= HOME/pub/bench/SAT07/random/OnTreshold/5SAT/v120/unif-k5-r21.3-v120-c2556-S340864765-13.SAT.shuffled.cnf
COMMAND LINE= /tmp/evaluation/293170-1171766043/adaptg2wsatp /tmp/evaluation/293170-1171766043/instance-293170-1171766043.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node24/watcher-293170-1171766043 -o ROOT/results/node24/solver-293170-1171766043 -C 1200 -M 1800 --output-limit 1,15  /tmp/evaluation/293170-1171766043/adaptg2wsatp /tmp/evaluation/293170-1171766043/instance-293170-1171766043.cnf            

META MD5SUM SOLVER= dc7cfffb7b5aa51d884144c196acd75c
MD5SUM BENCH=  1a2d4f656ef1a93a804e74aaef307a73

RANDOM SEED= 297221122

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node24.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.232
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.232
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:        341144 kB
Buffers:         39788 kB
Cached:        1573872 kB
SwapCached:       4536 kB
Active:         690752 kB
Inactive:       933224 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        341144 kB
SwapTotal:     4192956 kB
SwapFree:      4144024 kB
Dirty:            6304 kB
Writeback:           0 kB
Mapped:          15472 kB
Slab:            76344 kB
Committed_AS:   622332 kB
PageTables:       1732 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 node24 on Sun Feb 18 02:34:04 UTC 2007