Trace number 1784493

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
MXC 2009-03-10UNSAT 0.012997 0.0131021

General information on the benchmark

NameCRAFTED/parity-games/
instance_n3_i4_pp_ci_ce.cnf
MD5SUMa3abb10f5ab4ed4f5093550970c0200d
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.007998
Satisfiable
(Un)Satisfiability was proved
Number of variables696
Number of clauses3122
Sum of the clauses size9414
Maximum clause length6
Minimum clause length2
Number of clauses of size 10
Number of clauses of size 21091
Number of clauses of size 31138
Number of clauses of size 4650
Number of clauses of size 5240
Number of clauses of size over 53

Solver Data 

0.00/0.01	c starting MXC with:
0.00/0.01	c cnf_path = HOME/instance-1784493-1241948463.cnf
0.00/0.01	c restart_strategy = auto
0.00/0.01	c sign_strategy = cached
0.00/0.01	c use_preprocessing = -1
0.00/0.01	c output_implicant = 1
0.00/0.01	c timeout_seconds = 0
0.00/0.01	c running SatELite... done
0.00/0.01	c 246 vars eliminated
0.00/0.01	c received 12 units and 2184 clauses from SatELite
0.00/0.01	c 257 assignments made, starting to guess now
0.00/0.01	c ===================================[MXC]=====================================
0.00/0.01	c | Conflicts |                Clause Statistics                   |   Vars   |
0.00/0.01	c |           |    CARD     BIN      O3+      L3+   L3+Lim  Lit/CL |          |
0.00/0.01	c =============================================================================
0.00/0.01	c |         0 |       0     756     1428        0        0     nan |      696 |
0.00/0.01	c |        67 |       0     767     1428       47     1033     6.8 |      233 |
0.00/0.01	c ----- stats for thread 0 -----
0.00/0.01	c restarts: 0
0.00/0.01	c decisions: 146
0.00/0.01	c propagations: 4108
0.00/0.01	c conflicts: 67
0.00/0.01	c 0.012s elapsed
0.00/0.01	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-1784493-1241948463/watcher-1784493-1241948463 -o /tmp/evaluation-result-1784493-1241948463/solver-1784493-1241948463 -C 5000 -W 6000 -M 1800 HOME/mxc-sat09 -i HOME/instance-1784493-1241948463.cnf 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 5000 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 5030 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 6000 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.00 1.00 1.00 3/64 28973
/proc/meminfo: memFree=912888/2055920 swapFree=4175260/4192956
[pid=28973] ppid=28971 vsize=1240 CPUtime=0
/proc/28973/stat : 28973 (mxc-sat09) R 28971 28973 28870 0 -1 4194304 176 0 0 0 0 0 0 0 18 0 1 0 222873087 1269760 162 1992294400 134512640 135192793 4294956224 18446744073709551615 134567445 0 0 4096 0 0 0 0 17 1 0 0
/proc/28973/statm: 310 162 56 166 0 141 0

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

Child status: 20
Real time (s): 0.0131021
CPU time (s): 0.012997
CPU user time (s): 0.009998
CPU system time (s): 0.002999
CPU usage (%): 99.1978
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.009998
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= 238
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= 2
involuntary context switches= 0

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node60 at 2009-05-10 11:41:03
IDJOB=1784493
IDBENCH=71624
IDSOLVER=613
FILE ID=node60/1784493-1241948463
PBS_JOBID= 9265045
Free space on /tmp= 66044 MiB

SOLVER NAME= MXC 2009-03-10
BENCH NAME= SAT09/CRAFTED/parity-games/instance_n3_i4_pp_ci_ce.cnf
COMMAND LINE= HOME/mxc-sat09 -i BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1784493-1241948463/watcher-1784493-1241948463 -o /tmp/evaluation-result-1784493-1241948463/solver-1784493-1241948463 -C 5000 -W 6000 -M 1800  HOME/mxc-sat09 -i HOME/instance-1784493-1241948463.cnf

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

MD5SUM BENCH= a3abb10f5ab4ed4f5093550970c0200d
RANDOM SEED=1464989700

node60.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.256
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.256
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:        913368 kB
Buffers:         71164 kB
Cached:         976628 kB
SwapCached:      12124 kB
Active:         398256 kB
Inactive:       664192 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        913368 kB
SwapTotal:     4192956 kB
SwapFree:      4175260 kB
Dirty:             900 kB
Writeback:           0 kB
Mapped:          14084 kB
Slab:            66104 kB
Committed_AS:   763284 kB
PageTables:       1448 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= 66040 MiB
End job on node60 at 2009-05-10 11:41:03