Trace number 1730358

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
VARSAT-industrial 2009-03-22UNSAT 2.56761 2.56768

General information on the benchmark

Namecrafted/Difficult/contest05/sabharwal/
grid-pebbling-unsat-grid-pbl-0300.sat05-1350.sat05-1350.reshuffled-07.cnf
MD5SUM4c3b2816cb16b0fd4134bf2c85ce45d0
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark1.61375
Satisfiable
(Un)Satisfiability was proved
Number of variables90300
Number of clauses179702
Sum of the clauses size718202
Maximum clause length4
Minimum clause length1
Number of clauses of size 12
Number of clauses of size 2300
Number of clauses of size 30
Number of clauses of size 4179400
Number of clauses of size 50
Number of clauses of size over 50

Solver Data 

0.00/0.00	c ============================[ Problem Statistics ]=============================
0.00/0.00	c |                                                                             |
0.00/0.00	c |  Number of variables:  90300                                                |
0.00/0.00	c |  Number of clauses:    179702                                               |
1.10/1.18	c |  Parsing time:         1.13         s                                       |
1.10/1.18	c |  Timeout:              43200 s
1.10/1.18	c |  Random Seed:          1249372698.000000
1.10/1.18	c |  Heuristic:            EMBP-G, threshold 0.950                              |
1.10/1.18	c |  Branching Rule:       default (solution-guided)                            |
1.10/1.18	c |  Learned clauses in surveys?  Using NO learned clauses.                     |
1.10/1.18	c |                                                                             |
2.50/2.55	c surveys--CPU time (sec)   : 0.0000         (0.00 % of total)
2.50/2.55	c surveys--attempted        : 0              (nan /sec)
2.50/2.55	c surveys--converged        : 0              ( nan % successful)
2.50/2.55	c restarts              : 0
2.50/2.55	c conflicts             : 0              (0 /sec)
2.50/2.55	c decisions             : 0              ( nan % random) (0 /sec)
2.50/2.55	c propagations          : 4              (2 /sec)
2.50/2.55	c conflict literals     : 0              ( nan % deleted)
2.50/2.55	c Memory used           : 74.00 MB
2.50/2.55	c Total CPU time (sec)      : 2.4736      
2.50/2.55	c 
2.50/2.55	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-1730358-1240758485/watcher-1730358-1240758485 -o /tmp/evaluation-result-1730358-1240758485/solver-1730358-1240758485 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/varsat-industrial_static -seed=1249372698 HOME/instance-1730358-1240758485.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.92 0.99 1.15 3/64 1603
/proc/meminfo: memFree=1667136/2055920 swapFree=4181440/4192956
[pid=1603] ppid=1601 vsize=4272 CPUtime=0
/proc/1603/stat : 1603 (varsat-industri) R 1601 1603 1169 0 -1 4194304 785 0 0 0 0 0 0 0 18 0 1 0 103877024 4374528 770 1992294400 4194304 5102648 548682068768 18446744073709551615 4200628 0 0 4096 3 0 0 0 17 1 0 0
/proc/1603/statm: 1068 777 80 221 0 844 0

[startup+0.0332839 s]
/proc/loadavg: 0.92 0.99 1.15 3/64 1603
/proc/meminfo: memFree=1667136/2055920 swapFree=4181440/4192956
[pid=1603] ppid=1601 vsize=15052 CPUtime=0.02
/proc/1603/stat : 1603 (varsat-industri) R 1601 1603 1169 0 -1 4194304 3419 0 0 0 1 1 0 0 18 0 1 0 103877024 15413248 3380 1992294400 4194304 5102648 548682068768 18446744073709551615 4245145 0 0 4096 3 0 0 0 17 1 0 0
/proc/1603/statm: 3763 3383 82 221 0 3539 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 15052

[startup+0.101292 s]
/proc/loadavg: 0.92 0.99 1.15 3/64 1603
/proc/meminfo: memFree=1667136/2055920 swapFree=4181440/4192956
[pid=1603] ppid=1601 vsize=22280 CPUtime=0.09
/proc/1603/stat : 1603 (varsat-industri) R 1601 1603 1169 0 -1 4194304 5262 0 0 0 7 2 0 0 18 0 1 0 103877024 22814720 5223 1992294400 4194304 5102648 548682068768 18446744073709551615 4491703 0 0 4096 3 0 0 0 17 1 0 0
/proc/1603/statm: 5570 5223 87 221 0 5346 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 22280

[startup+0.301321 s]
/proc/loadavg: 0.92 0.99 1.15 3/64 1603
/proc/meminfo: memFree=1667136/2055920 swapFree=4181440/4192956
[pid=1603] ppid=1601 vsize=30772 CPUtime=0.29
/proc/1603/stat : 1603 (varsat-industri) R 1601 1603 1169 0 -1 4194304 7357 0 0 0 26 3 0 0 19 0 1 0 103877024 31510528 7318 1992294400 4194304 5102648 548682068768 18446744073709551615 4491703 0 0 4096 3 0 0 0 17 1 0 0
/proc/1603/statm: 7693 7319 87 221 0 7469 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 30772

