Trace number 1553229

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
hybridGM 1Signal 0.160975 0.16214

General information on the benchmark

NameAPPLICATIONS/bitverif/
minor/minor032.cnf
MD5SUM93c9f18c75548b864ec69c2789cae658
Bench CategoryAPPLICATION (applications instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.418935
Satisfiable
(Un)Satisfiability was proved
Number of variables4210
Number of clauses12053
Sum of the clauses size28121
Maximum clause length3
Minimum clause length1
Number of clauses of size 12
Number of clauses of size 28034
Number of clauses of size 34017
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 50

Solver Data 

0.03/0.05	c Heuristic: AdaptG2WSAT 
0.03/0.05	c Hybrid barrier : 1 
0.03/0.05	c Problem instance: numAtoms = 4210, numClauses = 12053, numLiterals = 28121
0.03/0.05	c General parameters: seed=1874844058, cutoff=1000000000, targetCost = 0, print solution: yes
0.03/0.05	c gNovelty+ parameters: noise = 0, walkprob = 1, smoothprob = 33
0.03/0.05	c tries = 1
0.03/0.05	c

Verifier Data 

ERROR: Unexpected answer ! (SATISFIABLE/UNSATISFIABLE expected)
Got answer: <no 's ' line found>

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1553229-1238712537/watcher-1553229-1238712537 -o /tmp/evaluation-result-1553229-1238712537/solver-1553229-1238712537 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/hybridGM HOME/instance-1553229-1238712537.cnf 1874844058 

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.12 3/80 16354
/proc/meminfo: memFree=1515708/2055920 swapFree=4163588/4192956
[pid=16354] ppid=16352 vsize=260600 CPUtime=0
/proc/16354/stat : 16354 (hybridGM) R 16352 16354 16262 0 -1 4194304 930 0 0 0 0 0 0 0 20 0 1 0 1143917402 266854400 914 1992294400 134512640 135204289 4294956224 18446744073709551615 134542712 0 0 4096 0 0 0 0 17 1 0 0
/proc/16354/statm: 65150 922 54 168 0 64980 0

[startup+0.047193 s]
/proc/loadavg: 1.00 1.00 1.12 3/80 16354
/proc/meminfo: memFree=1515708/2055920 swapFree=4163588/4192956
[pid=16354] ppid=16352 vsize=268412 CPUtime=0.03
/proc/16354/stat : 16354 (hybridGM) R 16352 16354 16262 0 -1 4194304 2780 0 0 0 3 0 0 0 20 0 1 0 1143917402 274853888 2763 1992294400 134512640 135204289 4294956224 18446744073709551615 134548408 0 0 4096 0 0 0 0 17 1 0 0
/proc/16354/statm: 67103 2771 56 168 0 66933 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 268412

[startup+0.101199 s]
/proc/loadavg: 1.00 1.00 1.12 3/80 16354
/proc/meminfo: memFree=1515708/2055920 swapFree=4163588/4192956
[pid=16354] ppid=16352 vsize=268416 CPUtime=0.09
/proc/16354/stat : 16354 (hybridGM) R 16352 16354 16262 0 -1 4195840 9056 0 0 0 5 4 0 0 20 0 1 0 1143917402 274857984 4703 1992294400 134512640 135204289 4294956224 18446744073709551615 134536656 0 0 4096 0 0 0 0 17 1 0 0
/proc/16354/statm: 67104 4703 63 168 0 66934 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 268416

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

Child ended because it received signal 11 (SIGSEGV)
Child dumped core
Real time (s): 0.16214
CPU time (s): 0.160975
CPU user time (s): 0.051992
CPU system time (s): 0.108983
CPU usage (%): 99.2814
Max. virtual memory (cumulated for all children) (KiB): 268416

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.051992
system time used= 0.108983
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 17351
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.005999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node90 at 2009-04-03 00:48:58
IDJOB=1553229
IDBENCH=70757
IDSOLVER=533
FILE ID=node90/1553229-1238712537
PBS_JOBID= 9085286
Free space on /tmp= 66532 MiB

SOLVER NAME= hybridGM 1
BENCH NAME= SAT09/APPLICATIONS/bitverif/minor/minor032.cnf
COMMAND LINE= HOME/hybridGM BENCHNAME RANDOMSEED 
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1553229-1238712537/watcher-1553229-1238712537 -o /tmp/evaluation-result-1553229-1238712537/solver-1553229-1238712537 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/hybridGM HOME/instance-1553229-1238712537.cnf 1874844058 

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

MD5SUM BENCH= 93c9f18c75548b864ec69c2789cae658
RANDOM SEED=1874844058

node90.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.234
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.234
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:       1516124 kB
Buffers:         83124 kB
Cached:         361208 kB
SwapCached:      19088 kB
Active:         234012 kB
Inactive:       230852 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1516124 kB
SwapTotal:     4192956 kB
SwapFree:      4163588 kB
Dirty:            1200 kB
Writeback:           0 kB
Mapped:          25684 kB
Slab:            59164 kB
Committed_AS:  2576960 kB
PageTables:       2668 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= 66512 MiB
End job on node90 at 2009-04-03 00:48:58