Trace number 1733100

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
SApperloT baseSAT 0.568912 0.569334

General information on the benchmark

NameCRAFTED/ramseycube/
Q3inK11.cnf
MD5SUM1fdca9b41a2ccb9f1b1754fb775769f0
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.560914
Satisfiable
(Un)Satisfiability was proved
Number of variables55
Number of clauses277200
Sum of the clauses size3326400
Maximum clause length12
Minimum clause length12
Number of clauses of size 10
Number of clauses of size 20
Number of clauses of size 30
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 5277200

Solver Data 

0.49/0.56	
0.49/0.56	s SATISFIABLE
0.49/0.56	v -1 2 -3 4 5 6 7 -8 -9 -10 11 12 -13 14 15 16 -17 -18 -19 20 21 22 -23 -24 -25 -26 -27 -28 29 30 31 -32 -33 -34 -35 -36 37 -38 39 40 41 -42 43 -44 45 -46 47 -48 49 -50 51 -52 -53 54 55  0

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1733100-1240784961/watcher-1733100-1240784961 -o /tmp/evaluation-result-1733100-1240784961/solver-1733100-1240784961 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/SApperloT-base -seed=1175477646 HOME/instance-1733100-1240784961.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: 1.78 1.33 1.12 3/64 9572
/proc/meminfo: memFree=1691384/2055920 swapFree=4182076/4192956
[pid=9572] ppid=9570 vsize=2532 CPUtime=0
/proc/9572/stat : 9572 (SApperloT-base) R 9570 9572 9119 0 -1 4194304 177 0 0 0 0 0 0 0 18 0 1 0 106522216 2592768 161 1992294400 134512640 135674940 4294956192 18446744073709551615 135172670 0 0 4096 0 0 0 0 17 1 0 0
/proc/9572/statm: 633 161 90 283 0 347 0

[startup+0.100723 s]
/proc/loadavg: 1.78 1.33 1.12 3/64 9572
/proc/meminfo: memFree=1691384/2055920 swapFree=4182076/4192956
[pid=9572] ppid=9570 vsize=7884 CPUtime=0.09
/proc/9572/stat : 9572 (SApperloT-base) R 9570 9572 9119 0 -1 4194304 1502 0 0 0 9 0 0 0 18 0 1 0 106522216 8073216 1486 1992294400 134512640 135674940 4294956192 18446744073709551615 135172670 0 0 4096 0 0 0 0 17 1 0 0
/proc/9572/statm: 1971 1489 90 283 0 1685 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 7884

[startup+0.201732 s]
/proc/loadavg: 1.78 1.33 1.12 3/64 9572
/proc/meminfo: memFree=1691384/2055920 swapFree=4182076/4192956
[pid=9572] ppid=9570 vsize=13736 CPUtime=0.19
/proc/9572/stat : 9572 (SApperloT-base) R 9570 9572 9119 0 -1 4194304 3096 0 0 0 18 1 0 0 18 0 1 0 106522216 14065664 2849 1992294400 134512640 135674940 4294956192 18446744073709551615 135172670 0 0 4096 0 0 0 0 17 1 0 0
/proc/9572/statm: 3434 2850 90 283 0 3148 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 13736

[startup+0.301741 s]
/proc/loadavg: 1.78 1.33 1.12 3/64 9572
/proc/meminfo: memFree=1691384/2055920 swapFree=4182076/4192956
[pid=9572] ppid=9570 vsize=18944 CPUtime=0.29
/proc/9572/stat : 9572 (SApperloT-base) R 9570 9572 9119 0 -1 4194304 4472 0 0 0 28 1 0 0 19 0 1 0 106522216 19398656 4225 1992294400 134512640 135674940 4294956192 18446744073709551615 135172670 0 0 4096 0 0 0 0 17 1 0 0
/proc/9572/statm: 4736 4226 90 283 0 4450 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 18944

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

[startup+0.401751 s]
/proc/loadavg: 1.78 1.33 1.12 3/64 9572
/proc/meminfo: memFree=1691384/2055920 swapFree=4182076/4192956
[pid=9572] ppid=9570 vsize=24604 CPUtime=0.39
/proc/9572/stat : 9572 (SApperloT-base) R 9570 9572 9119 0 -1 4194304 5850 0 0 0 37 2 0 0 19 0 1 0 106522216 25194496 5603 1992294400 134512640 135674940 4294956192 18446744073709551615 134543046 0 0 4096 0 0 0 0 17 1 0 0
/proc/9572/statm: 6151 5603 90 283 0 5865 0
Current children cumulated CPU time (s) 0.39
Current children cumulated vsize (KiB) 24604

[startup+0.501761 s]
/proc/loadavg: 1.78 1.33 1.12 3/64 9572
/proc/meminfo: memFree=1691384/2055920 swapFree=4182076/4192956
[pid=9572] ppid=9570 vsize=28408 CPUtime=0.49
/proc/9572/stat : 9572 (SApperloT-base) R 9570 9572 9119 0 -1 4194304 6718 0 0 0 46 3 0 0 20 0 1 0 106522216 29089792 6470 1992294400 134512640 135674940 4294956192 18446744073709551615 134564250 0 0 4096 0 0 0 0 17 1 0 0
/proc/9572/statm: 7102 6470 98 283 0 6816 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 28408

Child status: 0
Real time (s): 0.569334
CPU time (s): 0.568912
CPU user time (s): 0.527919
CPU system time (s): 0.040993
CPU usage (%): 99.9259
Max. virtual memory (cumulated for all children) (KiB): 28408

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

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node70 at 2009-04-27 00:29:22
IDJOB=1733100
IDBENCH=71134
IDSOLVER=509
FILE ID=node70/1733100-1240784961
PBS_JOBID= 9187240
Free space on /tmp= 66296 MiB

SOLVER NAME= SApperloT base
BENCH NAME= SAT09/CRAFTED/ramseycube/Q3inK11.cnf
COMMAND LINE= HOME/SApperloT-base -seed=RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1733100-1240784961/watcher-1733100-1240784961 -o /tmp/evaluation-result-1733100-1240784961/solver-1733100-1240784961 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/SApperloT-base -seed=1175477646 HOME/instance-1733100-1240784961.cnf

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

MD5SUM BENCH= 1fdca9b41a2ccb9f1b1754fb775769f0
RANDOM SEED=1175477646

node70.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.213
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.213
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:       1691864 kB
Buffers:         40960 kB
Cached:         256372 kB
SwapCached:       4996 kB
Active:         141760 kB
Inactive:       164200 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1691864 kB
SwapTotal:     4192956 kB
SwapFree:      4182076 kB
Dirty:           12788 kB
Writeback:           0 kB
Mapped:          14916 kB
Slab:            44220 kB
Committed_AS:   381116 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= 66292 MiB
End job on node70 at 2009-04-27 00:29:22