Trace number 1561043

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
gnovelty+2 2009-03-22? (exit code) 1.57676 1.57772

General information on the benchmark

NameCRAFTED/edgematching/
compact/em_7_3_6_cmp.cnf
MD5SUMc848a5766cfcc1d1c3f26c7818e48eb2
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark105.341
Satisfiable
(Un)Satisfiability was proved
Number of variables1473
Number of clauses11563
Sum of the clauses size37576
Maximum clause length25
Minimum clause length2
Number of clauses of size 10
Number of clauses of size 22381
Number of clauses of size 37024
Number of clauses of size 4708
Number of clauses of size 51300
Number of clauses of size over 5150

Solver Data

0.00/0.07	c +------------------------------+
0.00/0.07	c | gNovelty+, version 2.0       |
0.00/0.07	c +------------------------------+
0.00/0.07	c gnovelty+ -h for help
0.00/0.07	c 
0.00/0.07	c Problem instance: numAtoms = 1473, numClauses = 9182
0.00/0.07	c General parameters: seed = 2053346993, timeout = 10 secs, targetCost = 0, print solution: no
0.00/0.07	c gNovelty+ parameters: walkprob = 0.01, smoothprob = 0.30, noise = adaptive
0.00/0.07	c tries = 1
0.00/0.07	c 
1.49/1.57	Program error, verification of assignment cost fails!

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-1561043-1238760656/watcher-1561043-1238760656 -o /tmp/evaluation-result-1561043-1238760656/solver-1561043-1238760656 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/gnovelty+2 HOME/instance-1561043-1238760656.cnf 2053346993 

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.91 0.97 0.99 3/64 30782
/proc/meminfo: memFree=1762752/2055920 swapFree=4175828/4192956
[pid=30782] ppid=30780 vsize=1017856 CPUtime=0
/proc/30782/stat : 30782 (gnovelty+2) R 30780 30782 30028 0 -1 4194304 166 0 0 0 0 0 0 0 18 0 1 0 1148730579 1042284544 150 1992294400 134512640 135663704 4294956208 18446744073709551615 135160590 0 0 4096 0 0 0 0 17 1 0 0
/proc/30782/statm: 254464 150 96 281 0 254180 0

[startup+0.0769431 s]
/proc/loadavg: 0.91 0.97 0.99 3/64 30782
/proc/meminfo: memFree=1762752/2055920 swapFree=4175828/4192956
[pid=30782] ppid=30780 vsize=1021036 CPUtime=0.07
/proc/30782/stat : 30782 (gnovelty+2) R 30780 30782 30028 0 -1 4194304 1066 0 0 0 7 0 0 0 18 0 1 0 1148730579 1045540864 1049 1992294400 134512640 135663704 4294956208 18446744073709551615 134545174 0 0 4096 0 0 0 0 17 1 0 0
/proc/30782/statm: 255259 1049 117 281 0 254975 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 1021036

[startup+0.102948 s]
/proc/loadavg: 0.91 0.97 0.99 3/64 30782
/proc/meminfo: memFree=1762752/2055920 swapFree=4175828/4192956
[pid=30782] ppid=30780 vsize=1021036 CPUtime=0.09
/proc/30782/stat : 30782 (gnovelty+2) R 30780 30782 30028 0 -1 4194304 1066 0 0 0 9 0 0 0 18 0 1 0 1148730579 1045540864 1049 1992294400 134512640 135663704 4294956208 18446744073709551615 134545153 0 0 4096 0 0 0 0 17 1 0 0
/proc/30782/statm: 255259 1049 117 281 0 254975 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 1021036

[startup+0.301988 s]
/proc/loadavg: 0.91 0.97 0.99 3/64 30782
/proc/meminfo: memFree=1762752/2055920 swapFree=4175828/4192956
[pid=30782] ppid=30780 vsize=1021036 CPUtime=0.29
/proc/30782/stat : 30782 (gnovelty+2) R 30780 30782 30028 0 -1 4194304 1066 0 0 0 29 0 0 0 19 0 1 0 1148730579 1045540864 1049 1992294400 134512640 135663704 4294956208 18446744073709551615 134545169 0 0 4096 0 0 0 0 17 1 0 0
/proc/30782/statm: 255259 1049 117 281 0 254975 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 1021036

[startup+0.701069 s]
/proc/loadavg: 0.91 0.97 0.99 3/64 30782
/proc/meminfo: memFree=1762752/2055920 swapFree=4175828/4192956
[pid=30782] ppid=30780 vsize=1021036 CPUtime=0.69
/proc/30782/stat : 30782 (gnovelty+2) R 30780 30782 30028 0 -1 4194304 1066 0 0 0 69 0 0 0 22 0 1 0 1148730579 1045540864 1049 1992294400 134512640 135663704 4294956208 18446744073709551615 134524874 0 0 4096 0 0 0 0 17 1 0 0
/proc/30782/statm: 255259 1049 117 281 0 254975 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 1021036

[startup+1.50123 s]
/proc/loadavg: 0.91 0.97 0.99 2/65 30783
/proc/meminfo: memFree=1758968/2055920 swapFree=4175828/4192956
[pid=30782] ppid=30780 vsize=1021036 CPUtime=1.49
/proc/30782/stat : 30782 (gnovelty+2) R 30780 30782 30028 0 -1 4194304 1066 0 0 0 149 0 0 0 25 0 1 0 1148730579 1045540864 1049 1992294400 134512640 135663704 4294956208 18446744073709551615 134545909 0 0 4096 0 0 0 0 17 1 0 0
/proc/30782/statm: 255259 1049 117 281 0 254975 0
Current children cumulated CPU time (s) 1.49
Current children cumulated vsize (KiB) 1021036

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

Child status: 255
Real time (s): 1.57772
CPU time (s): 1.57676
CPU user time (s): 1.57176
CPU system time (s): 0.004999
CPU usage (%): 99.9393
Max. virtual memory (cumulated for all children) (KiB): 1021036

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

runsolver used 0.003999 second user time and 0.011998 second system time

The end

Launcher Data

Begin job on node33 at 2009-04-03 14:10:56
IDJOB=1561043
IDBENCH=70907
IDSOLVER=548
FILE ID=node33/1561043-1238760656
PBS_JOBID= 9085485
Free space on /tmp= 66524 MiB

SOLVER NAME= gnovelty+2 2009-03-22
BENCH NAME= SAT09/APPLICATIONS/edgematching/compact/em_7_3_6_cmp.cnf
COMMAND LINE= HOME/gnovelty+2 BENCHNAME RANDOMSEED
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1561043-1238760656/watcher-1561043-1238760656 -o /tmp/evaluation-result-1561043-1238760656/solver-1561043-1238760656 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/gnovelty+2 HOME/instance-1561043-1238760656.cnf 2053346993

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

MD5SUM BENCH= c848a5766cfcc1d1c3f26c7818e48eb2
RANDOM SEED=2053346993

node33.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.266
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.266
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:       1763168 kB
Buffers:         41788 kB
Cached:         174412 kB
SwapCached:      10920 kB
Active:          83632 kB
Inactive:       145148 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1763168 kB
SwapTotal:     4192956 kB
SwapFree:      4175828 kB
Dirty:            1596 kB
Writeback:           0 kB
Mapped:          18232 kB
Slab:            49896 kB
Committed_AS:  3327368 kB
PageTables:       1408 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= 66520 MiB
End job on node33 at 2009-04-03 14:10:57