Trace number 1725398

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.250961 0.251911

General information on the benchmark

Namecrafted/Medium/contest05/pebbling/
unsat-pbl-00090.sat05-1326.reshuffled-07.cnf
MD5SUMfc73c241ff6e8e1a49a6ff2500eb7905
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.131979
Satisfiable
(Un)Satisfiability was proved
Number of variables322
Number of clauses9322
Sum of the clauses size72335
Maximum clause length11
Minimum clause length1
Number of clauses of size 11
Number of clauses of size 211
Number of clauses of size 379
Number of clauses of size 4136
Number of clauses of size 5421
Number of clauses of size over 58674

Solver Data 

0.19/0.25	c starting MXC with:
0.19/0.25	c cnf_path = HOME/instance-1725398-1240704470.cnf
0.19/0.25	c restart_strategy = auto
0.19/0.25	c sign_strategy = cached
0.19/0.25	c use_preprocessing = -1
0.19/0.25	c output_implicant = 1
0.19/0.25	c timeout_seconds = 0
0.19/0.25	c running SatELite... c ===================================[MXC]=====================================
0.19/0.25	c | Conflicts |                Clause Statistics                   |   Vars   |
0.19/0.25	c |           |    CARD     BIN      O3+      L3+   L3+Lim  Lit/CL |          |
0.19/0.25	c =============================================================================
0.19/0.25	c |         0 |       0       0        0        0        0     nan |      322 |
0.19/0.25	c ----- stats for thread 0 -----
0.19/0.25	c restarts: 0
0.19/0.25	c decisions: 0
0.19/0.25	c propagations: 0
0.19/0.25	c conflicts: 0
0.19/0.25	c 0.250s elapsed
0.19/0.25	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-1725398-1240704470/watcher-1725398-1240704470 -o /tmp/evaluation-result-1725398-1240704470/solver-1725398-1240704470 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/mxc-sat09 -i HOME/instance-1725398-1240704470.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 0.99 3/64 21753
/proc/meminfo: memFree=1892440/2055920 swapFree=4180832/4192956
[pid=21753] ppid=21751 vsize=1424 CPUtime=0
/proc/21753/stat : 21753 (mxc-sat09) R 21751 21753 21348 0 -1 4194304 221 0 0 0 0 0 0 0 18 0 1 0 98475162 1458176 207 1992294400 134512640 135192793 4294956224 18446744073709551615 134766703 0 0 4096 0 0 0 0 17 1 0 0
/proc/21753/statm: 356 207 54 166 0 187 0

[startup+0.026662 s]
/proc/loadavg: 0.99 0.97 0.99 3/64 21753
/proc/meminfo: memFree=1892440/2055920 swapFree=4180832/4192956
[pid=21753] ppid=21751 vsize=1832 CPUtime=0.02
/proc/21753/stat : 21753 (mxc-sat09) R 21751 21753 21348 0 -1 4194304 411 0 0 0 2 0 0 0 18 0 1 0 98475162 1875968 318 1992294400 134512640 135192793 4294956224 18446744073709551615 134567773 0 0 4096 0 0 0 0 17 1 0 0
/proc/21753/statm: 458 318 55 166 0 289 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 1832

[startup+0.101669 s]
/proc/loadavg: 0.99 0.97 0.99 3/64 21753
/proc/meminfo: memFree=1892440/2055920 swapFree=4180832/4192956
[pid=21753] ppid=21751 vsize=2548 CPUtime=0.09
/proc/21753/stat : 21753 (mxc-sat09) R 21751 21753 21348 0 -1 4194304 603 0 0 0 9 0 0 0 18 0 1 0 98475162 2609152 510 1992294400 134512640 135192793 4294956224 18446744073709551615 134568153 0 0 4096 0 0 0 0 17 1 0 0
/proc/21753/statm: 637 510 56 166 0 468 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2548

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

[startup+0.201681 s]
/proc/loadavg: 0.99 0.97 0.99 3/64 21753
/proc/meminfo: memFree=1892440/2055920 swapFree=4180832/4192956
[pid=21753] ppid=21751 vsize=2880 CPUtime=0.19
/proc/21753/stat : 21753 (mxc-sat09) R 21751 21753 21348 0 -1 4194304 673 0 0 0 19 0 0 0 18 0 1 0 98475162 2949120 580 1992294400 134512640 135192793 4294956224 18446744073709551615 134567773 0 0 4096 0 0 0 0 17 1 0 0
/proc/21753/statm: 720 580 56 166 0 551 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 2880

Child status: 20
Real time (s): 0.251911
CPU time (s): 0.250961
CPU user time (s): 0.247962
CPU system time (s): 0.002999
CPU usage (%): 99.6228
Max. virtual memory (cumulated for all children) (KiB): 2880

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.247962
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= 755
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.001999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node42 at 2009-04-26 02:07:50
IDJOB=1725398
IDBENCH=24582
IDSOLVER=504
FILE ID=node42/1725398-1240704470
PBS_JOBID= 9186753
Free space on /tmp= 66328 MiB

SOLVER NAME= MXC 2009-03-10
BENCH NAME= SAT07/crafted/Medium/contest05/pebbling/unsat-pbl-00090.sat05-1326.reshuffled-07.cnf
COMMAND LINE= HOME/mxc-sat09 -i BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1725398-1240704470/watcher-1725398-1240704470 -o /tmp/evaluation-result-1725398-1240704470/solver-1725398-1240704470 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/mxc-sat09 -i HOME/instance-1725398-1240704470.cnf

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

MD5SUM BENCH= fc73c241ff6e8e1a49a6ff2500eb7905
RANDOM SEED=1801058600

node42.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:       1892856 kB
Buffers:         17940 kB
Cached:          83472 kB
SwapCached:       5688 kB
Active:          29808 kB
Inactive:        79756 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1892856 kB
SwapTotal:     4192956 kB
SwapFree:      4180832 kB
Dirty:             996 kB
Writeback:           0 kB
Mapped:          14048 kB
Slab:            39464 kB
Committed_AS:   460168 kB
PageTables:       1388 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= 66328 MiB
End job on node42 at 2009-04-26 02:07:50