[startup+0.70138 s]
/proc/loadavg: 0.92 0.99 1.15 3/64 1603
/proc/meminfo: memFree=1667136/2055920 swapFree=4181440/4192956
[pid=1603] ppid=1601 vsize=41344 CPUtime=0.69
/proc/1603/stat : 1603 (varsat-industri) R 1601 1603 1169 0 -1 4194304 9945 0 0 0 65 4 0 0 22 0 1 0 103877024 42336256 9906 1992294400 4194304 5102648 548682068768 18446744073709551615 4491703 0 0 4096 3 0 0 0 17 1 0 0
/proc/1603/statm: 10336 9906 87 221 0 10112 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 41344

[startup+1.5015 s]
/proc/loadavg: 0.92 0.99 1.15 2/65 1604
/proc/meminfo: memFree=1620280/2055920 swapFree=4181440/4192956
[pid=1603] ppid=1601 vsize=55900 CPUtime=1.49
/proc/1603/stat : 1603 (varsat-industri) R 1601 1603 1169 0 -1 4194304 13459 0 0 0 144 5 0 0 25 0 1 0 103877024 57241600 13420 1992294400 4194304 5102648 548682068768 18446744073709551615 4491703 0 0 4096 3 0 0 0 17 1 0 0
/proc/1603/statm: 13975 13420 100 221 0 13751 0
Current children cumulated CPU time (s) 1.49
Current children cumulated vsize (KiB) 55900

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

[startup+2.30161 s]
/proc/loadavg: 0.92 0.99 1.15 2/65 1604
/proc/meminfo: memFree=1603000/2055920 swapFree=4181440/4192956
[pid=1603] ppid=1601 vsize=70068 CPUtime=2.29
/proc/1603/stat : 1603 (varsat-industri) R 1601 1603 1169 0 -1 4194304 17042 0 0 0 222 7 0 0 25 0 1 0 103877024 71749632 17003 1992294400 4194304 5102648 548682068768 18446744073709551615 4491703 0 0 4096 3 0 0 0 17 1 0 0
/proc/1603/statm: 17517 17003 100 221 0 17293 0
Current children cumulated CPU time (s) 2.29
Current children cumulated vsize (KiB) 70068

[startup+2.50165 s]
/proc/loadavg: 0.92 0.99 1.15 2/65 1604
/proc/meminfo: memFree=1603000/2055920 swapFree=4181440/4192956
[pid=1603] ppid=1601 vsize=73632 CPUtime=2.5
/proc/1603/stat : 1603 (varsat-industri) R 1601 1603 1169 0 -1 4194304 18043 0 0 0 242 8 0 0 25 0 1 0 103877024 75399168 18004 1992294400 4194304 5102648 548682068768 18446744073709551615 4491703 0 0 4096 3 0 0 0 17 1 0 0
/proc/1603/statm: 18408 18004 100 221 0 18184 0
Current children cumulated CPU time (s) 2.5
Current children cumulated vsize (KiB) 73632

Child status: 20
Real time (s): 2.56768
CPU time (s): 2.56761
CPU user time (s): 2.47362
CPU system time (s): 0.093985
CPU usage (%): 99.9971
Max. virtual memory (cumulated for all children) (KiB): 73632

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

runsolver used 0.007998 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node39 at 2009-04-26 17:08:06
IDJOB=1730358
IDBENCH=24728
IDSOLVER=538
FILE ID=node39/1730358-1240758485
PBS_JOBID= 9187098
Free space on /tmp= 66340 MiB

SOLVER NAME= VARSAT-industrial 2009-03-22
BENCH NAME= SAT07/crafted/Difficult/contest05/sabharwal/grid-pebbling-unsat-grid-pbl-0300.sat05-1350.sat05-1350.reshuffled-07.cnf
COMMAND LINE= HOME/varsat-industrial_static -seed=RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1730358-1240758485/watcher-1730358-1240758485 -o /tmp/evaluation-result-1730358-1240758485/solver-1730358-1240758485 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/varsat-industrial_static -seed=1249372698 HOME/instance-1730358-1240758485.cnf

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

MD5SUM BENCH= 4c3b2816cb16b0fd4134bf2c85ce45d0
RANDOM SEED=1249372698

node39.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.281
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.281
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:       1667552 kB
Buffers:         45152 kB
Cached:         285940 kB
SwapCached:       6324 kB
Active:         157704 kB
Inactive:       182288 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1667552 kB
SwapTotal:     4192956 kB
SwapFree:      4181440 kB
Dirty:            5844 kB
Writeback:           0 kB
Mapped:          13588 kB
Slab:            34412 kB
Committed_AS:   475284 kB
PageTables:       1380 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= 66340 MiB
End job on node39 at 2009-04-26 17:08:09