|
From: Virden, L. W. <lv...@ca...> - 2008-08-25 16:11:33
|
Modules:
do-2.3
docidx-3.0
doctoc-3.0
doctools-3.0
fa-final-tcl-2.0
fa-next-tcl-1.0
fa-next-tcl-1.1
fa-next-tcl-1.9
fa-next-tcl-1.10
fa-start-tcl-2.0
fa-state-tcl-1.0
fa-state-tcl-1.1
fa-state-tcl-1.4
fa-state-tcl-1.6
fa-state-tcl-1.8
fa-symbol-tcl-1.0
fa-symbol-tcl-1.2
fa-symbol-tcl-1.5
fa-symbol-tcl-1.7
fa-symbol-tcl-1.9
me-cpucore-tok-tcl-1.0
jpeg-20.0
jpeg-20.1
ldap-18.0
logger-trace-1.1
math-1.1
math-2.1
math-3.1
math-4.1
math-5.1
math-6.1
math-6.2
math-7.1
math-7.2
math-8.1
math-8.2
linmin-2.1
linmin-4.1
report-6.0
report-15.0
report-16.0
report-17.0
report-18.0
report-19.0
report-20.0
report-21.0
report-22.0
report-23.0
report-24.0
htypemethod-1.6
creation-1.10
creation-1.14
hmethod-1.6
iinfo-1.2
tinfo-1.2
graph-tcl-tcl-walk-1.0
graph-tcl-tcl-arc-attr-1.0
graph-tcl-tcl-arc-insert-1.0
graph-tcl-tcl-arc-insert-1.1
graph-tcl-tcl-node-attr-1.0
graph-tcl-tcl-arc-set-1.0
graph-tcl-tcl-arc-set-1.1
graph-tcl-tcl-node-set-1.0
graph-tcl-tcl-node-set-1.1
graph-tcl-tcl-graph-set-1.0
matrix-11.0
matrix-11.1
matrix1-11.0
matrix1-11.1
set-tcl-1.0
tree-tcl-4.4.17
tree-tcl-6.0
tie-7.1
tie-8.0
--
<URL: http://wiki.tcl.tk/ >
Even if explicitly stated to the contrary, nothing in this posting
should be construed as representing my employer's opinions.
<URL: mailto:lv...@gm... > <URL: http://www.purl.org/NET/lvirden/
>
-----Original Message-----
From: Andreas Kupries [mailto:and...@ac...]
Sent: Monday, August 25, 2008 11:46 AM
To: Virden, Larry W.; tcl...@li...
Subject: RE: [Tcllib-devel] has anyone began testing tcllib cvs head and
tcl8.5.4?
>
> $ fgrep -c FAILED tcllib/unix/casrun.lwv
> 148
>
> Now, for each failure, there's two lines with FAILED in it. So 74 test
> cases failed.
> It appears there are quite a large number of errors being generated
> when I run the tcllib test suite against tcl 8.5.4 built on sparc
> solaris.
> With this many errors, I don't have time, and you probalby don't have
> the energy, to handle that many bug reports.
Can you reduce it down to the names of the modules in which we have the
failures ?
> Here's a sampling of what I see:
>
> ==== do-2.3 wrong no of arguments FAILED ==== Contents of test case:
>
> set res [catch do]
> if {[string match {no value given for parameter "body" to "do"*}
> $::errorInfo]
> } then {
> set ::errorInfo {wrong # args: should be "do body args"
> while executing
> "do"}
> }
> list $res $::errorInfo
>
> ---- Result was:
> 1 {wrong # args: should be "do body ?arg ...?"
> while executing
> "do"}
> ---- Result should have been (exact matching):
> 1 {wrong # args: should be "do body ..."
> while executing
> "do"}
> ==== do-2.3 FAILED
Snit ... And it seems that the recent drive for 'consistent error
messages'
(which started in the 8.5 series IIRC) has changed the details of the
error stack, causing many tests containing (partial) stack trac traces
to now fail.
We can likely fix this by "simply" updating the test cases. Maybe
changing to glob matching, to ignore the changing parts?
> This difference in error message appears to be the sort of thing many
> of the failures are.
Yes.
> Here's another type of error:
>
> ==== tree-tcl-4.4.17 error in walk FAILED
Also stacktrace
--
Andreas Kupries <and...@Ac...>
Developer @ http://www.ActiveState.com
Tel: +1 778-786-1122
|