Trace number 461781

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, and are wall clock time (not CPU 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
minicirc 2007-05-17? (problem) 0.183971 0.183016

General information on the benchmark

Nameadditional-aig/tip-k-ind-aigs-o1234g/
O3/texas.parsesys^2.E.aig
MD5SUM995d875eaa398649ddb51e55b549e2af
Bench CategoryALL (all instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.021996
SatisfiableNO
(Un)Satisfiability was proved

Solver Data (download as text)

0.08/0.18	c ____________________________________________________________________________________
0.08/0.18	c !! Parsing                         :      813 ANDs     26 PIs   (CPU-Time   -0.00 s)
0.08/0.18	c ____________________________________________________________________________________
0.08/0.18	c !! Initial simplification          :      808 ANDs     26 PIs   (CPU-Time    0.00 s)
0.08/0.18	c >>     Top conjunction: 6 POs
0.08/0.18	c ____________________________________________________________________________________
0.08/0.18	c !! DAG-aware minimization begins   : 
0.08/0.18	c >>     Strashing:
0.08/0.18	c >>     Minimizing:
0.08/0.18	c >>     progress        0/     808
>>     Reduction in #ANDs: 85.15 %
0.08/0.18	c >>     Core shrink time  : 0.02 s
0.08/0.18	c >>     Globally redundant: 0
0.08/0.18	c >> DAG-aware minimization completed:      120 ANDs     26 PIs   (CPU-Time    0.02 s)
0.08/0.18	c ____________________________________________________________________________________
0.08/0.18	c !! Tech-mapping for CNF begins     : 
0.08/0.18	c >>     Cut statistics:  (total = 703, avg = 5.9, max = 15)          
0.08/0.18	c >>        0:      189 clauses   (CPU Time 0.00)
0.08/0.18	c >>        1:      168 clauses   (CPU Time 0.00)
0.08/0.18	c >>        2:      170 clauses   (CPU Time 0.00)
0.08/0.18	c >>        3:      170 clauses   (CPU Time 0.00)
0.08/0.18	c >>     Core techmap time: 0.00 s
0.08/0.18	c >> Tech-mapping for CNF completed  :       35 LUTs     26 PIs   (CPU-Time    0.00 s)
0.08/0.18	c ____________________________________________________________________________________
0.08/0.18	c !! Producing initial SAT-problem   :      169 clauses           (CPU-Time    0.00 s)
0.08/0.18	c ____________________________________________________________________________________
0.08/0.18	c !! Running SAT...
0.08/0.18	c 
0.08/0.18	c ============================[After Simplification]=============================
0.08/0.18	c |  Number of variables:  62                                                   |
0.08/0.18	c |  Number of clauses:    351                                                  |
0.08/0.18	c restarts         : 0
0.08/0.18	c conflicts        : 0           
0.08/0.18	c decisions        : 0            ( nan % random)
0.08/0.18	c propagations     : 10          
0.08/0.18	c conflict literals: 0            ( nan % deleted)

Verifier Data (download as text)

No verification made

Watcher Data (download as text)

runsolver version 3.2.4 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node12/watcher-461781-1179406288 -o ROOT/results/node12/solver-461781-1179406288 -C 1200 -W 1800 -M 1800 --output-limit 1,15 minicirc.bash /tmp/evaluation/461781-1179406288/instance-461781-1179406288.aig 

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.43 0.12 0.06 3/77 18532
/proc/meminfo: memFree=1649704/2055920 swapFree=4154884/4192956
[pid=18532] ppid=18530 vsize=5352 CPUtime=0
/proc/18532/stat : 18532 (minicirc.bash) S 18530 18532 18360 0 -1 4194304 281 0 0 0 0 0 0 0 18 0 1 0 416666178 5480448 223 18446744073709551615 4194304 4889804 548682069264 18446744073709551615 252429525828 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/18532/statm: 1338 223 186 169 0 49 0
[pid=18533] ppid=18532 vsize=9972 CPUtime=0
/proc/18533/stat : 18533 (minicirc.linux3) R 18532 18532 18360 0 -1 4194304 158 0 0 0 0 0 0 0 19 0 1 0 416666178 10211328 133 18446744073709551615 134512640 135636928 4294956784 18446744073709551615 134969235 0 0 4096 17507 0 0 0 17 1 0 0
/proc/18533/statm: 2493 133 45 274 0 2008 0
[pid=18534] ppid=18532 vsize=2504 CPUtime=0
/proc/18534/stat : 18534 (miniadapter.pl) R 18532 18532 18360 0 -1 4194304 50 0 0 0 0 0 0 0 21 0 1 0 416666178 2564096 26 18446744073709551615 4194304 4206940 548682069472 18446744073709551615 252426908949 0 0 4096 0 0 0 0 17 1 0 0
/proc/18534/statm: 626 26 19 3 0 5 0

[startup+0.045323 s]
/proc/loadavg: 0.43 0.12 0.06 3/77 18532
/proc/meminfo: memFree=1649704/2055920 swapFree=4154884/4192956
[pid=18532] ppid=18530 vsize=5352 CPUtime=0
/proc/18532/stat : 18532 (minicirc.bash) S 18530 18532 18360 0 -1 4194304 281 0 0 0 0 0 0 0 18 0 1 0 416666178 5480448 223 18446744073709551615 4194304 4889804 548682069264 18446744073709551615 252429525828 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/18532/statm: 1338 223 186 169 0 49 0
[pid=18533] ppid=18532 vsize=10260 CPUtime=0.03
/proc/18533/stat : 18533 (minicirc.linux3) R 18532 18532 18360 0 -1 4194304 948 0 0 0 3 0 0 0 19 0 1 0 416666178 10506240 891 18446744073709551615 134512640 135636928 4294956784 18446744073709551615 134696128 0 0 4096 17507 0 0 0 17 1 0 0
/proc/18533/statm: 2565 891 71 274 0 2080 0
[pid=18534] ppid=18532 vsize=12268 CPUtime=0
/proc/18534/stat : 18534 (miniadapter.pl) S 18532 18532 18360 0 -1 4194304 378 0 0 0 0 0 0 0 21 0 1 0 416666178 12562432 337 18446744073709551615 4194304 4206940 548682069472 18446744073709551615 252438425698 0 0 4224 0 18446744071563648864 0 0 17 0 0 0
/proc/18534/statm: 3067 337 262 3 0 167 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 27880

[startup+0.101325 s]
/proc/loadavg: 0.43 0.12 0.06 3/77 18532
/proc/meminfo: memFree=1649704/2055920 swapFree=4154884/4192956
[pid=18532] ppid=18530 vsize=5352 CPUtime=0
/proc/18532/stat : 18532 (minicirc.bash) S 18530 18532 18360 0 -1 4194304 281 0 0 0 0 0 0 0 18 0 1 0 416666178 5480448 223 18446744073709551615 4194304 4889804 548682069264 18446744073709551615 252429525828 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/18532/statm: 1338 223 186 169 0 49 0
[pid=18533] ppid=18532 vsize=10448 CPUtime=0.08
/proc/18533/stat : 18533 (minicirc.linux3) R 18532 18532 18360 0 -1 4194304 2153 0 0 0 8 0 0 0 19 0 1 0 416666178 10698752 2095 18446744073709551615 134512640 135636928 4294956784 18446744073709551615 134695678 0 0 4096 17507 0 0 0 17 1 0 0
/proc/18533/statm: 2612 2096 71 274 0 2127 0
[pid=18534] ppid=18532 vsize=12268 CPUtime=0
/proc/18534/stat : 18534 (miniadapter.pl) S 18532 18532 18360 0 -1 4194304 378 0 0 0 0 0 0 0 21 0 1 0 416666178 12562432 337 18446744073709551615 4194304 4206940 548682069472 18446744073709551615 252438425698 0 0 4224 0 18446744071563648864 0 0 17 0 0 0
/proc/18534/statm: 3067 337 262 3 0 167 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 28068

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

Child status: 0
Real time (s): 0.183016
CPU time (s): 0.183971
CPU user time (s): 0.12998
CPU system time (s): 0.053991
CPU usage (%): 100.522
Max. virtual memory (cumulated for all children) (KiB): 28068

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.12998
system time used= 0.053991
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3247
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= 38
involuntary context switches= 7

runsolver used 0.001999 second user time and 0.002999 second system time

The end

Launcher Data (download as text)

Begin job on node12 on Thu May 17 12:51:28 UTC 2007

IDJOB= 461781
IDBENCH= 48644
IDSOLVER= 205
FILE ID= node12/461781-1179406288

PBS_JOBID= 5292828

Free space on /tmp= 66529 MiB

SOLVER NAME= minicirc 2007-05-17
BENCH NAME= HOME/pub/bench/AIG07/additional-aig/tip-k-ind-aigs-o1234g/O3/texas.parsesys^2.E.aig
COMMAND LINE= minicirc.bash /tmp/evaluation/461781-1179406288/instance-461781-1179406288.aig
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node12/watcher-461781-1179406288 -o ROOT/results/node12/solver-461781-1179406288 -C 1200 -W 1800 -M 1800 --output-limit 1,15  minicirc.bash /tmp/evaluation/461781-1179406288/instance-461781-1179406288.aig

META MD5SUM SOLVER= 5a68a0730754c919c3e4a8ed70e49cdc
MD5SUM BENCH=  995d875eaa398649ddb51e55b549e2af

RANDOM SEED= 584755848

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node12.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.239
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.239
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:       1649992 kB
Buffers:         49044 kB
Cached:         258036 kB
SwapCached:      17756 kB
Active:         113808 kB
Inactive:       218148 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1649992 kB
SwapTotal:     4192956 kB
SwapFree:      4154884 kB
Dirty:            4744 kB
Writeback:           0 kB
Mapped:          30304 kB
Slab:            59452 kB
Committed_AS: 11192292 kB
PageTables:       1792 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= 66519 MiB

End job on node12 on Thu May 17 12:51:28 UTC 2007