Trace number 1717445

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+-V.2-T 2009-03-22? (exit code) 0.082987 0.0825119

General information on the benchmark

Nameindustrial/palacios/uts/
uts-l06-ipc5-h35-unknown.cnf
MD5SUM5e044c9f89a347ff1731180a403693c1
Bench CategoryAPPLICATION (applications instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark19.512
Satisfiable
(Un)Satisfiability was proved
Number of variables196689
Number of clauses912286
Sum of the clauses size2345308
Maximum clause length591
Minimum clause length1
Number of clauses of size 1276
Number of clauses of size 2717679
Number of clauses of size 3188110
Number of clauses of size 41747
Number of clauses of size 5138
Number of clauses of size over 54336

Solver Data 

0.00/0.06	c +------------------------------+
0.00/0.06	c | gNovelty+, version 2.0       |
0.00/0.06	c +------------------------------+
0.00/0.06	c gnovelty+ -h for help
0.00/0.06	c 
0.00/0.06	ERROR - clause 12043 is too long

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

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.99 0.98 1.00 2/64 16956
/proc/meminfo: memFree=1514352/2055920 swapFree=4180592/4192956
[pid=16956] ppid=16954 vsize=66796 CPUtime=0
/proc/16956/stat : 16956 (gnovelty+) R 16954 16956 14568 0 -1 4194304 578 0 0 0 0 0 0 0 18 0 1 0 90863614 68399104 563 1992294400 134512640 135728688 4294956192 18446744073709551615 135136966 0 0 4096 0 0 0 0 17 1 0 0
/proc/16956/statm: 16699 566 97 296 0 16400 0

[startup+0.0722679 s]
/proc/loadavg: 0.99 0.98 1.00 2/64 16956
/proc/meminfo: memFree=1514352/2055920 swapFree=4180592/4192956
[pid=16956] ppid=16954 vsize=75836 CPUtime=0.07
/proc/16956/stat : 16956 (gnovelty+) R 16954 16956 14568 0 -1 4194304 3075 0 0 0 6 1 0 0 18 0 1 0 90863614 77656064 2576 1992294400 134512640 135728688 4294956192 18446744073709551615 135133231 0 0 4096 0 0 0 0 17 1 0 0
/proc/16956/statm: 18959 2576 106 296 0 18660 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 75836

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

[startup+0.0722679 s]
/proc/loadavg: 0.99 0.98 1.00 2/64 16956
/proc/meminfo: memFree=1514352/2055920 swapFree=4180592/4192956
[pid=16956] ppid=16954 vsize=75836 CPUtime=0.07
/proc/16956/stat : 16956 (gnovelty+) R 16954 16956 14568 0 -1 4194304 3075 0 0 0 6 1 0 0 18 0 1 0 90863614 77656064 2576 1992294400 134512640 135728688 4294956192 18446744073709551615 135133231 0 0 4096 0 0 0 0 17 1 0 0
/proc/16956/statm: 18959 2576 106 296 0 18660 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 75836

Child status: 255
Real time (s): 0.0825119
CPU time (s): 0.082987
CPU user time (s): 0.070989
CPU system time (s): 0.011998
CPU usage (%): 100.576
Max. virtual memory (cumulated for all children) (KiB): 75836

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

runsolver used 0.001999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node24 at 2009-04-25 04:58:21
IDJOB=1717445
IDBENCH=20414
IDSOLVER=552
FILE ID=node24/1717445-1240628300
PBS_JOBID= 9186387
Free space on /tmp= 66224 MiB

SOLVER NAME= gNovelty+-V.2-T 2009-03-22
BENCH NAME= SAT07/industrial/palacios/uts/uts-l06-ipc5-h35-unknown.cnf
COMMAND LINE= HOME/gnovelty+ BENCHNAME RANDOMSEED MAXNBTHREAD
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1717445-1240628300/watcher-1717445-1240628300 -o /tmp/evaluation-result-1717445-1240628300/solver-1717445-1240628300 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/gnovelty+ HOME/instance-1717445-1240628300.cnf 344274647 2

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

MD5SUM BENCH= 5e044c9f89a347ff1731180a403693c1
RANDOM SEED=344274647

node24.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.232
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.232
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:       1514832 kB
Buffers:         55232 kB
Cached:         411544 kB
SwapCached:       6708 kB
Active:         174860 kB
Inactive:       301096 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1514832 kB
SwapTotal:     4192956 kB
SwapFree:      4180592 kB
Dirty:           18184 kB
Writeback:           0 kB
Mapped:          13996 kB
Slab:            51060 kB
Committed_AS:   349560 kB
PageTables:       1440 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= 66224 MiB
End job on node24 at 2009-04-25 04:58:21