Trace number 1785803

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
SApperloT baseUNSAT 0.134978 0.135789

General information on the benchmark

NameCRAFTED/modcircuits/
owp_4vars_5gates.cnf
MD5SUMfe245e5f46bcc987fd412946151b9c92
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.097984
Satisfiable
(Un)Satisfiability was proved
Number of variables267
Number of clauses23747
Sum of the clauses size136362
Maximum clause length19
Minimum clause length1
Number of clauses of size 164
Number of clauses of size 2700
Number of clauses of size 31
Number of clauses of size 4563
Number of clauses of size 51926
Number of clauses of size over 520493

Solver Data 

0.10/0.13	
0.10/0.13	s UNSATISFIABLE

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-1785803-1241932185/watcher-1785803-1241932185 -o /tmp/evaluation-result-1785803-1241932185/solver-1785803-1241932185 -C 5000 -W 6000 -M 1800 --output-limit 1,128 HOME/SApperloT-base -seed=144146616 HOME/instance-1785803-1241932185.cnf 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 5000 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 5030 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 6000 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 134217728 bytes. The first 1048576 bytes and the last 133169152 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 31127
/proc/meminfo: memFree=1512320/2055920 swapFree=4191900/4192956
[pid=31127] ppid=31125 vsize=1580 CPUtime=0
/proc/31127/stat : 31127 (SApperloT-base) R 31125 31127 28094 0 -1 4194304 183 0 0 0 0 0 0 0 18 0 1 0 221246107 1617920 167 1992294400 134512640 135674940 4294956208 18446744073709551615 135172670 0 0 4096 0 0 0 0 17 1 0 0
/proc/31127/statm: 395 167 90 283 0 109 0

[startup+0.092883 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 31127
/proc/meminfo: memFree=1512320/2055920 swapFree=4191900/4192956
[pid=31127] ppid=31125 vsize=2772 CPUtime=0.09
/proc/31127/stat : 31127 (SApperloT-base) R 31125 31127 28094 0 -1 4194304 498 0 0 0 9 0 0 0 18 0 1 0 221246107 2838528 481 1992294400 134512640 135674940 4294956208 18446744073709551615 135113206 0 0 4096 0 0 0 0 17 1 0 0
/proc/31127/statm: 693 481 98 283 0 407 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2772

[startup+0.102883 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 31127
/proc/meminfo: memFree=1512320/2055920 swapFree=4191900/4192956
[pid=31127] ppid=31125 vsize=2772 CPUtime=0.1
/proc/31127/stat : 31127 (SApperloT-base) R 31125 31127 28094 0 -1 4194304 511 0 0 0 10 0 0 0 18 0 1 0 221246107 2838528 494 1992294400 134512640 135674940 4294956208 18446744073709551615 135113206 0 0 4096 0 0 0 0 17 1 0 0
/proc/31127/statm: 693 494 98 283 0 407 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 2772

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

Child status: 0
Real time (s): 0.135789
CPU time (s): 0.134978
CPU user time (s): 0.133979
CPU system time (s): 0.000999
CPU usage (%): 99.4028
Max. virtual memory (cumulated for all children) (KiB): 2772

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.133979
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= 528
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.002999 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node62 at 2009-05-10 07:09:45
IDJOB=1785803
IDBENCH=71149
IDSOLVER=642
FILE ID=node62/1785803-1241932185
PBS_JOBID= 9264923
Free space on /tmp= 66472 MiB

SOLVER NAME= SApperloT base
BENCH NAME= SAT09/CRAFTED/modcircuits/owp_4vars_5gates.cnf
COMMAND LINE= HOME/SApperloT-base -seed=RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1785803-1241932185/watcher-1785803-1241932185 -o /tmp/evaluation-result-1785803-1241932185/solver-1785803-1241932185 -C 5000 -W 6000 -M 1800 --output-limit 1,128  HOME/SApperloT-base -seed=144146616 HOME/instance-1785803-1241932185.cnf

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

MD5SUM BENCH= fe245e5f46bcc987fd412946151b9c92
RANDOM SEED=144146616

node62.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.220
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.220
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:       1512800 kB
Buffers:         53628 kB
Cached:         414692 kB
SwapCached:        268 kB
Active:         129728 kB
Inactive:       353424 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1512800 kB
SwapTotal:     4192956 kB
SwapFree:      4191900 kB
Dirty:            2320 kB
Writeback:           0 kB
Mapped:          23368 kB
Slab:            45776 kB
Committed_AS:   558024 kB
PageTables:       1456 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264960 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66468 MiB
End job on node62 at 2009-05-10 07:09:46