Trace number 1733852

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
LySAT i/2009-03-20UNSAT 0.380941 0.384729

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.06099
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.00/0.00	c Parsing...
0.00/0.03	c ==============================================================================
0.00/0.03	c |           |     ORIGINAL     |              LEARNT              |          |
0.00/0.03	c | Conflicts | Clauses Literals |   Limit Clauses Literals  Lit/Cl | Progress |
0.00/0.03	c ==============================================================================
0.00/0.03	c |         0 |   23683   136298 |    7104       0        0     nan |  0.000 % |
0.00/0.28	c |         0 |    9529    50535 |      --       0       --      -- |     --   | -2634/-7683
0.00/0.28	c ==============================================================================
0.00/0.28	c Result  :   #vars: 165   #clauses: 9529   #literals: 50535
0.00/0.28	c CPU time:   0.268959 s
0.00/0.28	c ==============================================================================
0.00/0.30	c lySAT 0.1
0.00/0.30	c minisat core +  additionnal features
0.00/0.30	c ============================[ Problem Statistics ]=============================
0.00/0.30	c |                                                                             |
0.00/0.30	c |  Number of variables:  165                                                  |
0.00/0.30	c |  Number of clauses:    9529                                                 |
0.28/0.30	c |  Parsing time:         0.01         s                                       |
0.28/0.38	c restarts              : 112
0.28/0.38	c conflicts             : 2462           (30400 /sec)
0.28/0.38	c decisions             : 6152           (34.72 % random) (75963 /sec)
0.28/0.38	c euip                  : 214         
0.28/0.38	c propagations          : 59438          (733920 /sec)
0.28/0.38	c conflict literals     : 18822          (20.91 % deleted)
0.28/0.38	c Memory used           : 2.65 MB
0.28/0.38	c CPU time              : 0.080987 s
0.28/0.38	c 
0.28/0.38	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-1733852-1240793252/watcher-1733852-1240793252 -o /tmp/evaluation-result-1733852-1240793252/solver-1733852-1240793252 -C 1200 -W 1800 -M 1800 --output-limit 1,15 lysat.sh HOME/instance-1733852-1240793252.cnf i 

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.92 1.85 1.52 3/64 24806
/proc/meminfo: memFree=1765416/2055920 swapFree=4181732/4192956
[pid=24806] ppid=24804 vsize=5212 CPUtime=0
/proc/24806/stat : 24806 (lysat.sh) R 24804 24806 24546 0 -1 4194304 79 0 0 0 0 0 0 0 20 0 1 0 107352707 5337088 53 1992294400 4194304 4889804 548682068800 18446744073709551615 4291344 0 0 4096 0 0 0 0 17 1 0 0
/proc/24806/statm: 1303 63 46 169 0 14 0

[startup+0.0634991 s]
/proc/loadavg: 1.92 1.85 1.52 3/64 24806
/proc/meminfo: memFree=1765416/2055920 swapFree=4181732/4192956
[pid=24806] ppid=24804 vsize=5356 CPUtime=0
/proc/24806/stat : 24806 (lysat.sh) S 24804 24806 24546 0 -1 4194304 286 0 0 0 0 0 0 0 20 0 1 0 107352707 5484544 235 1992294400 4194304 4889804 548682068800 18446744073709551615 273653752644 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/24806/statm: 1339 235 195 169 0 50 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5356

[startup+0.101496 s]
/proc/loadavg: 1.92 1.85 1.52 3/64 24806
/proc/meminfo: memFree=1765416/2055920 swapFree=4181732/4192956
[pid=24806] ppid=24804 vsize=5356 CPUtime=0
/proc/24806/stat : 24806 (lysat.sh) S 24804 24806 24546 0 -1 4194304 286 0 0 0 0 0 0 0 20 0 1 0 107352707 5484544 235 1992294400 4194304 4889804 548682068800 18446744073709551615 273653752644 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/24806/statm: 1339 235 195 169 0 50 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5356

[startup+0.301513 s]
/proc/loadavg: 1.92 1.85 1.52 3/64 24806
/proc/meminfo: memFree=1765416/2055920 swapFree=4181732/4192956
[pid=24806] ppid=24804 vsize=5356 CPUtime=0.28
/proc/24806/stat : 24806 (lysat.sh) S 24804 24806 24546 0 -1 4194304 310 832 0 0 0 0 28 0 16 0 1 0 107352707 5484544 237 1992294400 4194304 4889804 548682068800 18446744073709551615 273653752644 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/24806/statm: 1339 237 195 169 0 50 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 5356

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

Child status: 20
Real time (s): 0.384729
CPU time (s): 0.380941
CPU user time (s): 0.368943
CPU system time (s): 0.011998
CPU usage (%): 99.0154
Max. virtual memory (cumulated for all children) (KiB): 5356

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.368943
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= 1666
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= 11
involuntary context switches= 24

runsolver used 0.000999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node52 at 2009-04-27 02:47:32
IDJOB=1733852
IDBENCH=71149
IDSOLVER=511
FILE ID=node52/1733852-1240793252
PBS_JOBID= 9187330
Free space on /tmp= 66232 MiB

SOLVER NAME= LySAT i/2009-03-20
BENCH NAME= SAT09/CRAFTED/modcircuits/owp_4vars_5gates.cnf
COMMAND LINE= lysat.sh BENCHNAME i
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1733852-1240793252/watcher-1733852-1240793252 -o /tmp/evaluation-result-1733852-1240793252/solver-1733852-1240793252 -C 1200 -W 1800 -M 1800 --output-limit 1,15  lysat.sh HOME/instance-1733852-1240793252.cnf i

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

MD5SUM BENCH= fe245e5f46bcc987fd412946151b9c92
RANDOM SEED=1417953717

node52.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.214
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.214
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:       1765896 kB
Buffers:         28196 kB
Cached:         183604 kB
SwapCached:       5120 kB
Active:          31088 kB
Inactive:       188632 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1765896 kB
SwapTotal:     4192956 kB
SwapFree:      4181732 kB
Dirty:            2776 kB
Writeback:           0 kB
Mapped:          13976 kB
Slab:            56276 kB
Committed_AS:   438764 kB
PageTables:       1476 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= 66232 MiB
End job on node52 at 2009-04-27 02:47:33