Trace number 1834171

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
minisat_cumr p-2009-03-18UNSAT 0.006998 0.0102409

General information on the benchmark

NameCRAFTED/parity-games/
instance_n2_i2_pp.cnf
MD5SUM969b7dec8b8c4f862d2feed9796787c8
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0
Satisfiable
(Un)Satisfiability was proved
Number of variables27
Number of clauses53
Sum of the clauses size114
Maximum clause length3
Minimum clause length2
Number of clauses of size 10
Number of clauses of size 245
Number of clauses of size 38
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 50

Solver Data 

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 |      53      114 |      15       0        0     nan |  0.000 % |
0.00/0.00	c (contradiction during subsumption)
0.00/0.00	c starts                :        0
0.00/0.00	c conflicts             :        0   (0 /sec)
0.00/0.00	c reduce learnts        :        0   (0 /sec)
0.00/0.00	c decisions             :        0   (0 /sec)
0.00/0.00	c propagations          :        0   (0 /sec)
0.00/0.00	c inspects              :        0   (0 /sec)
0.00/0.00	c memory used           : 0.859375 MB
0.00/0.00	c CPU time              : 0.000999 s
0.00/0.00	c 
0.00/0.00	s UNSATISFIABLE

Verifier Data 

No possible verification on an UNSAT instance

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1834171-1242828545/watcher-1834171-1242828545 -o /tmp/evaluation-result-1834171-1242828545/solver-1834171-1242828545 -C 1200 -W 1800 -M 1800 SatELiteGTI HOME/instance-1834171-1242828545.cnf 

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: 0.91 0.97 0.99 3/64 16793
/proc/meminfo: memFree=1838600/2055920 swapFree=4120716/4192956
[pid=16793] ppid=16791 vsize=5356 CPUtime=0
/proc/16793/stat : 16793 (SatELiteGTI) S 16791 16793 16542 0 -1 4194304 276 0 0 0 0 0 0 0 19 0 1 0 310887451 5484544 235 1992294400 4194304 4889804 548682068832 18446744073709551615 233588883538 0 0 4100 65536 18446744071563648864 0 0 17 0 0 0
/proc/16793/statm: 1339 235 195 169 0 50 0
[pid=16794] ppid=16793 vsize=5356 CPUtime=0
/proc/16794/stat : 16794 (SatELiteGTI) S 16793 16793 16542 0 -1 4194368 51 25 0 0 0 0 0 0 21 0 1 0 310887451 5484544 238 1992294400 4194304 4889804 548682068832 18446744073709551615 233588712260 0 65536 4096 65538 18446744071563356171 0 0 17 0 0 0
/proc/16794/statm: 1339 238 198 169 0 50 0
[pid=16796] ppid=16794 vsize=5356 CPUtime=0
/proc/16796/stat : 16796 (SatELiteGTI) R 16794 16793 16542 0 -1 4194368 19 0 0 0 0 0 0 0 22 0 1 0 310887451 5484544 239 1992294400 4194304 4889804 548682068832 18446744073709551615 233588714791 0 0 4096 0 0 0 0 17 0 0 0
/proc/16796/statm: 48 23 16 11 0 11 0

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

Child status: 20
Real time (s): 0.0102409
CPU time (s): 0.006998
CPU user time (s): 0.004999
CPU system time (s): 0.001999
CPU usage (%): 68.3338
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.004999
system time used= 0.001999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 828
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= 18
involuntary context switches= 9

runsolver used 0.006998 second user time and 0.002999 second system time

The end

Launcher Data 

Begin job on node27 at 2009-05-20 16:09:05
IDJOB=1834171
IDBENCH=71634
IDSOLVER=671
FILE ID=node27/1834171-1242828545
PBS_JOBID= 9322487
Free space on /tmp= 66300 MiB

SOLVER NAME= minisat_cumr p-2009-03-18
BENCH NAME= SAT09/CRAFTED/parity-games/instance_n2_i2_pp.cnf
COMMAND LINE= SatELiteGTI BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1834171-1242828545/watcher-1834171-1242828545 -o /tmp/evaluation-result-1834171-1242828545/solver-1834171-1242828545 -C 1200 -W 1800 -M 1800  SatELiteGTI HOME/instance-1834171-1242828545.cnf

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

MD5SUM BENCH= 969b7dec8b8c4f862d2feed9796787c8
RANDOM SEED=722940336

node27.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		: 2800.234
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	: 5521.40
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		: 2800.234
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:       1839088 kB
Buffers:         21940 kB
Cached:          92164 kB
SwapCached:      65008 kB
Active:          96220 kB
Inactive:        85352 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1839088 kB
SwapTotal:     4192956 kB
SwapFree:      4120716 kB
Dirty:            1592 kB
Writeback:           0 kB
Mapped:          14632 kB
Slab:            21188 kB
Committed_AS:  1031004 kB
PageTables:       1380 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264948 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66296 MiB
End job on node27 at 2009-05-20 16:09:05