Trace number 291645

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
FH 2007-02-08SAT 0.192969 0.195023

General information on the benchmark

Namerandom/OnTreshold/5SAT/v80/
unif-k5-r21.3-v80-c1704-S256297823-16.SAT.shuffled.cnf
MD5SUM98acb22e903e1289d5e4bb5a28958843
Bench CategoryRANDOM (random instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.05799
Satisfiable
(Un)Satisfiability was proved
Number of variables80
Number of clauses1704
Sum of the clauses size8520
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 51704
Number of clauses of size over 50

Solver Data (download as text)

0.10/0.19	c try 1 flip j 27970
0.10/0.19	c A solution is found
0.10/0.19	s SATISFIABLE
0.10/0.19	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 
0.10/0.19	v 0 
0.10/0.19	c Done (mycputime is 0.000 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/node29/watcher-291645-1171744901 -o ROOT/results/node29/solver-291645-1171744901 -C 1200 -M 1800 --output-limit 1,15 /tmp/evaluation/291645-1171744901/FH /tmp/evaluation/291645-1171744901/instance-291645-1171744901.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.92 0.96 0.83 3/77 14641
/proc/meminfo: memFree=1008928/2055920 swapFree=4147432/4192956
[pid=14641] ppid=14639 vsize=244848 CPUtime=0
/proc/14641/stat : 14641 (FH) R 14639 14641 14536 0 -1 4194304 125 0 0 0 0 0 0 0 18 0 1 0 168254446 250724352 108 18446744073709551615 134512640 134936988 4294956640 18446744073709551615 134589751 0 0 4096 0 0 0 0 17 1 0 0
/proc/14641/statm: 61212 108 36 103 0 60716 0

[startup+0.107043 s]
/proc/loadavg: 0.92 0.96 0.83 3/77 14641
/proc/meminfo: memFree=1008928/2055920 swapFree=4147432/4192956
[pid=14641] ppid=14639 vsize=246400 CPUtime=0.1
/proc/14641/stat : 14641 (FH) R 14639 14641 14536 0 -1 4194304 181 0 0 0 10 0 0 0 18 0 1 0 168254446 252313600 161 18446744073709551615 134512640 134936988 4294956640 18446744073709551615 134553554 0 0 4096 0 0 0 0 17 1 0 0
/proc/14641/statm: 61600 161 40 103 0 61104 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 246400

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

[startup+0.107043 s]
/proc/loadavg: 0.92 0.96 0.83 3/77 14641
/proc/meminfo: memFree=1008928/2055920 swapFree=4147432/4192956
[pid=14641] ppid=14639 vsize=246400 CPUtime=0.1
/proc/14641/stat : 14641 (FH) R 14639 14641 14536 0 -1 4194304 181 0 0 0 10 0 0 0 18 0 1 0 168254446 252313600 161 18446744073709551615 134512640 134936988 4294956640 18446744073709551615 134553554 0 0 4096 0 0 0 0 17 1 0 0
/proc/14641/statm: 61600 161 40 103 0 61104 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 246400

Child status: 10
Real time (s): 0.195023
CPU time (s): 0.192969
CPU user time (s): 0.19097
CPU system time (s): 0.001999
CPU usage (%): 98.9468
Max. virtual memory (cumulated for all children) (KiB): 246400

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

runsolver used 0.000999 second user time and 0.006998 second system time

The end

Launcher Data (download as text)

Begin job on node29 on Sat Feb 17 20:41:41 UTC 2007

IDJOB= 291645
IDBENCH= 19820
IDSOLVER= 117
FILE ID= node29/291645-1171744901

PBS_JOBID= 3839477

Free space on /tmp= 66559 MiB

SOLVER NAME= FH 2007-02-08
BENCH NAME= HOME/pub/bench/SAT07/random/OnTreshold/5SAT/v80/unif-k5-r21.3-v80-c1704-S256297823-16.SAT.shuffled.cnf
COMMAND LINE= /tmp/evaluation/291645-1171744901/FH /tmp/evaluation/291645-1171744901/instance-291645-1171744901.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node29/watcher-291645-1171744901 -o ROOT/results/node29/solver-291645-1171744901 -C 1200 -M 1800 --output-limit 1,15  /tmp/evaluation/291645-1171744901/FH /tmp/evaluation/291645-1171744901/instance-291645-1171744901.cnf            

META MD5SUM SOLVER= 4ad8950502569bcbd9dc3ae819b6eefe
MD5SUM BENCH=  98acb22e903e1289d5e4bb5a28958843

RANDOM SEED= 226895015

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node29.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.209
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	: 5931.00
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.209
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:       1009336 kB
Buffers:         36404 kB
Cached:         913892 kB
SwapCached:      12176 kB
Active:         711664 kB
Inactive:       261444 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1009336 kB
SwapTotal:     4192956 kB
SwapFree:      4147432 kB
Dirty:            6240 kB
Writeback:           0 kB
Mapped:          29800 kB
Slab:            58936 kB
Committed_AS:   598372 kB
PageTables:       1864 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 node29 on Sat Feb 17 20:41:43 UTC 2007