Trace number 1717548

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-H 2009-03-22? (exit code) 0.071988 0.072588

General information on the benchmark

Nameindustrial/palacios/uts/
uts-l06-ipc5-h33-unknown.cnf
MD5SUM6197e38464facb30636a5a3ad5b2f0b5
Bench CategoryAPPLICATION (applications instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark77.2523
Satisfiable
(Un)Satisfiability was proved
Number of variables172950
Number of clauses837466
Sum of the clauses size2168190
Maximum clause length591
Minimum clause length1
Number of clauses of size 1276
Number of clauses of size 2666462
Number of clauses of size 3164950
Number of clauses of size 41526
Number of clauses of size 5129
Number of clauses of size over 54123

Solver Data 

0.00/0.05	c +------------------------------+
0.00/0.05	c | gNovelty+, version 2.0       |
0.00/0.05	c +------------------------------+
0.00/0.05	c gnovelty+ -h for help
0.00/0.05	c 
0.00/0.05	ERROR - clause 10361 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-1717548-1240628939/watcher-1717548-1240628939 -o /tmp/evaluation-result-1717548-1240628939/solver-1717548-1240628939 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/gnovelty+ HOME/instance-1717548-1240628939.cnf 1320348674 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: 1.00 1.00 1.00 3/64 11394
/proc/meminfo: memFree=988328/2055920 swapFree=4192956/4192956
[pid=11394] ppid=11392 vsize=66272 CPUtime=0
/proc/11394/stat : 11394 (gnovelty+) R 11392 11394 10630 0 -1 4194304 555 0 0 0 0 0 0 0 18 0 1 0 90926673 67862528 540 1992294400 134512640 135730148 4294956192 18446744073709551615 135138454 0 0 4096 0 0 0 0 17 1 0 0
/proc/11394/statm: 16601 541 98 297 0 16301 0

[startup+0.010359 s]
/proc/loadavg: 1.00 1.00 1.00 3/64 11394
/proc/meminfo: memFree=988328/2055920 swapFree=4192956/4192956
[pid=11394] ppid=11392 vsize=67448 CPUtime=0
/proc/11394/stat : 11394 (gnovelty+) R 11392 11394 10630 0 -1 4194304 898 0 0 0 0 0 0 0 18 0 1 0 90926673 69066752 785 1992294400 134512640 135730148 4294956192 18446744073709551615 135138454 0 0 4096 0 0 0 0 17 1 0 0
/proc/11394/statm: 16862 788 98 297 0 16562 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 67448

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

[startup+0.010359 s]
/proc/loadavg: 1.00 1.00 1.00 3/64 11394
/proc/meminfo: memFree=988328/2055920 swapFree=4192956/4192956
[pid=11394] ppid=11392 vsize=67448 CPUtime=0
/proc/11394/stat : 11394 (gnovelty+) R 11392 11394 10630 0 -1 4194304 898 0 0 0 0 0 0 0 18 0 1 0 90926673 69066752 785 1992294400 134512640 135730148 4294956192 18446744073709551615 135138454 0 0 4096 0 0 0 0 17 1 0 0
/proc/11394/statm: 16862 788 98 297 0 16562 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 67448

Child status: 255
Real time (s): 0.072588
CPU time (s): 0.071988
CPU user time (s): 0.06099
CPU system time (s): 0.010998
CPU usage (%): 99.1734
Max. virtual memory (cumulated for all children) (KiB): 67448

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.06099
system time used= 0.010998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2786
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.004999 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node33 at 2009-04-25 05:09:00
IDJOB=1717548
IDBENCH=20418
IDSOLVER=551
FILE ID=node33/1717548-1240628939
PBS_JOBID= 9186362
Free space on /tmp= 66364 MiB

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

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

MD5SUM BENCH= 6197e38464facb30636a5a3ad5b2f0b5
RANDOM SEED=1320348674

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.212
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.212
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:        988808 kB
Buffers:         84948 kB
Cached:         878272 kB
SwapCached:          0 kB
Active:         153668 kB
Inactive:       823448 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        988808 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:           16688 kB
Writeback:           0 kB
Mapped:          23688 kB
Slab:            76056 kB
Committed_AS:   272756 kB
PageTables:       1388 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= 66364 MiB
End job on node33 at 2009-04-25 05:09:01