Trace number 461314

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
aigsat-wc 2007-05-15? (problem) 0.084986 0.08754

General information on the benchmark

Nameadditional-aig/pico-java/
prop06_len41_step.aig
MD5SUM7ac4807797b684b58ed1ebf9eb586ac1
Bench CategoryALL (all instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark129.591
SatisfiableNO
(Un)Satisfiability was proved

Solver Data (download as text)

0.02/0.08	c file: /tmp/evaluation/461314-1179252882/instance-461314-1179252882.aig
0.02/0.08	c Reading aig format..
0.02/0.08	c MAXVAR  301553
0.02/0.08	c INPUTS  5233
0.02/0.08	c LATCHES 0
0.02/0.08	c OUTPUTS 944
0.02/0.08	c AND     296320
0.02/0.08	c More than one output 
0.02/0.08	Exception: c Not a structural aig. Expected zero latches and atmost one output 
0.02/0.08	.

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/node52/watcher-461314-1179252882 -o ROOT/results/node52/solver-461314-1179252882 -C 1200 -W 1800 -M 1800 --output-limit 1,15 -S 1 /tmp/evaluation/461314-1179252882/aigsat-wc /tmp/evaluation/461314-1179252882/instance-461314-1179252882.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 Stack size limit: 1048576 KiB
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: 1048576 KiB


[startup+0 s]
/proc/loadavg: 0.91 0.85 0.73 3/64 5320
/proc/meminfo: memFree=1821316/2055920 swapFree=4183124/4192956
[pid=5320] ppid=5318 vsize=3676 CPUtime=0
/proc/5320/stat : 5320 (aigsat-wc) R 5318 5320 5166 0 -1 0 442 249 0 0 0 0 0 0 18 0 1 0 280133303 3764224 421 18446744073709551615 134512640 135716322 4294956672 18446744073709551615 135242916 0 0 4096 35 0 0 0 17 0 0 0
/proc/5320/statm: 919 432 124 293 0 620 0

[startup+0.040224 s]
/proc/loadavg: 0.91 0.85 0.73 3/64 5320
/proc/meminfo: memFree=1821316/2055920 swapFree=4183124/4192956
[pid=5320] ppid=5318 vsize=7224 CPUtime=0.02
/proc/5320/stat : 5320 (aigsat-wc) R 5318 5320 5166 0 -1 0 1638 249 0 0 2 0 0 0 19 0 1 0 280133303 7397376 1617 18446744073709551615 134512640 135716322 4294956672 18446744073709551615 135276893 0 0 4096 35 0 0 0 17 0 0 0
/proc/5320/statm: 1806 1617 125 293 0 1507 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 7224

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

[startup+0.040224 s]
/proc/loadavg: 0.91 0.85 0.73 3/64 5320
/proc/meminfo: memFree=1821316/2055920 swapFree=4183124/4192956
[pid=5320] ppid=5318 vsize=7224 CPUtime=0.02
/proc/5320/stat : 5320 (aigsat-wc) R 5318 5320 5166 0 -1 0 1638 249 0 0 2 0 0 0 19 0 1 0 280133303 7397376 1617 18446744073709551615 134512640 135716322 4294956672 18446744073709551615 135276893 0 0 4096 35 0 0 0 17 0 0 0
/proc/5320/statm: 1806 1617 125 293 0 1507 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 7224

Child status: 0
Real time (s): 0.08754
CPU time (s): 0.084986
CPU user time (s): 0.074988
CPU system time (s): 0.009998
CPU usage (%): 97.0825
Max. virtual memory (cumulated for all children) (KiB): 7224

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

runsolver used 0 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node52 on Tue May 15 18:14:42 UTC 2007

IDJOB= 461314
IDBENCH= 48673
IDSOLVER= 202
FILE ID= node52/461314-1179252882

PBS_JOBID= 5277193

Free space on /tmp= 66544 MiB

SOLVER NAME= aigsat-wc 2007-05-15
BENCH NAME= HOME/pub/bench/AIG07/additional-aig/pico-java/prop06_len41_step.aig
COMMAND LINE= /tmp/evaluation/461314-1179252882/aigsat-wc /tmp/evaluation/461314-1179252882/instance-461314-1179252882.aig            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node52/watcher-461314-1179252882 -o ROOT/results/node52/solver-461314-1179252882 -C 1200 -W 1800 -M 1800 --output-limit 1,15 -S 1 /tmp/evaluation/461314-1179252882/aigsat-wc /tmp/evaluation/461314-1179252882/instance-461314-1179252882.aig            

META MD5SUM SOLVER= a44537a071ffb1a142b3275181a5083c
MD5SUM BENCH=  7ac4807797b684b58ed1ebf9eb586ac1

RANDOM SEED= 376548991

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node52.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.236
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.236
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:       1821532 kB
Buffers:          4316 kB
Cached:         129456 kB
SwapCached:       3860 kB
Active:          21948 kB
Inactive:       121500 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1821532 kB
SwapTotal:     4192956 kB
SwapFree:      4183124 kB
Dirty:            2460 kB
Writeback:           0 kB
Mapped:          15716 kB
Slab:            76912 kB
Committed_AS:  7346872 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= 66544 MiB

End job on node52 on Tue May 15 18:14:43 UTC 2007