Trace number 1784676

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
clasp 1.2.0-SAT09-32UNSAT 0.067989 0.068022

General information on the benchmark

Namecrafted/Medium/contest05/pebbling/
unsat-grid-pbl-0080.sat05-1344.reshuffled-07.cnf
MD5SUM35f2aba974a0579245ba9b669f0484ae
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.067989
Satisfiable
(Un)Satisfiability was proved
Number of variables6480
Number of clauses12722
Sum of the clauses size50722
Maximum clause length4
Minimum clause length1
Number of clauses of size 12
Number of clauses of size 280
Number of clauses of size 30
Number of clauses of size 412640
Number of clauses of size 50
Number of clauses of size over 50

Solver Data 

0.03/0.06	c clasp version 1.2.0-SAT09 
0.03/0.06	c Reading from ...864336/instance-1784676-1241864336.cnf
0.03/0.06	c Reading      : Done(0.010s)
0.03/0.06	c Preprocessing: |-Done(0.050s)
0.03/0.06	
0.03/0.06	c Models    : 0     
0.03/0.06	c Time         : 0.060s (Solve: 0.000s)
0.03/0.06	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-1784676-1241864336/watcher-1784676-1241864336 -o /tmp/evaluation-result-1784676-1241864336/solver-1784676-1241864336 -C 5000 -W 6000 -M 1800 HOME/clasp --file=HOME/instance-1784676-1241864336.cnf --dimacs --number=1 --sat-p=20,25,150 --hParam=0,512 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 5000 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 5030 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 6000 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: 0.99 0.97 0.89 3/64 27130
/proc/meminfo: memFree=987208/2055920 swapFree=4182092/4192956
[pid=27130] ppid=27128 vsize=2364 CPUtime=0
/proc/27130/stat : 27130 (clasp) R 27128 27130 27058 0 -1 4194304 350 0 0 0 0 0 0 0 18 0 1 0 214467220 2420736 334 1992294400 134512640 136057169 4294956160 18446744073709551615 135502702 0 0 4096 16386 0 0 0 17 1 0 0
/proc/27130/statm: 591 334 144 377 0 211 0

[startup+0.037416 s]
/proc/loadavg: 0.99 0.97 0.89 3/64 27130
/proc/meminfo: memFree=987208/2055920 swapFree=4182092/4192956
[pid=27130] ppid=27128 vsize=3668 CPUtime=0.03
/proc/27130/stat : 27130 (clasp) R 27128 27130 27058 0 -1 4194304 730 0 0 0 3 0 0 0 18 0 1 0 214467220 3756032 664 1992294400 134512640 136057169 4294956160 18446744073709551615 134768694 0 0 4096 16386 0 0 0 17 1 0 0
/proc/27130/statm: 917 664 170 377 0 537 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 3668

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

[startup+0.037416 s]
/proc/loadavg: 0.99 0.97 0.89 3/64 27130
/proc/meminfo: memFree=987208/2055920 swapFree=4182092/4192956
[pid=27130] ppid=27128 vsize=3668 CPUtime=0.03
/proc/27130/stat : 27130 (clasp) R 27128 27130 27058 0 -1 4194304 730 0 0 0 3 0 0 0 18 0 1 0 214467220 3756032 664 1992294400 134512640 136057169 4294956160 18446744073709551615 134768694 0 0 4096 16386 0 0 0 17 1 0 0
/proc/27130/statm: 917 664 170 377 0 537 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 3668

Child status: 20
Real time (s): 0.068022
CPU time (s): 0.067989
CPU user time (s): 0.06499
CPU system time (s): 0.002999
CPU usage (%): 99.9514
Max. virtual memory (cumulated for all children) (KiB): 3668

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.06499
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= 753
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.005999 second system time

The end

Launcher Data 

Begin job on node11 at 2009-05-09 12:18:56
IDJOB=1784676
IDBENCH=24589
IDSOLVER=637
FILE ID=node11/1784676-1241864336
PBS_JOBID= 9264601
Free space on /tmp= 66216 MiB

SOLVER NAME= clasp 1.2.0-SAT09-32
BENCH NAME= SAT07/crafted/Medium/contest05/pebbling/unsat-grid-pbl-0080.sat05-1344.reshuffled-07.cnf
COMMAND LINE= HOME/clasp --file=BENCHNAME --dimacs --number=1 --sat-p=20,25,150 --hParam=0,512
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1784676-1241864336/watcher-1784676-1241864336 -o /tmp/evaluation-result-1784676-1241864336/solver-1784676-1241864336 -C 5000 -W 6000 -M 1800  HOME/clasp --file=HOME/instance-1784676-1241864336.cnf --dimacs --number=1 --sat-p=20,25,150 --hParam=0,512

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

MD5SUM BENCH= 35f2aba974a0579245ba9b669f0484ae
RANDOM SEED=1043943663

node11.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.214
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.214
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:        987688 kB
Buffers:         48584 kB
Cached:         927472 kB
SwapCached:       4708 kB
Active:         167448 kB
Inactive:       816492 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        987688 kB
SwapTotal:     4192956 kB
SwapFree:      4182092 kB
Dirty:            2136 kB
Writeback:           0 kB
Mapped:          14444 kB
Slab:            70200 kB
Committed_AS:   728376 kB
PageTables:       1448 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= 66216 MiB
End job on node11 at 2009-05-09 12:18:56