Trace number 292042

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
Rsat 2007-02-08? (exit code) 0.019996 0.02466

General information on the benchmark

Namerandom/OnTreshold/5SAT/v70/
unif-k5-r21.3-v70-c1491-S127192076-04.UNSAT.shuffled.cnf
MD5SUMa03c8caae5f60333b324125585e28090
Bench CategoryRANDOM (random instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark6.94094
Satisfiable
(Un)Satisfiability was proved
Number of variables70
Number of clauses1491
Sum of the clauses size7455
Maximum clause length5
Minimum clause length5
Number of clauses of size 10
Number of clauses of size 20
Number of clauses of size 30
Number of clauses of size 40
Number of clauses of size 51491
Number of clauses of size over 50

Solver Data (download as text)

0.00/0.00	c Parsing...
0.00/0.00	c ==============================================================================
0.00/0.00	c |           |     ORIGINAL     |              LEARNT              |          |
0.00/0.00	c | Conflicts | Clauses Literals |   Limit Clauses Literals  Lit/Cl | Progress |
0.00/0.00	c ==============================================================================
0.00/0.00	c |         0 |    1491     7455 |     447       0        0     nan |  0.000 % |
0.00/0.00	c ==============================================================================
0.00/0.00	c Result  :   #vars: 70   #clauses: 1491   #literals: 7455
0.00/0.00	c CPU time:   0.002999 s
0.00/0.00	c ==============================================================================
0.00/0.01	c Rsat version 2.00
0.00/0.02	*** glibc detected *** free(): invalid next size (fast): 0x0814e140 ***
0.00/0.02	/tmp/evaluation/292042-1171749545/rsat.sh: line 39:  8926 Aborted                 (core dumped) $RS $TMP.cnf -r $TMP.result

Verifier Data (download as text)

ERROR: Unexpected answer ! (SATISFIABLE/UNSATISFIABLE expected)
Got answer:

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node13/watcher-292042-1171749545 -o ROOT/results/node13/solver-292042-1171749545 -C 1200 -M 1800 --output-limit 1,15 /tmp/evaluation/292042-1171749545/rsat.sh /tmp/evaluation/292042-1171749545/instance-292042-1171749545.cnf 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1230 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: 1.00 1.00 0.92 3/77 8923
/proc/meminfo: memFree=796664/2055920 swapFree=4192812/4192956
[pid=8923] ppid=8921 vsize=5356 CPUtime=0
/proc/8923/stat : 8923 (rsat.sh) S 8921 8923 8399 0 -1 4194304 285 0 0 0 0 0 0 0 18 0 1 0 194908977 5484544 234 18446744073709551615 4194304 4889804 548682069232 18446744073709551615 269757244228 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/8923/statm: 1339 234 195 169 0 50 0
[pid=8924] ppid=8923 vsize=820 CPUtime=0
/proc/8924/stat : 8924 (SatElite) R 8923 8923 8399 0 -1 4194304 124 0 0 0 0 0 0 0 19 0 1 0 194908978 839680 106 18446744073709551615 134512640 135038345 4294956672 18446744073709551615 134591825 0 0 4096 3 0 0 0 17 1 0 0
/proc/8924/statm: 205 108 66 128 0 74 0

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

Child status: 134
Real time (s): 0.02466
CPU time (s): 0.019996
CPU user time (s): 0.013997
CPU system time (s): 0.005999
CPU usage (%): 81.0869
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node13 on Sat Feb 17 21:59:05 UTC 2007

IDJOB= 292042
IDBENCH= 19830
IDSOLVER= 104
FILE ID= node13/292042-1171749545

PBS_JOBID= 3839256

Free space on /tmp= 66541 MiB

SOLVER NAME= Rsat 2007-02-08
BENCH NAME= HOME/pub/bench/SAT07/random/OnTreshold/5SAT/v70/unif-k5-r21.3-v70-c1491-S127192076-04.UNSAT.shuffled.cnf
COMMAND LINE= /tmp/evaluation/292042-1171749545/rsat.sh /tmp/evaluation/292042-1171749545/instance-292042-1171749545.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node13/watcher-292042-1171749545 -o ROOT/results/node13/solver-292042-1171749545 -C 1200 -M 1800 --output-limit 1,15  /tmp/evaluation/292042-1171749545/rsat.sh /tmp/evaluation/292042-1171749545/instance-292042-1171749545.cnf            

META MD5SUM SOLVER= 42fb71d21991acbdd759c16645f65450
MD5SUM BENCH=  a03c8caae5f60333b324125585e28090

RANDOM SEED= 916445264

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node13.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:        797136 kB
Buffers:         67020 kB
Cached:        1057360 kB
SwapCached:          0 kB
Active:         606236 kB
Inactive:       572556 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        797136 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1724 kB
Writeback:           0 kB
Mapped:          73300 kB
Slab:            65580 kB
Committed_AS:   816048 kB
PageTables:       1744 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= 66541 MiB

End job on node13 on Sat Feb 17 21:59:05 UTC 2007