Trace number 1730342

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
HydraSAT-Flat 2009-03-22-FlatUNSAT 1.64175 1.64132

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 

1.59/1.63	
1.59/1.63	c decisions : 0
1.59/1.63	c conflicts : 0
1.59/1.63	c Memory limit 1620 MiB
1.59/1.63	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-1730342-1240758394/watcher-1730342-1240758394 -o /tmp/evaluation-result-1730342-1240758394/solver-1730342-1240758394 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/hydrasat-flat HOME/instance-1730342-1240758394.cnf -rs 1283588002 -co memory_limit 1800 

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/65 9394
/proc/meminfo: memFree=1849128/2055920 swapFree=4192952/4192956
[pid=9394] ppid=9392 vsize=2300 CPUtime=0
/proc/9394/stat : 9394 (hydrasat-flat) R 9392 9394 9207 0 -1 4194304 189 0 0 0 0 0 0 0 18 0 1 0 103868655 2355200 173 1992294400 134512640 135819388 4294956160 18446744073709551615 135210678 0 0 4096 1 0 0 0 17 1 0 0
/proc/9394/statm: 575 174 119 319 0 253 0

[startup+0.0852979 s]
/proc/loadavg: 0.99 0.97 0.99 3/65 9394
/proc/meminfo: memFree=1849128/2055920 swapFree=4192952/4192956
[pid=9394] ppid=9392 vsize=5072 CPUtime=0.07
/proc/9394/stat : 9394 (hydrasat-flat) R 9392 9394 9207 0 -1 4194304 945 0 0 0 7 0 0 0 18 0 1 0 103868655 5193728 929 1992294400 134512640 135819388 4294956160 18446744073709551615 135270494 0 0 4096 1 0 0 0 17 1 0 0
/proc/9394/statm: 1268 930 119 319 0 946 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 5072

[startup+0.102299 s]
/proc/loadavg: 0.99 0.97 0.99 3/65 9394
/proc/meminfo: memFree=1849128/2055920 swapFree=4192952/4192956
[pid=9394] ppid=9392 vsize=5732 CPUtime=0.09
/proc/9394/stat : 9394 (hydrasat-flat) R 9392 9394 9207 0 -1 4194304 1105 0 0 0 9 0 0 0 18 0 1 0 103868655 5869568 1089 1992294400 134512640 135819388 4294956160 18446744073709551615 135210678 0 0 4096 1 0 0 0 17 1 0 0
/proc/9394/statm: 1433 1089 119 319 0 1111 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 5732

[startup+0.302322 s]
/proc/loadavg: 0.99 0.97 0.99 3/65 9394
/proc/meminfo: memFree=1849128/2055920 swapFree=4192952/4192956
[pid=9394] ppid=9392 vsize=15072 CPUtime=0.29
/proc/9394/stat : 9394 (hydrasat-flat) R 9392 9394 9207 0 -1 4194304 3580 0 0 0 28 1 0 0 19 0 1 0 103868655 15433728 3564 1992294400 134512640 135819388 4294956160 18446744073709551615 135210678 0 0 4096 1 0 0 0 17 1 0 0
/proc/9394/statm: 3768 3564 125 319 0 3446 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 15072

[startup+0.702368 s]
/proc/loadavg: 0.99 0.97 0.99 3/65 9394
/proc/meminfo: memFree=1849128/2055920 swapFree=4192952/4192956
[pid=9394] ppid=9392 vsize=20708 CPUtime=0.69
/proc/9394/stat : 9394 (hydrasat-flat) R 9392 9394 9207 0 -1 4194304 5056 0 0 0 67 2 0 0 23 0 1 0 103868655 21204992 4951 1992294400 134512640 135819388 4294956160 18446744073709551615 134681355 0 0 4096 1 0 0 0 17 1 0 0
/proc/9394/statm: 5177 4951 127 319 0 4855 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 20708

[startup+1.50146 s]
/proc/loadavg: 0.99 0.97 0.99 2/66 9395
/proc/meminfo: memFree=1828576/2055920 swapFree=4192952/4192956
[pid=9394] ppid=9392 vsize=29512 CPUtime=1.49
/proc/9394/stat : 9394 (hydrasat-flat) R 9392 9394 9207 0 -1 4194304 7389 0 0 0 146 3 0 0 25 0 1 0 103868655 30220288 6979 1992294400 134512640 135819388 4294956160 18446744073709551615 135210678 0 0 4096 1 0 0 0 17 1 0 0
/proc/9394/statm: 7378 6979 128 319 0 7056 0
Current children cumulated CPU time (s) 1.49
Current children cumulated vsize (KiB) 29512

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

[startup+1.60147 s]
/proc/loadavg: 0.99 0.97 0.99 2/66 9395
/proc/meminfo: memFree=1828576/2055920 swapFree=4192952/4192956
[pid=9394] ppid=9392 vsize=30568 CPUtime=1.59
/proc/9394/stat : 9394 (hydrasat-flat) R 9392 9394 9207 0 -1 4194304 7712 0 0 0 156 3 0 0 25 0 1 0 103868655 31301632 7302 1992294400 134512640 135819388 4294956160 18446744073709551615 135210678 0 0 4096 1 0 0 0 17 1 0 0
/proc/9394/statm: 7642 7302 128 319 0 7320 0
Current children cumulated CPU time (s) 1.59
Current children cumulated vsize (KiB) 30568

Child status: 20
Real time (s): 1.64132
CPU time (s): 1.64175
CPU user time (s): 1.59876
CPU system time (s): 0.042993
CPU usage (%): 100.026
Max. virtual memory (cumulated for all children) (KiB): 30568

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

runsolver used 0.003999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node88 at 2009-04-26 17:06:35
IDJOB=1730342
IDBENCH=24728
IDSOLVER=519
FILE ID=node88/1730342-1240758394
PBS_JOBID= 9187130
Free space on /tmp= 66544 MiB

SOLVER NAME= HydraSAT-Flat 2009-03-22-Flat
BENCH NAME= SAT07/crafted/Difficult/contest05/sabharwal/grid-pebbling-unsat-grid-pbl-0300.sat05-1350.sat05-1350.reshuffled-07.cnf
COMMAND LINE= DIR/hydrasat-flat BENCHNAME -rs RANDOMSEED -co memory_limit MEMLIMIT
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1730342-1240758394/watcher-1730342-1240758394 -o /tmp/evaluation-result-1730342-1240758394/solver-1730342-1240758394 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/hydrasat-flat HOME/instance-1730342-1240758394.cnf -rs 1283588002 -co memory_limit 1800

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

MD5SUM BENCH= 4c3b2816cb16b0fd4134bf2c85ce45d0
RANDOM SEED=1283588002

node88.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.229
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.229
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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1849544 kB
Buffers:         16184 kB
Cached:         107436 kB
SwapCached:          4 kB
Active:          40084 kB
Inactive:        97852 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1849544 kB
SwapTotal:     4192956 kB
SwapFree:      4192952 kB
Dirty:            6348 kB
Writeback:           0 kB
Mapped:          24048 kB
Slab:            54316 kB
Committed_AS:   276688 kB
PageTables:       1444 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= 66544 MiB
End job on node88 at 2009-04-26 17:06:37