Trace number 461335

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-sp 2007-05-15? (problem) 0.158975 0.160868

General information on the benchmark

Nameadditional-aig/pico-java/
prop02_len66_step.aig
MD5SUM6968c7137f0674678bc86dca099f1103
Bench CategoryALL (all instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark252.326
SatisfiableNO
(Un)Satisfiability was proved

Solver Data (download as text)

0.09/0.15	c file: /tmp/evaluation/461335-1179253026/instance-461335-1179253026.aig
0.09/0.15	c Reading aig format..
0.09/0.15	c MAXVAR  542633
0.09/0.15	c INPUTS  6312
0.09/0.15	c LATCHES 0
0.09/0.15	c OUTPUTS 2344
0.09/0.15	c AND     536321
0.09/0.15	c More than one output 
0.09/0.15	Exception: c Not a structural aig. Expected zero latches and atmost one output 
0.09/0.15	.

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/node70/watcher-461335-1179253026 -o ROOT/results/node70/solver-461335-1179253026 -C 1200 -W 1800 -M 1800 --output-limit 1,15 -S 1 /tmp/evaluation/461335-1179253026/aigsat-sp /tmp/evaluation/461335-1179253026/instance-461335-1179253026.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.85 0.94 0.90 3/64 3429
/proc/meminfo: memFree=1757368/2055920 swapFree=4183904/4192956
[pid=3429] ppid=3427 vsize=5432 CPUtime=0
/proc/3429/stat : 3429 (aigsat-sp) R 3427 3429 2217 0 -1 0 959 0 0 0 0 0 0 0 18 0 1 0 364839971 5562368 947 18446744073709551615 134512640 135650930 4294956672 18446744073709551615 135188852 0 0 4096 35 0 0 0 17 0 0 0
/proc/3429/statm: 1358 955 121 277 0 1076 0

[startup+0.035811 s]
/proc/loadavg: 0.85 0.94 0.90 3/64 3429
/proc/meminfo: memFree=1757368/2055920 swapFree=4183904/4192956
[pid=3429] ppid=3427 vsize=11824 CPUtime=0.03
/proc/3429/stat : 3429 (aigsat-sp) R 3427 3429 2217 0 -1 0 2807 0 0 0 2 1 0 0 18 0 1 0 364839971 12107776 2795 18446744073709551615 134512640 135650930 4294956672 18446744073709551615 135222829 0 0 4096 35 0 0 0 17 0 0 0
/proc/3429/statm: 2956 2795 121 277 0 2674 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 11824

[startup+0.101819 s]
/proc/loadavg: 0.85 0.94 0.90 3/64 3429
/proc/meminfo: memFree=1757368/2055920 swapFree=4183904/4192956
[pid=3429] ppid=3427 vsize=11824 CPUtime=0.09
/proc/3429/stat : 3429 (aigsat-sp) R 3427 3429 2217 0 -1 0 2807 0 0 0 8 1 0 0 18 0 1 0 364839971 12107776 2795 18446744073709551615 134512640 135650930 4294956672 18446744073709551615 135222829 0 0 4096 35 0 0 0 17 0 0 0
/proc/3429/statm: 2956 2795 121 277 0 2674 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 11824

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

Child status: 0
Real time (s): 0.160868
CPU time (s): 0.158975
CPU user time (s): 0.142978
CPU system time (s): 0.015997
CPU usage (%): 98.8233
Max. virtual memory (cumulated for all children) (KiB): 11824

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

runsolver used 0 second user time and 0.006998 second system time

The end

Launcher Data (download as text)

Begin job on node70 on Tue May 15 18:17:06 UTC 2007

IDJOB= 461335
IDBENCH= 48678
IDSOLVER= 203
FILE ID= node70/461335-1179253026

PBS_JOBID= 5277102

Free space on /tmp= 66538 MiB

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

META MD5SUM SOLVER= f61578204551f85c79544b972aeb08d2
MD5SUM BENCH=  6968c7137f0674678bc86dca099f1103

RANDOM SEED= 98514295

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node70.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.218
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.218
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:       1757584 kB
Buffers:          5636 kB
Cached:         178036 kB
SwapCached:       3056 kB
Active:          24444 kB
Inactive:       169048 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1757584 kB
SwapTotal:     4192956 kB
SwapFree:      4183904 kB
Dirty:            3340 kB
Writeback:           0 kB
Mapped:          15868 kB
Slab:            90868 kB
Committed_AS:  9312900 kB
PageTables:       1396 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= 66538 MiB

End job on node70 on Tue May 15 18:17:07 UTC 2007