Trace number 1720207

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-03Wrong UNSAT 1.63375 1.63455

General information on the benchmark

Namemizh-sha0-36-4.cnf
MD5SUMf43e1bf70d9ce8021bafd328efc83ae7
Bench CategoryAPPLICATION (applications instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark159.031
Satisfiable
(Un)Satisfiability was proved
Number of variables50073
Number of clauses210235
Sum of the clauses size628383
Maximum clause length4
Minimum clause length1
Number of clauses of size 1177
Number of clauses of size 286992
Number of clauses of size 338042
Number of clauses of size 485024
Number of clauses of size 50
Number of clauses of size over 50

Solver Data

0.00/0.00	c MoRsat version 1.02 2009.03 
1.59/1.63	c atom#=50073 clause#=210235 total literals=628383 
1.59/1.63	c 
1.59/1.63	s UNSATISFIABLE
1.59/1.63	c Running time: 1.30880 seconds 

Verifier Data

No possible verification on an UNSAT instance

Watcher Data

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1720207-1240653649/watcher-1720207-1240653649 -o /tmp/evaluation-result-1720207-1240653649/solver-1720207-1240653649 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/MoRsat HOME/instance-1720207-1240653649.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: 1.83 1.83 1.47 2/65 11920
/proc/meminfo: memFree=1827704/2055920 swapFree=4181068/4192956
[pid=11920] ppid=11918 vsize=4616 CPUtime=0
/proc/11920/stat : 11920 (MoRsat) R 11918 11920 11621 0 -1 4194304 139 0 0 0 0 0 0 0 20 0 1 0 93394533 4726784 123 1992294400 134512640 135679800 4294956224 18446744073709551615 134537519 0 0 4096 1026 0 0 0 17 1 0 0
/proc/11920/statm: 1154 123 96 284 0 867 0

[startup+0.064124 s]
/proc/loadavg: 1.83 1.83 1.47 2/65 11920
/proc/meminfo: memFree=1827704/2055920 swapFree=4181068/4192956
[pid=11920] ppid=11918 vsize=4616 CPUtime=0.06
/proc/11920/stat : 11920 (MoRsat) R 11918 11920 11621 0 -1 4194304 340 0 0 0 6 0 0 0 20 0 1 0 93394533 4726784 324 1992294400 134512640 135679800 4294956224 18446744073709551615 135172366 0 0 4096 1026 0 0 0 17 1 0 0
/proc/11920/statm: 1154 324 96 284 0 867 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 4616

[startup+0.101127 s]
/proc/loadavg: 1.83 1.83 1.47 2/65 11920
/proc/meminfo: memFree=1827704/2055920 swapFree=4181068/4192956
[pid=11920] ppid=11918 vsize=4616 CPUtime=0.09
/proc/11920/stat : 11920 (MoRsat) R 11918 11920 11621 0 -1 4194304 462 0 0 0 9 0 0 0 20 0 1 0 93394533 4726784 446 1992294400 134512640 135679800 4294956224 18446744073709551615 135172366 0 0 4096 1026 0 0 0 17 1 0 0
/proc/11920/statm: 1154 446 96 284 0 867 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 4616

[startup+0.301149 s]
/proc/loadavg: 1.83 1.83 1.47 2/65 11920
/proc/meminfo: memFree=1827704/2055920 swapFree=4181068/4192956
[pid=11920] ppid=11918 vsize=9260 CPUtime=0.29
/proc/11920/stat : 11920 (MoRsat) R 11918 11920 11621 0 -1 4194304 2114 0 0 0 28 1 0 0 22 0 1 0 93394533 9482240 1951 1992294400 134512640 135679800 4294956224 18446744073709551615 134552322 0 0 4096 1026 0 0 0 17 1 0 0
/proc/11920/statm: 2315 1951 103 284 0 2028 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 9260

[startup+0.701194 s]
/proc/loadavg: 1.83 1.83 1.47 2/65 11920
/proc/meminfo: memFree=1827704/2055920 swapFree=4181068/4192956
[pid=11920] ppid=11918 vsize=5420 CPUtime=0.68
/proc/11920/stat : 11920 (MoRsat) R 11918 11920 11621 0 -1 4194304 7975 0 0 0 65 3 0 0 25 0 1 0 93394533 5550080 1041 1992294400 134512640 135679800 4294956224 18446744073709551615 134559641 0 0 4096 1026 0 0 0 17 1 0 0
/proc/11920/statm: 1355 1041 104 284 0 1068 0
Current children cumulated CPU time (s) 0.68
Current children cumulated vsize (KiB) 5420

[startup+1.50128 s]
/proc/loadavg: 1.83 1.83 1.47 2/66 11921
/proc/meminfo: memFree=1823728/2055920 swapFree=4181068/4192956
[pid=11920] ppid=11918 vsize=9188 CPUtime=1.49
/proc/11920/stat : 11920 (MoRsat) R 11918 11920 11621 0 -1 4194304 15861 0 0 0 142 7 0 0 25 0 1 0 93394533 9408512 1927 1992294400 134512640 135679800 4294956224 18446744073709551615 134567892 0 0 4096 1026 0 0 0 17 1 0 0
/proc/11920/statm: 2297 1927 106 284 0 2010 0
Current children cumulated CPU time (s) 1.49
Current children cumulated vsize (KiB) 9188

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

[startup+1.60129 s]
/proc/loadavg: 1.83 1.83 1.47 2/66 11921
/proc/meminfo: memFree=1823728/2055920 swapFree=4181068/4192956
[pid=11920] ppid=11918 vsize=13392 CPUtime=1.59
/proc/11920/stat : 11920 (MoRsat) R 11918 11920 11621 0 -1 4194304 17226 0 0 0 152 7 0 0 25 0 1 0 93394533 13713408 1829 1992294400 134512640 135679800 4294956224 18446744073709551615 134552293 0 0 4096 1026 0 0 0 17 1 0 0
/proc/11920/statm: 3348 1829 107 284 0 3061 0
Current children cumulated CPU time (s) 1.59
Current children cumulated vsize (KiB) 13392

Child status: 20
Real time (s): 1.63455
CPU time (s): 1.63375
CPU user time (s): 1.55076
CPU system time (s): 0.082987
CPU usage (%): 99.9512
Max. virtual memory (cumulated for all children) (KiB): 13392

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

runsolver used 0.004999 second user time and 0.009998 second system time

The end

Launcher Data

Begin job on node86 at 2009-04-25 12:00:49
IDJOB=1720207
IDBENCH=69598
IDSOLVER=502
FILE ID=node86/1720207-1240653649
PBS_JOBID= 9186496
Free space on /tmp= 66160 MiB

SOLVER NAME= MoRsat 2009-03-03
BENCH NAME= SAT_RACE08/cnf/mizh-sha0-36-4.cnf
COMMAND LINE= HOME/MoRsat BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1720207-1240653649/watcher-1720207-1240653649 -o /tmp/evaluation-result-1720207-1240653649/solver-1720207-1240653649 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/MoRsat HOME/instance-1720207-1240653649.cnf

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

MD5SUM BENCH= f43e1bf70d9ce8021bafd328efc83ae7
RANDOM SEED=1124637415

node86.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.213
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.213
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:       1828184 kB
Buffers:          8600 kB
Cached:         145808 kB
SwapCached:       5732 kB
Active:          37664 kB
Inactive:       125528 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1828184 kB
SwapTotal:     4192956 kB
SwapFree:      4181068 kB
Dirty:            5536 kB
Writeback:           0 kB
Mapped:          14060 kB
Slab:            50424 kB
Committed_AS:   328288 kB
PageTables:       1504 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= 66156 MiB
End job on node86 at 2009-04-25 12:00:51