RE: !! Take note !! CVS frozen !! RE: [Tcllib-devel] Tcllib Relea se

[Techentin, R. W. <tec...@ma...>]

Thanks for the analysis, Andreas.

> > I downloaded the preview, unpacked, configured, and ran "make
> > test."  Everything passes on Fedora Core 3, ActiveTcl 8.4.6.  But
> > I got failures doing the same thing on HP-UX, WinXP/MingW/Msys,
> > and Red Hat Enterprise Linux (RHEL) 3.
> 
> I wish that you had done that when I posted the 'testenv', it 
> is for easy testing of a Tcllib checkout using Tcl 8.2 to 
> 8.5. Ok, water under bridge ...

My bad.  I was really concerned with the bugs that appeared with the units
package and Tcl 8.5.  I spent a lot of time trying to build Tcl HEAD, and
not much focusing on Tcllib.  :-(


> > ActiveTcl 8.4.6 was
> > installed everywhere.
> 
> What is the situation if you are using ActiveTcl 8.4.11 ?

I don't know.  Its getting about time to upgrade.  But the Sysadmins have to
be fed. :-)


> How about filing bugs against the modules and packages which 
> are in your opinion to chatty in the test output ?

OK.  I will do so.  I see unnecessary log messages from calendar, comm,
counter, docstrip, grammar_fa, htmlparse, log, math, ncgi, png, pop3, pop3d,
struct, and tie.

> Do we have commands in tcltest for our own log 
> output, which can then be controlled through its -verbose option ?

No, not really.  Tcltest's -verbose option controls when the test suite
prints messages.  The default is to print the body when a test fails, and
error information if there is an uncaught error.  You could also ask for a
message when tests are passed or skipped.  But there isn't an associated
general logging facility.



> > Modules with "Error: No test files remain ...
> 
> This is the message generated by tcltest when there are 
> either no .test files or they are empty, i.e. when there is 
> no testsuite.
> 
> > So I'm not testing these on unix, but they appeared to run tests
> > on WinXP.
> 
> How did you come to the conclusion that they have tests on WinXP ?

I didn't get "Error: No test files remain..."  My misinterpretation.


> > Many aes and blowfish tests failed with "integer value too large
> > to represent" on HP-UX and "integer value too large to represent
> > as non-long integer" on RHEL with tclsh8.3.  For example, I
> > include just one test, but there were 27 others.
> 
> This could be a problem with Tcl 8.3. Do the same error occur 
> with Tcl 8.4 ? Is your machine 64 bit ? 

These fail on HP-UX with ActiveTcl 8.4.6, and also on RHEL with its stock
tclsh8.3.  So it doesn't work on HP-UX.  Might be something to do with wide
ints.  Perhaps we need to ugrade. :-)



Bob
-- 
Bob Techentin                        tec...@ma... 
Mayo Foundation                                 (507) 538-5495 
200 First St. SW                            FAX (507) 284-9171
Rochester MN, 55901  USA            http://www.mayo.edu/sppdg/