Trace number 1720883

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-03? 0.551915 0.552538

General information on the benchmark

Nameeen-tip-sat-texas-tp-5e.cnf
MD5SUM5bf390b945bda57e276dac6d13ea27f6
Bench CategoryAPPLICATION (applications instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.12198
Satisfiable
(Un)Satisfiability was proved
Number of variables17985
Number of clauses52128
Sum of the clauses size123454
Maximum clause length15
Minimum clause length1
Number of clauses of size 115
Number of clauses of size 232912
Number of clauses of size 319200
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 51

Solver Data 

0.00/0.00	c MoRsat version 1.02 2009.03 
0.29/0.32	c atom#=17985 clause#=52128 total literals=123454 
0.29/0.32	c before shortening average=3.000000, #XOR clauses=17 
0.29/0.32	c after shortening average=3.000000 #XOR clauses=17 
0.49/0.55	c 
0.49/0.55	c CNF stats: (17985 vars, 52128 clauses) 
0.49/0.55	c Decisions: 105 
0.49/0.55	c Conflicts: 17 
0.49/0.55	c 
0.49/0.55	s UNKNOWN
0.49/0.55	c Running time: 0.48792 seconds

Verifier Data 

ERROR: Unexpected answer ! (SATISFIABLE/UNSATISFIABLE expected)
Got answer: UNKNOWN

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1720883-1240660699/watcher-1720883-1240660699 -o /tmp/evaluation-result-1720883-1240660699/solver-1720883-1240660699 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/MoRsat HOME/instance-1720883-1240660699.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.98 0.99 3/64 19165
/proc/meminfo: memFree=1688640/2055920 swapFree=4192812/4192956
[pid=19165] ppid=19163 vsize=2756 CPUtime=0
/proc/19165/stat : 19165 (MoRsat) R 19163 19165 18669 0 -1 4194304 138 0 0 0 0 0 0 0 18 0 1 0 94103580 2822144 122 1992294400 134512640 135679800 4294956224 18446744073709551615 135172366 0 0 4096 1026 0 0 0 17 1 0 0
/proc/19165/statm: 689 122 96 284 0 402 0

[startup+0.0886231 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 19165
/proc/meminfo: memFree=1688640/2055920 swapFree=4192812/4192956
[pid=19165] ppid=19163 vsize=3036 CPUtime=0.08
/proc/19165/stat : 19165 (MoRsat) R 19163 19165 18669 0 -1 4194304 355 0 0 0 8 0 0 0 18 0 1 0 94103580 3108864 337 1992294400 134512640 135679800 4294956224 18446744073709551615 134560785 0 0 4096 1026 0 0 0 17 1 0 0
/proc/19165/statm: 759 337 101 284 0 472 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 3036

[startup+0.101624 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 19165
/proc/meminfo: memFree=1688640/2055920 swapFree=4192812/4192956
[pid=19165] ppid=19163 vsize=3036 CPUtime=0.09
/proc/19165/stat : 19165 (MoRsat) R 19163 19165 18669 0 -1 4194304 355 0 0 0 9 0 0 0 18 0 1 0 94103580 3108864 337 1992294400 134512640 135679800 4294956224 18446744073709551615 134560506 0 0 4096 1026 0 0 0 17 1 0 0
/proc/19165/statm: 759 337 101 284 0 472 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3036

[startup+0.301667 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 19165
/proc/meminfo: memFree=1688640/2055920 swapFree=4192812/4192956
[pid=19165] ppid=19163 vsize=2628 CPUtime=0.29
/proc/19165/stat : 19165 (MoRsat) R 19163 19165 18669 0 -1 4194304 782 0 0 0 29 0 0 0 19 0 1 0 94103580 2691072 444 1992294400 134512640 135679800 4294956224 18446744073709551615 134564635 0 0 4096 1026 0 0 0 17 1 0 0
/proc/19165/statm: 657 444 107 284 0 370 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 2628

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

[startup+0.50171 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 19165
/proc/meminfo: memFree=1688640/2055920 swapFree=4192812/4192956
[pid=19165] ppid=19163 vsize=4300 CPUtime=0.49
/proc/19165/stat : 19165 (MoRsat) R 19163 19165 18669 0 -1 4194304 1280 0 0 0 49 0 0 0 20 0 1 0 94103580 4403200 607 1992294400 134512640 135679800 4294956224 18446744073709551615 135089578 0 0 4096 1026 0 0 0 17 1 0 0
/proc/19165/statm: 1075 607 115 284 0 788 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 4300

Child status: 0
Real time (s): 0.552538
CPU time (s): 0.551915
CPU user time (s): 0.539917
CPU system time (s): 0.011998
CPU usage (%): 99.8873
Max. virtual memory (cumulated for all children) (KiB): 4416

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.539917
system time used= 0.011998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1392
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.003999 second user time and 0.004999 second system time

The end

Launcher Data 

Begin job on node10 at 2009-04-25 13:58:19
IDJOB=1720883
IDBENCH=69643
IDSOLVER=502
FILE ID=node10/1720883-1240660699
PBS_JOBID= 9186531
Free space on /tmp= 66340 MiB

SOLVER NAME= MoRsat 2009-03-03
BENCH NAME= SAT_RACE08/cnf/een-tip-sat-texas-tp-5e.cnf
COMMAND LINE= HOME/MoRsat BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1720883-1240660699/watcher-1720883-1240660699 -o /tmp/evaluation-result-1720883-1240660699/solver-1720883-1240660699 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/MoRsat HOME/instance-1720883-1240660699.cnf

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

MD5SUM BENCH= 5bf390b945bda57e276dac6d13ea27f6
RANDOM SEED=1111208270

node10.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.263
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.263
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:       1689056 kB
Buffers:         16424 kB
Cached:         274548 kB
SwapCached:          0 kB
Active:          73444 kB
Inactive:       231532 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1689056 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2316 kB
Writeback:           0 kB
Mapped:          23712 kB
Slab:            47960 kB
Committed_AS:   334248 kB
PageTables:       1372 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= 66336 MiB
End job on node10 at 2009-04-25 13:58:20