Bug 649292 – dev-tcltk/tcllib-1.16: fails 2-3 tests

• Status: RESOLVED OBSOLETE
• Product: Gentoo Linux

[Description Michał Górny 2018-03-01 22:48:51 UTC]

==== profiler-7.2-85 sortFunctions FAILED
==== Contents of test case:

    set c [interp create]
    interp alias $c parentSet {} set
    set result [$c eval {
	set auto_path [parentSet auto_path]
	package require profiler
	profiler::init
	proc ::foo {} {
	    set foobar 0
	}
	proc ::bar {} {
	    set foobar 1
	}
	foo; foo; bar;
	profiler::sortFunctions calls
    }]
    interp delete $c
    set result

---- Result was:
{::bar 1} {::foo 2}
---- Result should have been (exact matching):
{::tcl::clock::scan 0} {::tcl::clock::format 0} {::tcl::clock::add 0} {::bar 1} {::foo 2}
==== profiler-7.2-85 FAILED

==== uevent-10.3 watch events, watch after bind, glob FAILED
==== Contents of test case:

    set res {}
    set t1 [::uevent::bind TAGX E FOO]
    set t2 [::uevent::bind TAG  E FOO]
    set t3 [::uevent::bind TAGX EX FOO]
    set t4 [::uevent::bind TAG  EX FOO]
    set tw [::uevent::watch::event::add TAG* E* WATCHE]
    ::uevent::unbind $t1
    ::uevent::unbind $t2
    ::uevent::unbind $t3
    ::uevent::unbind $t4
    ::uevent::watch::event::remove $tw
    set res

---- Result was:
bound TAG EX bound TAGX EX bound TAG E bound TAGX E unbound TAGX E unbound TAG E unbound TAGX EX unbound TAG EX
---- Result should have been (exact matching):
bound TAGX E bound TAGX EX bound TAG E bound TAG EX unbound TAGX E unbound TAG E unbound TAGX EX unbound TAG EX
==== uevent-10.3 FAILED


I'm currently determining whether the failure is FreeBSD-specific or can be reproduced on regular amd64 system.

[Comment 1 Michał Górny 2018-03-01 22:49:27 UTC]

Created attachment 521794 [details]
dev-tcltk:tcllib-1.16:20180301-220239.log.xz

[Comment 2 Michał Górny 2018-03-01 22:49:42 UTC]

Created attachment 521796 [details]
e-info.txt

[Comment 3 Michał Górny 2018-03-02 08:13:28 UTC]

Actually, I can reproduce the same failures on my regular amd64 box, plus a third one:

==== doctools-msgcat-2.0 init, ok args FAILED
==== Contents of test case:

    doctools::msgcat::init idx

---- Result was:
0
---- Result should have been (exact matching):
1
==== doctools-msgcat-2.0 FAILED

[Comment 4 Tupone Alfredo 2019-01-31 11:42:03 UTC]

The 1.16 version is not more in the tree
The bug is not present in the 1.19 versio