Trace number 461200

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
aig-cmusat 2007-05-15UNSAT 0.021996 0.02255

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.00/0.00	c Executing aigtocnf /tmp/evaluation/461200-1179256303/instance-461200-1179256303.aig /tmp/evaluation/461200-1179256303/instance-461200-1179256303.aig.cnf
0.00/0.00	c Pre-processing provided 0 assignments
0.00/0.00	c REMAP internally 1
0.00/0.00	c |  Number of variables:  840                                                  |
0.00/0.00	c |  Number of clauses:    2441                                                 |
0.00/0.02	c |  Parsing time:         0.00         sec                                       |
0.00/0.02	c #varS 840 #clauseS 641
0.00/0.02	c After remapping new number of variables: 141
0.00/0.02	c #Total time (in seconds): 0.013997
0.00/0.02	c #Memory used (in MB): 2.49609
0.00/0.02	c 
0.00/0.02	s UNSATISFIABLE

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/node5/watcher-461200-1179256303 -o ROOT/results/node5/solver-461200-1179256303 -C 1200 -W 1800 -M 1800 --output-limit 1,15 /tmp/evaluation/461200-1179256303/aig-cmusat /tmp/evaluation/461200-1179256303/instance-461200-1179256303.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.77 0.92 0.82 3/77 18019
/proc/meminfo: memFree=1862720/2055920 swapFree=4150068/4192956
[pid=18019] ppid=18017 vsize=1000 CPUtime=0
/proc/18019/stat : 18019 (aig-cmusat) S 18017 18019 17577 0 -1 0 109 0 0 0 0 0 0 0 18 0 1 0 401667984 1024000 94 18446744073709551615 134512640 135469250 4294956672 18446744073709551615 135073394 0 65536 4102 33 18446744071563356171 0 0 17 0 0 0
/proc/18019/statm: 250 94 83 233 0 10 0
[pid=18020] ppid=18019 vsize=0 CPUtime=0
/proc/18020/stat : 18020 (aigtocnf) D 18019 18019 17577 0 -1 4 299 0 0 0 0 0 0 0 20 0 1 0 401667984 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 0 18446744072100051646 0 0 17 0 0 0
/proc/18020/statm: 0 0 0 0 0 0 0

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

Child status: 20
Real time (s): 0.02255
CPU time (s): 0.021996
CPU user time (s): 0.016997
CPU system time (s): 0.004999
CPU usage (%): 97.5432
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.016997
system time used= 0.004999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 597
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= 2

runsolver used 0.001999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node5 on Tue May 15 19:11:43 UTC 2007

IDJOB= 461200
IDBENCH= 48644
IDSOLVER= 204
FILE ID= node5/461200-1179256303

PBS_JOBID= 5277290

Free space on /tmp= 66526 MiB

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

META MD5SUM SOLVER= 46c0b88679dc7b9c7f6dd96ef04c5851
MD5SUM BENCH=  995d875eaa398649ddb51e55b549e2af

RANDOM SEED= 664054721

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node5.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.232
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.232
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:       1862936 kB
Buffers:         18716 kB
Cached:          83460 kB
SwapCached:      11180 kB
Active:          31712 kB
Inactive:        93544 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1862936 kB
SwapTotal:     4192956 kB
SwapFree:      4150068 kB
Dirty:            1800 kB
Writeback:           0 kB
Mapped:          30072 kB
Slab:            53140 kB
Committed_AS: 15081492 kB
PageTables:       1740 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= 66526 MiB

End job on node5 on Tue May 15 19:11:43 UTC 2007