Trace number 1521475

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
MoRsat 2009-03-03SAT 1.3258 1.32671

General information on the benchmark

NameRANDOM/MEDIUM/5SAT/SATISFIABLE/100/
unif-k5-r21.3-v100-c2130-S748216286-061.cnf
MD5SUM2754b3d0d46124bc4b807ae18c388fa5
Bench CategoryRANDOM (random instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.093985
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.00/0.00	c MoRsat version 1.02 2009.03 
0.07/0.07	c atom#=100 clause#=2130 total literals=10650 
1.29/1.32	c Solution Verified
1.29/1.32	c CNF stats: (100 vars, 2130 clauses) 
1.29/1.32	c 
1.29/1.32	s SATISFIABLE
1.29/1.32	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
1.29/1.32	c 
1.29/1.32	c Running time: 1.32080 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-1521475-1238358531/watcher-1521475-1238358531 -o /tmp/evaluation-result-1521475-1238358531/solver-1521475-1238358531 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/MoRsat HOME/instance-1521475-1238358531.cnf 

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.92 0.97 0.90 2/64 27832
/proc/meminfo: memFree=1080464/2055920 swapFree=4176868/4192956
[pid=27832] ppid=27830 vsize=1324 CPUtime=0
/proc/27832/stat : 27832 (MoRsat) R 27830 27832 27703 0 -1 4194304 140 0 0 0 0 0 0 0 18 0 1 0 1108515521 1355776 123 1992294400 134512640 135679800 4294956240 18446744073709551615 135173409 0 0 4096 1026 0 0 0 17 1 0 0
/proc/27832/statm: 331 126 101 284 0 44 0

[startup+0.078386 s]
/proc/loadavg: 0.92 0.97 0.90 2/64 27832
/proc/meminfo: memFree=1080464/2055920 swapFree=4176868/4192956
[pid=27832] ppid=27830 vsize=1468 CPUtime=0.07
/proc/27832/stat : 27832 (MoRsat) R 27830 27832 27703 0 -1 4194304 207 0 0 0 7 0 0 0 18 0 1 0 1108515521 1503232 183 1992294400 134512640 135679800 4294956240 18446744073709551615 134532944 0 0 4096 1026 0 0 0 17 1 0 0
/proc/27832/statm: 367 183 110 284 0 80 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 1468

[startup+0.101388 s]
/proc/loadavg: 0.92 0.97 0.90 2/64 27832
/proc/meminfo: memFree=1080464/2055920 swapFree=4176868/4192956
[pid=27832] ppid=27830 vsize=1612 CPUtime=0.09
/proc/27832/stat : 27832 (MoRsat) R 27830 27832 27703 0 -1 4194304 245 0 0 0 9 0 0 0 18 0 1 0 1108515521 1650688 221 1992294400 134512640 135679800 4294956240 18446744073709551615 134574874 0 0 4096 1026 0 0 0 17 1 0 0
/proc/27832/statm: 403 221 114 284 0 116 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 1612

[startup+0.301406 s]
/proc/loadavg: 0.92 0.97 0.90 2/64 27832
/proc/meminfo: memFree=1080464/2055920 swapFree=4176868/4192956
[pid=27832] ppid=27830 vsize=1612 CPUtime=0.29
/proc/27832/stat : 27832 (MoRsat) R 27830 27832 27703 0 -1 4194304 245 0 0 0 29 0 0 0 19 0 1 0 1108515521 1650688 221 1992294400 134512640 135679800 4294956240 18446744073709551615 134574499 0 0 4096 1026 0 0 0 17 1 0 0
/proc/27832/statm: 403 221 114 284 0 116 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 1612

[startup+0.701443 s]
/proc/loadavg: 0.92 0.97 0.90 2/64 27832
/proc/meminfo: memFree=1080464/2055920 swapFree=4176868/4192956
[pid=27832] ppid=27830 vsize=1612 CPUtime=0.69
/proc/27832/stat : 27832 (MoRsat) R 27830 27832 27703 0 -1 4194304 245 0 0 0 69 0 0 0 23 0 1 0 1108515521 1650688 221 1992294400 134512640 135679800 4294956240 18446744073709551615 134577374 0 0 4096 1026 0 0 0 17 1 0 0
/proc/27832/statm: 403 221 114 284 0 116 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 1612

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

[startup+1.10648 s]
/proc/loadavg: 0.92 0.97 0.90 2/65 27833
/proc/meminfo: memFree=1080008/2055920 swapFree=4176868/4192956
[pid=27832] ppid=27830 vsize=1612 CPUtime=1.1
/proc/27832/stat : 27832 (MoRsat) R 27830 27832 27703 0 -1 4194304 245 0 0 0 110 0 0 0 25 0 1 0 1108515521 1650688 221 1992294400 134512640 135679800 4294956240 18446744073709551615 134574509 0 0 4096 1026 0 0 0 17 1 0 0
/proc/27832/statm: 403 221 114 284 0 116 0
Current children cumulated CPU time (s) 1.1
Current children cumulated vsize (KiB) 1612

[startup+1.3015 s]
/proc/loadavg: 0.92 0.97 0.90 2/65 27833
/proc/meminfo: memFree=1080008/2055920 swapFree=4176868/4192956
[pid=27832] ppid=27830 vsize=1612 CPUtime=1.29
/proc/27832/stat : 27832 (MoRsat) R 27830 27832 27703 0 -1 4194304 245 0 0 0 129 0 0 0 25 0 1 0 1108515521 1650688 221 1992294400 134512640 135679800 4294956240 18446744073709551615 134573582 0 0 4096 1026 0 0 0 17 1 0 0
/proc/27832/statm: 403 221 114 284 0 116 0
Current children cumulated CPU time (s) 1.29
Current children cumulated vsize (KiB) 1612

Child status: 10
Real time (s): 1.32671
CPU time (s): 1.3258
CPU user time (s): 1.3248
CPU system time (s): 0.000999
CPU usage (%): 99.9316
Max. virtual memory (cumulated for all children) (KiB): 1612

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.3248
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= 249
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= 2

runsolver used 0.005999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node48 at 2009-03-29 22:28:51
IDJOB=1521475
IDBENCH=70440
IDSOLVER=502
FILE ID=node48/1521475-1238358531
PBS_JOBID= 9061182
Free space on /tmp= 66464 MiB

SOLVER NAME= MoRsat 2009-03-03
BENCH NAME= SAT09/RANDOM/MEDIUM/5SAT/SATISFIABLE/100/unif-k5-r21.3-v100-c2130-S748216286-061.cnf
COMMAND LINE= HOME/MoRsat BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1521475-1238358531/watcher-1521475-1238358531 -o /tmp/evaluation-result-1521475-1238358531/solver-1521475-1238358531 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/MoRsat HOME/instance-1521475-1238358531.cnf

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

MD5SUM BENCH= 2754b3d0d46124bc4b807ae18c388fa5
RANDOM SEED=924081642

node48.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.236
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.236
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:       1080880 kB
Buffers:         89980 kB
Cached:         787704 kB
SwapCached:      10192 kB
Active:         165296 kB
Inactive:       724168 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1080880 kB
SwapTotal:     4192956 kB
SwapFree:      4176868 kB
Dirty:            1440 kB
Writeback:           0 kB
Mapped:          17432 kB
Slab:            71508 kB
Committed_AS:  2511440 kB
PageTables:       1376 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= 66464 MiB
End job on node48 at 2009-03-29 22:28:53