Trace number 1523121

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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
Hybrid2 2009-03-22SAT 0.19197 0.191183

General information on the benchmark

NameRANDOM/MEDIUM/5SAT/SATISFIABLE/100/
unif-k5-r21.3-v100-c2130-S1707873242-085.cnf
MD5SUM50fb19065f42fe4981158c7f4fb4e31f
Bench CategoryRANDOM (random instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.024995
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of clauses2130
Sum of the clauses size10650
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 52130
Number of clauses of size over 50

Solver Data 

0.09/0.19	c try 1 flip j 36378
0.09/0.19	c A solution is found
0.09/0.19	s SATISFIABLE
0.09/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 -81 82 -83 -84 85 -86 87 88 89 90 91 -92 -93 94 95 -96 97 -98 99 -100 
0.09/0.19	v 0 
0.09/0.19	c Done (mycputime is 0.130 seconds)

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:489) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1523121-1238456201/watcher-1523121-1238456201 -o /tmp/evaluation-result-1523121-1238456201/solver-1523121-1238456201 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/Hybrid2 HOME/instance-1523121-1238456201.cnf 2144920049 

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): 1800 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.99 0.98 0.99 3/73 15119
/proc/meminfo: memFree=1671440/2055920 swapFree=4175504/4192956
[pid=15119] ppid=15117 vsize=451072 CPUtime=0
/proc/15119/stat : 15119 (Hybrid2) R 15117 15119 14806 0 -1 4194304 155 0 0 0 0 0 0 0 18 0 1 0 1118284653 461897728 139 1992294400 134512640 135106774 4294956208 18446744073709551615 134612774 0 0 4096 0 0 0 0 17 1 0 0
/proc/15119/statm: 112768 139 53 145 0 111644 0

[startup+0.0683199 s]
/proc/loadavg: 0.99 0.98 0.99 3/73 15119
/proc/meminfo: memFree=1671440/2055920 swapFree=4175504/4192956
[pid=15119] ppid=15117 vsize=455104 CPUtime=0.06
/proc/15119/stat : 15119 (Hybrid2) R 15117 15119 14806 0 -1 4194304 196 0 0 0 6 0 0 0 18 0 1 0 1118284653 466026496 180 1992294400 134512640 135106774 4294956208 18446744073709551615 134527161 0 0 4096 0 0 0 0 17 1 0 0
/proc/15119/statm: 113776 180 54 145 0 112652 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 455104

[startup+0.101323 s]
/proc/loadavg: 0.99 0.98 0.99 3/73 15119
/proc/meminfo: memFree=1671440/2055920 swapFree=4175504/4192956
[pid=15119] ppid=15117 vsize=455104 CPUtime=0.09
/proc/15119/stat : 15119 (Hybrid2) R 15117 15119 14806 0 -1 4194304 198 0 0 0 9 0 0 0 18 0 1 0 1118284653 466026496 182 1992294400 134512640 135106774 4294956208 18446744073709551615 134528512 0 0 4096 0 0 0 0 17 1 0 0
/proc/15119/statm: 113776 182 56 145 0 112652 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 455104

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

Child status: 10
Real time (s): 0.191183
CPU time (s): 0.19197
CPU user time (s): 0.189971
CPU system time (s): 0.001999
CPU usage (%): 100.412
Max. virtual memory (cumulated for all children) (KiB): 455104

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.189971
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= 216
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= 2
involuntary context switches= 1

runsolver used 0 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node77 at 2009-03-31 01:36:41
IDJOB=1523121
IDBENCH=70438
IDSOLVER=530
FILE ID=node77/1523121-1238456201
PBS_JOBID= 9061678
Free space on /tmp= 66552 MiB

SOLVER NAME= Hybrid2 2009-03-22
BENCH NAME= SAT09/RANDOM/MEDIUM/5SAT/SATISFIABLE/100/unif-k5-r21.3-v100-c2130-S1707873242-085.cnf
COMMAND LINE= HOME/Hybrid2 BENCHNAME RANDOMSEED
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1523121-1238456201/watcher-1523121-1238456201 -o /tmp/evaluation-result-1523121-1238456201/solver-1523121-1238456201 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/Hybrid2 HOME/instance-1523121-1238456201.cnf 2144920049

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 50fb19065f42fe4981158c7f4fb4e31f
RANDOM SEED=2144920049

node77.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/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.230
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.230
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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1671920 kB
Buffers:         67196 kB
Cached:         227876 kB
SwapCached:       9160 kB
Active:         133808 kB
Inactive:       174592 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1671920 kB
SwapTotal:     4192956 kB
SwapFree:      4175504 kB
Dirty:            4612 kB
Writeback:           0 kB
Mapped:          17580 kB
Slab:            60748 kB
Committed_AS:  2681436 kB
PageTables:       1984 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= 66548 MiB
End job on node77 at 2009-03-31 01:36:42