Trace number 1796487

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
ReVivAl 0.23 + SatElite 2009-03-18? (problem) 0.003998 0.00589492

General information on the benchmark

Nameindustrial/vliw_unsat_2.0/
9dlx_vliw_at_b_iq9.cnf
MD5SUM9a43349587a435e7109b46b3aceb156e
Bench CategoryAPPLICATION (applications instances)
Best result obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark
Satisfiable
(Un)Satisfiability was proved
Number of variables482093
Number of clauses9676386
Sum of the clauses size28195028
Maximum clause length226
Minimum clause length1
Number of clauses of size 11
Number of clauses of size 29152157
Number of clauses of size 3120945
Number of clauses of size 410067
Number of clauses of size 528986
Number of clauses of size over 5364230

Solver Data 

0.00/0.00	c SatElite...
0.00/0.00	c Parsing...
0.00/0.00	c num clause = 9676386, num vars = 482093
0.00/0.00	c Exiting...too many clauses
0.00/0.00	SatElite died... trying RSAT...
0.00/0.00	ERROR! unknown flag -s

Verifier Data 

ERROR: Unexpected answer ! (SATISFIABLE/UNSATISFIABLE expected)
Got answer: <no 's ' line found>

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1796487-1242076444/watcher-1796487-1242076444 -o /tmp/evaluation-result-1796487-1242076444/solver-1796487-1242076444 -C 1200 -W 1800 -M 1800 HOME/run.sh HOME/instance-1796487-1242076444.cnf HOME 

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
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.45 1.12 1.08 3/64 16771
/proc/meminfo: memFree=468860/2055920 swapFree=4181692/4192956
[pid=16771] ppid=16769 vsize=5360 CPUtime=0
/proc/16771/stat : 16771 (run.sh) R 16769 16771 16487 0 -1 4194304 315 80 0 0 0 0 0 0 21 0 1 0 235675621 5488640 241 1992294400 4194304 4889804 548682068784 18446744073709551615 256364831556 0 65536 4100 65538 0 0 0 17 1 0 0
/proc/16771/statm: 1340 241 197 169 0 51 0
[pid=16773] ppid=16771 vsize=0 CPUtime=0
/proc/16773/stat : 16773 (minisat) Z 16771 16771 16487 0 -1 4194316 68 0 0 0 0 0 0 0 18 0 1 0 235675621 0 0 1992294400 0 0 0 0 0 0 0 4096 0 18446744071563351923 0 0 17 0 0 0
/proc/16773/statm: 0 0 0 0 0 0 0

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

Child status: 0
Real time (s): 0.00589492
CPU time (s): 0.003998
CPU user time (s): 0.000999
CPU system time (s): 0.002999
CPU usage (%): 67.8212
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.001999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node90 at 2009-05-11 23:14:26
IDJOB=1796487
IDBENCH=20574
IDSOLVER=648
FILE ID=node90/1796487-1242076444
PBS_JOBID= 9277664
Free space on /tmp= 66080 MiB

SOLVER NAME= ReVivAl 0.23 + SatElite 2009-03-18
BENCH NAME= SAT07/industrial/vliw_unsat_2.0/9dlx_vliw_at_b_iq9.cnf
COMMAND LINE= HOME/run.sh BENCHNAME TMPDIR
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1796487-1242076444/watcher-1796487-1242076444 -o /tmp/evaluation-result-1796487-1242076444/solver-1796487-1242076444 -C 1200 -W 1800 -M 1800  HOME/run.sh HOME/instance-1796487-1242076444.cnf HOME

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

MD5SUM BENCH= 9a43349587a435e7109b46b3aceb156e
RANDOM SEED=1125761484

node90.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.238
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.238
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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:        469404 kB
Buffers:         87576 kB
Cached:        1374180 kB
SwapCached:       5480 kB
Active:         515760 kB
Inactive:       955000 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        469404 kB
SwapTotal:     4192956 kB
SwapFree:      4181692 kB
Dirty:          206404 kB
Writeback:           0 kB
Mapped:          15032 kB
Slab:           101772 kB
Committed_AS:   703468 kB
PageTables:       1428 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= 66076 MiB
End job on node90 at 2009-05-11 23:14:26