Trace number 1773037

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 1.53477 1.53632

General information on the benchmark

Nameindustrial/babic/hsatv17/
hsat_vc11803.cnf
MD5SUM6c6fd606fd41d7205b07602118ad74a0
Bench CategoryAPPLICATION (applications instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark1.53477
Satisfiable
(Un)Satisfiability was proved
Number of variables276402
Number of clauses798348
Sum of the clauses size2080196
Maximum clause length3
Minimum clause length1
Number of clauses of size 131560
Number of clauses of size 2251728
Number of clauses of size 3515060
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 50

Solver Data 

1.49/1.51	c starting MXC with:
1.49/1.51	c cnf_path = HOME/instance-1773037-1241298333.cnf
1.49/1.51	c restart_strategy = auto
1.49/1.51	c sign_strategy = cached
1.49/1.51	c use_preprocessing = -1
1.49/1.51	c output_implicant = 1
1.49/1.51	c timeout_seconds = 0
1.49/1.51	c running SatELite... c ===================================[MXC]=====================================
1.49/1.51	c | Conflicts |                Clause Statistics                   |   Vars   |
1.49/1.51	c |           |    CARD     BIN      O3+      L3+   L3+Lim  Lit/CL |          |
1.49/1.51	c =============================================================================
1.49/1.51	c |         0 |       0       0        0        0        0     nan |   276427 |
1.49/1.51	c ----- stats for thread 0 -----
1.49/1.51	c restarts: 0
1.49/1.51	c decisions: 0
1.49/1.51	c propagations: 0
1.49/1.51	c conflicts: 0
1.49/1.51	c 1.495s elapsed
1.49/1.51	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-1773037-1241298333/watcher-1773037-1241298333 -o /tmp/evaluation-result-1773037-1241298333/solver-1773037-1241298333 -C 10000 -W 12000 -M 1800 HOME/mxc-sat09 -i HOME/instance-1773037-1241298333.cnf 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 10000 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 10030 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 12000 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: 3.19 3.82 3.88 3/64 30691
/proc/meminfo: memFree=1950560/2055920 swapFree=4181336/4192956
[pid=30691] ppid=30689 vsize=16600 CPUtime=0
/proc/30691/stat : 30691 (mxc-sat09) R 30689 30691 30627 0 -1 4194304 816 0 0 0 0 0 0 0 18 0 1 0 157861954 16998400 802 1992294400 134512640 135192793 4294956224 18446744073709551615 134779278 0 0 4096 0 0 0 0 17 0 0 0
/proc/30691/statm: 4150 810 46 166 0 3981 0

[startup+0.0215399 s]
/proc/loadavg: 3.19 3.82 3.88 3/64 30691
/proc/meminfo: memFree=1950560/2055920 swapFree=4181336/4192956
[pid=30691] ppid=30689 vsize=16600 CPUtime=0.02
/proc/30691/stat : 30691 (mxc-sat09) R 30689 30691 30627 0 -1 4194304 3598 0 0 0 0 2 0 0 18 0 1 0 157861954 16998400 3584 1992294400 134512640 135192793 4294956224 18446744073709551615 134779278 0 0 4096 0 0 0 0 17 0 0 0
/proc/30691/statm: 4150 3591 46 166 0 3981 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 16600

[startup+0.101551 s]
/proc/loadavg: 3.19 3.82 3.88 3/64 30691
/proc/meminfo: memFree=1950560/2055920 swapFree=4181336/4192956
[pid=30691] ppid=30689 vsize=82592 CPUtime=0.09
/proc/30691/stat : 30691 (mxc-sat09) R 30689 30691 30627 0 -1 4194304 12958 0 0 0 3 6 0 0 18 0 1 0 157861954 84574208 12874 1992294400 134512640 135192793 4294956224 18446744073709551615 134569157 0 0 4096 0 0 0 0 17 0 0 0
/proc/30691/statm: 20648 12878 53 166 0 20479 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 82592

[startup+0.301567 s]
/proc/loadavg: 3.19 3.82 3.88 3/64 30691
/proc/meminfo: memFree=1950560/2055920 swapFree=4181336/4192956
[pid=30691] ppid=30689 vsize=108024 CPUtime=0.29
/proc/30691/stat : 30691 (mxc-sat09) R 30689 30691 30627 0 -1 4194304 19034 0 0 0 21 8 0 0 19 0 1 0 157861954 110616576 18857 1992294400 134512640 135192793 4294956224 18446744073709551615 134750438 0 0 4096 0 0 0 0 17 0 0 0
/proc/30691/statm: 27006 18858 55 166 0 26837 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 108024

[startup+0.701604 s]
/proc/loadavg: 3.19 3.82 3.88 3/64 30691
/proc/meminfo: memFree=1950560/2055920 swapFree=4181336/4192956
[pid=30691] ppid=30689 vsize=137988 CPUtime=0.69
/proc/30691/stat : 30691 (mxc-sat09) R 30689 30691 30627 0 -1 4194304 26548 0 0 0 56 13 0 0 23 0 1 0 157861954 141299712 26371 1992294400 134512640 135192793 4294956224 18446744073709551615 134750438 0 0 4096 0 0 0 0 17 0 0 0
/proc/30691/statm: 34497 26372 55 166 0 34328 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 137988

[startup+1.50169 s]
/proc/loadavg: 3.19 3.82 3.88 2/65 30692
/proc/meminfo: memFree=1854488/2055920 swapFree=4181336/4192956
[pid=30691] ppid=30689 vsize=142068 CPUtime=1.49
/proc/30691/stat : 30691 (mxc-sat09) R 30689 30691 30627 0 -1 4194304 31202 0 0 0 134 15 0 0 25 0 1 0 157861954 145477632 27086 1992294400 134512640 135192793 4294956224 18446744073709551615 134750438 0 0 4096 0 0 0 0 17 0 0 0
/proc/30691/statm: 35517 27086 56 166 0 35348 0
Current children cumulated CPU time (s) 1.49
Current children cumulated vsize (KiB) 142068

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

Child status: 20
Real time (s): 1.53632
CPU time (s): 1.53477
CPU user time (s): 1.36279
CPU system time (s): 0.171973
CPU usage (%): 99.8987
Max. virtual memory (cumulated for all children) (KiB): 142068

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.36279
system time used= 0.171973
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 31335
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= 3

runsolver used 0.005999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node36 at 2009-05-02 23:05:34
IDJOB=1773037
IDBENCH=20463
IDSOLVER=613
FILE ID=node36/1773037-1241298333
PBS_JOBID= 9225182
Free space on /tmp= 66476 MiB

SOLVER NAME= MXC 2009-03-10
BENCH NAME= SAT07/industrial/babic/hsatv17/hsat_vc11803.cnf
COMMAND LINE= HOME/mxc-sat09 -i BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1773037-1241298333/watcher-1773037-1241298333 -o /tmp/evaluation-result-1773037-1241298333/solver-1773037-1241298333 -C 10000 -W 12000 -M 1800  HOME/mxc-sat09 -i HOME/instance-1773037-1241298333.cnf

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

MD5SUM BENCH= 6c6fd606fd41d7205b07602118ad74a0
RANDOM SEED=725575811

node36.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.232
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.232
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:       1950976 kB
Buffers:          5504 kB
Cached:          47828 kB
SwapCached:       5352 kB
Active:          39132 kB
Inactive:        21980 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1950976 kB
SwapTotal:     4192956 kB
SwapFree:      4181336 kB
Dirty:           16696 kB
Writeback:           0 kB
Mapped:          13408 kB
Slab:            29868 kB
Committed_AS:   667444 kB
PageTables:       1356 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= 66476 MiB
End job on node36 at 2009-05-02 23:05:35