convn test known failure dumps volumes of data into fntests.log

[Daniel J Sebald]

As noted in the package license thread, the known failure test

> > > > > processing 
> > > > > /usr/local/src/octave/octave-polygcd/build1/libinterp/corefcn/conv2.cc-tst
***** xtest
 assert (convn (a, b, "valid"), c(3:10,3:10,3:10));

!!!!! known failure

displays an outrageous amount of data to fntests.log.  The error that 
"assert" creates isn't so bad, but there is something about "shared 
variables" that is pretty voluminous.  Most of the tests are failing 
with something like:

(2,4,4,5,4)     16.848       16.848      Abs err 3.5527e-15 exceeds tol 0

Could the existing convn tests be commented out and replaced with 
something of lower dimensionality that still illustrates the problem?

Dan

PS: Just ran into pager problems.  Could it be that the pager is too 
full?  When running

test conv2.cc-tst

and paging down through the results with the "Page Down" key it 
eventually hits:

undecodable token: \001b(hex)[6~
undecodable token: \001b(hex)[6~
undecodable token: \001b(hex)[6~
undecodable token: \001b(hex)[6~
undecodable token: \001b(hex)[6~
undecodable token: \001b(hex)[6~

The same thing happens with the down arrow (but that takes a while to 
page through all the data).  Something similar also happens in the 
--no-gui version.