Trace number 1736995

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.350946 0.351635

General information on the benchmark

NameCRAFTED/parity-games/
instance_n4_i5_pp.cnf
MD5SUMc15885aa7570af76db584f0c4936c8d8
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.280956
Satisfiable
(Un)Satisfiability was proved
Number of variables1960
Number of clauses11270
Sum of the clauses size35662
Maximum clause length12
Minimum clause length2
Number of clauses of size 10
Number of clauses of size 22945
Number of clauses of size 34500
Number of clauses of size 42881
Number of clauses of size 5940
Number of clauses of size over 54

Solver Data 

0.29/0.35	c starting MXC with:
0.29/0.35	c cnf_path = HOME/instance-1736995-1240814218.cnf
0.29/0.35	c restart_strategy = auto
0.29/0.35	c sign_strategy = cached
0.29/0.35	c use_preprocessing = -1
0.29/0.35	c output_implicant = 1
0.29/0.35	c timeout_seconds = 0
0.29/0.35	c running SatELite... done
0.29/0.35	c 770 vars eliminated
0.29/0.35	c received 80 units and 7779 clauses from SatELite
0.29/0.35	c 849 assignments made, starting to guess now
0.29/0.35	c ===================================[MXC]=====================================
0.29/0.35	c | Conflicts |                Clause Statistics                   |   Vars   |
0.29/0.35	c |           |    CARD     BIN      O3+      L3+   L3+Lim  Lit/CL |          |
0.29/0.35	c =============================================================================
0.29/0.35	c |         0 |       0    1390     6389        0        0     nan |     1960 |
0.29/0.35	c |       100 |       0    1394     6389       96     1050     9.6 |     1111 |
0.29/0.35	c |       210 |       0    1394     6389      206     1105    10.5 |     1111 |
0.29/0.35	c |       441 |       0    1402     6359      430     1220    11.6 |     1110 |
0.29/0.35	c |       805 |       0    1403     6359      793     1402    12.3 |     1110 |
0.29/0.35	c |      1315 |       0    1408     6359     1298     1657    13.3 |     1110 |
0.29/0.35	c |      1986 |       0    1410     6359     1967     1993    13.6 |     1110 |
0.29/0.35	c |      2834 |       0    1414     6359     1801     2417    12.7 |     1110 |
0.29/0.35	c |      3876 |       0    1420     6359     2837     2938    12.5 |     1110 |
0.29/0.35	c |      4253 |       0    1426     6359     1683     3126    10.3 |     1017 |
0.29/0.35	c ----- stats for thread 0 -----
0.29/0.35	c restarts: 32
0.29/0.35	c decisions: 7612
0.29/0.35	c propagations: 679313
0.29/0.35	c conflicts: 4253
0.29/0.35	c 0.350s elapsed
0.29/0.35	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-1736995-1240814218/watcher-1736995-1240814218 -o /tmp/evaluation-result-1736995-1240814218/solver-1736995-1240814218 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/mxc-sat09 -i HOME/instance-1736995-1240814218.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
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.99 0.97 1.00 2/64 30172
/proc/meminfo: memFree=1607856/2055920 swapFree=4180816/4192956
[pid=30172] ppid=30170 vsize=1588 CPUtime=0
/proc/30172/stat : 30172 (mxc-sat09) R 30170 30172 28894 0 -1 4194304 267 0 0 0 0 0 0 0 18 0 1 0 109449705 1626112 253 1992294400 134512640 135192793 4294956208 18446744073709551615 134766703 0 0 4096 0 0 0 0 17 1 0 0
/proc/30172/statm: 397 254 54 166 0 228 0

[startup+0.0930699 s]
/proc/loadavg: 0.99 0.97 1.00 2/64 30172
/proc/meminfo: memFree=1607856/2055920 swapFree=4180816/4192956
[pid=30172] ppid=30170 vsize=2896 CPUtime=0.08
/proc/30172/stat : 30172 (mxc-sat09) R 30170 30172 28894 0 -1 4194304 678 0 0 0 8 0 0 0 18 0 1 0 109449705 2965504 615 1992294400 134512640 135192793 4294956208 18446744073709551615 134533920 0 0 4096 0 0 0 0 17 1 0 0
/proc/30172/statm: 724 615 72 166 0 555 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 2896

[startup+0.10207 s]
/proc/loadavg: 0.99 0.97 1.00 2/64 30172
/proc/meminfo: memFree=1607856/2055920 swapFree=4180816/4192956
[pid=30172] ppid=30170 vsize=3028 CPUtime=0.09
/proc/30172/stat : 30172 (mxc-sat09) R 30170 30172 28894 0 -1 4194304 685 0 0 0 9 0 0 0 18 0 1 0 109449705 3100672 622 1992294400 134512640 135192793 4294956208 18446744073709551615 134750438 0 0 4096 0 0 0 0 17 1 0 0
/proc/30172/statm: 757 622 72 166 0 588 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3028

[startup+0.301089 s]
/proc/loadavg: 0.99 0.97 1.00 2/64 30172
/proc/meminfo: memFree=1607856/2055920 swapFree=4180816/4192956
[pid=30172] ppid=30170 vsize=3296 CPUtime=0.29
/proc/30172/stat : 30172 (mxc-sat09) R 30170 30172 28894 0 -1 4194304 770 0 0 0 29 0 0 0 19 0 1 0 109449705 3375104 707 1992294400 134512640 135192793 4294956208 18446744073709551615 134534332 0 0 4096 0 0 0 0 17 1 0 0
/proc/30172/statm: 824 707 73 166 0 655 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 3296

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

Child status: 20
Real time (s): 0.351635
CPU time (s): 0.350946
CPU user time (s): 0.345947
CPU system time (s): 0.004999
CPU usage (%): 99.8041
Max. virtual memory (cumulated for all children) (KiB): 3296

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.345947
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= 788
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= 1

runsolver used 0.002999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node45 at 2009-04-27 08:36:58
IDJOB=1736995
IDBENCH=71640
IDSOLVER=504
FILE ID=node45/1736995-1240814218
PBS_JOBID= 9187400
Free space on /tmp= 66296 MiB

SOLVER NAME= MXC 2009-03-10
BENCH NAME= SAT09/CRAFTED/parity-games/instance_n4_i5_pp.cnf
COMMAND LINE= HOME/mxc-sat09 -i BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1736995-1240814218/watcher-1736995-1240814218 -o /tmp/evaluation-result-1736995-1240814218/solver-1736995-1240814218 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/mxc-sat09 -i HOME/instance-1736995-1240814218.cnf

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

MD5SUM BENCH= c15885aa7570af76db584f0c4936c8d8
RANDOM SEED=1185249417

node45.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.231
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.231
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:       1608336 kB
Buffers:         60100 kB
Cached:         306364 kB
SwapCached:       5972 kB
Active:         144648 kB
Inactive:       230212 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1608336 kB
SwapTotal:     4192956 kB
SwapFree:      4180816 kB
Dirty:            1108 kB
Writeback:           0 kB
Mapped:          14064 kB
Slab:            58788 kB
Committed_AS:   476080 kB
PageTables:       1376 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= 66296 MiB
End job on node45 at 2009-04-27 08:36:59