Trace number 1736390

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
satake 2009-03-22UNSAT 0.015997 0.0145659

General information on the benchmark

NameCRAFTED/parity-games/
instance_n3_i4_pp_ci_ce.cnf
MD5SUMa3abb10f5ab4ed4f5093550970c0200d
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.007998
Satisfiable
(Un)Satisfiability was proved
Number of variables696
Number of clauses3122
Sum of the clauses size9414
Maximum clause length6
Minimum clause length2
Number of clauses of size 10
Number of clauses of size 21091
Number of clauses of size 31138
Number of clauses of size 4650
Number of clauses of size 5240
Number of clauses of size over 53

Solver Data 

0.00/0.01	c Benchmark name    : HOME/instance-1736390-1240811660.cnf
0.00/0.01	c Thread Num        :            3
0.00/0.01	c restarts          :            1
0.00/0.01	c conflicts         :           88
0.00/0.01	c decisions         :          224           (    27231 / sec      )
0.00/0.01	c propagations      :         6328           (   769268 / sec      )
0.00/0.01	c inspects          :        22315           (  2712740 / sec      )
0.00/0.01	c conflict literals :          490           (    27.73 % deleted  )
0.00/0.01	c cpu time          :         0.01           
0.00/0.01	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-1736390-1240811660/watcher-1736390-1240811660 -o /tmp/evaluation-result-1736390-1240811660/solver-1736390-1240811660 -C 1200 -W 1800 -M 1800 --output-limit 1,15 --cleanup-all-ipc-queues HOME/satake HOME/instance-1736390-1240811660.cnf 3 1200 

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: 1.00 1.00 1.09 3/64 29202
/proc/meminfo: memFree=1393456/2055920 swapFree=4192812/4192956
[pid=29202] ppid=29200 vsize=1280 CPUtime=0
/proc/29202/stat : 29202 (satake) S 29200 29202 29078 0 -1 4194304 165 0 0 0 0 0 0 0 18 0 4 0 109199646 1310720 150 1992294400 134512640 135180984 4294956208 18446744073709551615 134573496 0 0 4096 0 18446744073709551615 0 0 17 1 0 0
/proc/29202/statm: 320 150 68 163 0 155 0
[pid=29202/tid=29203] ppid=29200 vsize=1280 CPUtime=0
/proc/29202/task/29203/stat : 29203 (satake) R 29200 29202 29078 0 -1 4194368 7 0 0 0 0 0 0 0 19 0 4 0 109199646 1310720 150 1992294400 134512640 135180984 4294956208 18446744073709551615 134580407 0 0 4096 0 0 0 0 -1 1 0 0
[pid=29202/tid=29204] ppid=29200 vsize=1280 CPUtime=0
/proc/29202/task/29204/stat : 29204 (satake) R 29200 29202 29078 0 -1 4194368 75 0 0 0 0 0 0 0 19 0 4 0 109199646 1310720 150 1992294400 134512640 135180984 4294956208 18446744073709551615 134520662 0 0 4096 0 0 0 0 -1 1 0 0
[pid=29202/tid=29205] ppid=29200 vsize=1280 CPUtime=0
/proc/29202/task/29205/stat : 29205 (satake) R 29200 29202 29078 0 -1 4194368 0 0 0 0 0 0 0 0 19 0 4 0 109199646 1310720 150 1992294400 134512640 135180984 4294956208 18446744073709551615 134705812 0 0 4096 0 0 0 0 -1 1 0 0

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

Child status: 3
Real time (s): 0.0145659
CPU time (s): 0.015997
CPU user time (s): 0.015997
CPU system time (s): 0
CPU usage (%): 109.825
Max. virtual memory (cumulated for all children) (KiB): 0


getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.015997
system time used= 0
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 248
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= 10
involuntary context switches= 1

runsolver used 0.004999 second user time and 0.004999 second system time

The end

Launcher Data 

Begin job on node10 at 2009-04-27 07:54:20
IDJOB=1736390
IDBENCH=71624
IDSOLVER=553
FILE ID=node10/1736390-1240811660
PBS_JOBID= 9187459
Free space on /tmp= 66404 MiB

SOLVER NAME= satake 2009-03-22
BENCH NAME= SAT09/CRAFTED/parity-games/instance_n3_i4_pp_ci_ce.cnf
COMMAND LINE= HOME/satake BENCHNAME MAXNBTHREAD TIMEOUT
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1736390-1240811660/watcher-1736390-1240811660 -o /tmp/evaluation-result-1736390-1240811660/solver-1736390-1240811660 -C 1200 -W 1800 -M 1800 --output-limit 1,15 --cleanup-all-ipc-queues HOME/satake HOME/instance-1736390-1240811660.cnf 3 1200

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

MD5SUM BENCH= a3abb10f5ab4ed4f5093550970c0200d
RANDOM SEED=533706460

node10.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.263
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	: 5931.00
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.263
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:       1393872 kB
Buffers:         73448 kB
Cached:         507544 kB
SwapCached:          0 kB
Active:         168416 kB
Inactive:       426488 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1393872 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:             796 kB
Writeback:           0 kB
Mapped:          23648 kB
Slab:            53152 kB
Committed_AS:   442184 kB
PageTables:       1372 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= 66404 MiB
End job on node10 at 2009-04-27 07:54:20