Menu
▾
▴
tcl-core
|
From: Jan N. <jan...@gm...> - 2019-10-10 22:57:25
|
Op vr 11 okt. 2019 om 00:15 schreef Marc Culler:
>
> If no one objects I would like to merge the catalina_more_tests branch into core-8-6-branch and close it. The changes would be:
>
> UPDATE macosx/tkMacOSXColor.c
> UPDATE macosx/tkMacOSXNotify.c
> UPDATE tests/ttk/entry.test
>
> I am not sure why the last one was not merged earlier, but I see no problem with doing that.
Looks good to me! Great work! ttk/entry.test could indeed have
been merged earlier.
I just ran the "catalina_more_tests" build on Catalina:
Tests ended at Fri Oct 11 00:43:26 CEST 2019
all.tcl: Total 9627 Passed 8282 Skipped 1345 Failed 0
Sourced 92 Test Files.
Number of tests skipped for each constraint:
....
So, all looks good to me!
Thanks!
Jan Nijtmans
P.S: For completeness, I also ran "catalina_more_tests" on XQuartz:
Tests ended at Fri Oct 11 00:53:24 CEST 2019
all.tcl: Total 9619 Passed 8871 Skipped 703 Failed 45
Sourced 92 Test Files.
Files with failing tests: canvText.test clipboard.test entry.test
focus.test pack.test place.test scrollbar.test textDisp.test
unixEmbed.test unixFont.test unixWm.test winfo.test wm.test
Number of tests skipped for each constraint:
....
Tests running in: /Users/jan/workspace/tk8.7/unix
Temporary files stored in /Users/jan/workspace/tk8.7/unix
Test files sourced into current interpreter
Running tests that match: *
Skipping test files that match: l.*.test
Only running test files that match: *.test
Tests began at Fri Oct 11 00:46:37 CEST 2019
bell.test
Bell should ring now ...
bgerror.test
bind.test
bitmap.test
border.test
busy.test
button.test
canvImg.test
canvMoveto.test
canvPs.test
canvRect.test
canvText.test
==== canvText-20.1 angled text bounding box FAILED
==== Contents of test case:
.c create text 2 2 -tag t -anchor center -text 0 -font {Helvetica 24}
set bb0 [.c bbox t]
.c itemconf t -angle 90
set bb1 [.c bbox t]
.c itemconf t -angle 180
set bb2 [.c bbox t]
.c itemconf t -angle 270
set bb3 [.c bbox t]
list [expr {$bb0 eq $bb2 ? "ok" : "$bb0,$bb2"}] [expr {$bb1 eq
$bb3 ? "ok" : "$bb1,$bb3"}] [expr {$bb0 eq [transpose $bb1] ? "ok" :
"$bb0,$bb1"}]
---- Result was:
{-7 -15 12 19,-8 -15 11 19} {-15 -8 19 11,-15 -7 19 12} {-7 -15 12
19,-15 -8 19 11}
---- Result should have been (exact matching):
ok ok ok
==== canvText-20.1 FAILED
canvWind.test
canvas.test
choosedir.test
clipboard.test
==== clipboard-6.2 Tk_ClipboardAppend procedure FAILED
==== Contents of test case:
setupbg
clipboard append -f INTEGER -t TEST "16"
set result [dobg {clipboard get TEST}]
return $result
---- Result was:
CLIPBOARD selection doesn't exist or form "TEST" not defined
---- Result should have been (exact matching):
0x10
==== clipboard-6.2 FAILED
clrpick.test
cmds.test
color.test
config.test
cursor.test
dialog.test
embed.test
entry.test
==== entry-5.8 ConfigureEntry procedure FAILED
==== Contents of test case:
.e configure -width 0 -font {Helvetica -12}
.e insert end "0123"
update
.e configure -font {Helvetica -24}
update
winfo geom .e
---- Result was:
62x37+5+0
---- Result should have been (exact matching):
62x37+0+0
==== entry-5.8 FAILED
event.test
filebox.test
focus.test
==== focus-2.6 TkFocusFilterEvent procedure, FocusIn events FAILED
==== Contents of test case:
focus .t.b1
focus .
update
event gen [testwrapper .t] <FocusIn> -detail NotifyAncestor
set focusInfo {}
set x [focus]
event gen . <KeyPress-x>
list $x $focusInfo
---- Result was:
. {press . x}
---- Result should have been (exact matching):
.t.b1 {press .t.b1 x}
==== focus-2.6 FAILED
==== focus-2.7 TkFocusFilterEvent procedure, FocusOut events FAILED
==== Contents of test case:
set result {}
foreach detail {NotifyAncestor NotifyInferior NotifyNonlinear
NotifyNonlinearVirtual NotifyPointer NotifyPointerRoot
NotifyVirtual} {
focus -force .t.b1
event gen [testwrapper .t] <FocusOut> -detail $detail
update
lappend result [focus]
}
return $result
---- Result was:
.t.b1 .t.b1 .t.b1 .t.b1 .t.b1 .t.b1 .t.b1
---- Result should have been (exact matching):
{} .t.b1 {} {} .t.b1 .t.b1 {}
==== focus-2.7 FAILED
==== focus-2.9 TkFocusFilterEvent procedure, FocusOut events FAILED
==== Contents of test case:
focus .t.b1
event gen [testwrapper .] <FocusOut> -detail NotifyAncestor
focus
---- Result was:
.t.b1
---- Result should have been (exact matching):
==== focus-2.9 FAILED
==== focus-5.1 ChangeXFocus procedure, don't take focus unless have it FAILED
==== Contents of test case:
setupbg
focusSetup
focus -force .t
update
set result [focus]
send [dobg {tk appname}] {focus -force .; update}
lappend result [focus]
focus .t.b2
update
lappend result [focus]
---- Result was:
.t .t {}
---- Result should have been (exact matching):
.t {} {}
==== focus-5.1 FAILED
focusTcl.test
font.test
fontchooser.test
frame.test
geometry.test
get.test
grab.test
grid.test
image.test
imgBmap.test
imgPNG.test
imgPPM.test
imgPhoto.test
listbox.test
main.test
menu.test
menuDraw.test
menubut.test
message.test
msgbox.test
obj.test
oldpack.test
option.test
pack.test
==== pack-18.2 unmap slaves when master unmapped FAILED
==== Contents of test case:
# adjust the position of .pack before test to avoid a screen switch
# that occurs with window managers that have desktops four times as big
# as the screen (screen switch causes scale and other tests to fail).
wm geometry .pack +100+100
frame .pack.a -relief raised -bd 2
frame .pack.b -width 70 -height 30 -relief sunken -bd 2
pack .pack.a
pack .pack.b -in .pack.a
update
set result [winfo ismapped .pack.b]
wm iconify .pack
update
lappend result [winfo ismapped .pack.b]
.pack.b configure -width 100 -height 30
update
lappend result [winfo width .pack.b ] [winfo height .pack.b]
[winfo ismapped .pack.b]
wm deiconify .pack
update
lappend result [winfo ismapped .pack.b]
---- Result was:
1 1 100 30 1 1
---- Result should have been (exact matching):
1 0 100 30 0 1
==== pack-18.2 FAILED
packgrid.test
panedwindow.test
place.test
==== place-8.2 MasterStructureProc, mapping and unmapping slaves FAILED
==== Contents of test case:
place .t.f -x 0 -y 0 -width 200 -height 100
place .t.f2 -in .t.f -relx 1.0 -rely 1.0 -anchor sw -width 50 -height 20
update
set result [winfo ismapped .t.f2]
wm iconify .t
update
lappend result [winfo ismapped .t.f2]
place .t.f2 -x 40 -y 30 -relx 0 -rely 0 -anchor nw
update
lappend result [winfo x .t.f2] [winfo y .t.f2] [winfo ismapped .t.f2]
wm deiconify .t
update
lappend result [winfo ismapped .t.f2]
---- Result was:
1 1 42 32 1 1
---- Result should have been (exact matching):
1 0 42 32 0 1
==== place-8.2 FAILED
raise.test
safe.test
safePrimarySelection.test
scale.test
scrollbar.test
==== scrollbar-3.36 ScrollbarWidgetCmd procedure, "fraction" option FAILED
==== Contents of test case:
format {%.6g} [.s fraction 4 179]
---- Result was:
0.976048
---- Result should have been (exact matching):
1
==== scrollbar-3.36 FAILED
==== scrollbar-3.38 ScrollbarWidgetCmd procedure, "fraction" option FAILED
==== Contents of test case:
format {%.6g} [.s fraction 4 178]
---- Result was:
0.97006
---- Result should have been (exact matching):
0.993711
==== scrollbar-3.38 FAILED
==== scrollbar-6.12.1 ScrollbarPosition procedure FAILED
==== Contents of test case:
.s identify 8 19
---- Result was:
trough1
---- Result should have been (exact matching):
arrow1
==== scrollbar-6.12.1 FAILED
==== scrollbar-6.29.1 ScrollbarPosition procedure FAILED
==== Contents of test case:
.s identify 8 180
---- Result was:
trough2
---- Result should have been (exact matching):
arrow2
==== scrollbar-6.29.1 FAILED
==== scrollbar-6.35 ScrollbarPosition procedure FAILED
==== Contents of test case:
.s identify 18 100
---- Result was:
---- Result should have been (exact matching):
trough2
==== scrollbar-6.35 FAILED
==== scrollbar-6.44 ScrollbarPosition procedure FAILED
==== Contents of test case:
.t.s identify 100 18
---- Result was:
---- Result should have been (exact matching):
trough2
==== scrollbar-6.44 FAILED
select.test
send.test
spinbox.test
text.test
textBTree.test
textDisp.test
==== textDisp-4.8 UpdateDisplayInfo, filling in extra vertical space FAILED
==== Contents of test case:
.t delete 1.0 end
.t insert end "1\n2\n3\n4\n5\n6\n7\n8\n9\n10\n11\n12\n13\n14\n15\n16\n17"
.t yview 16.0
updateText
.t delete 5.0 14.0
updateText
set x [list [.t index @0,0] $tk_textRelayout $tk_textRedraw]
---- Result was:
1.0 {5.0 4.0 3.0 2.0 1.0} {1.0 2.0 3.0 4.0 5.0 8.0 eof}
---- Result should have been (exact matching):
1.0 {5.0 4.0 3.0 2.0 1.0} {1.0 2.0 3.0 4.0 5.0 eof}
==== textDisp-4.8 FAILED
==== textDisp-4.14 UpdateDisplayInfo, special handling for top/bottom
lines FAILED
==== Contents of test case:
.t tag remove x 1.0 end
.t yview 1.0
updateText
.t yview scroll 3 units
updateText
list $tk_textRelayout $tk_textRedraw
---- Result was:
{11.0 12.0 13.0} {10.0 11.0 12.0 13.0}
---- Result should have been (exact matching):
{11.0 12.0 13.0} {11.0 12.0 13.0}
==== textDisp-4.14 FAILED
==== textDisp-6.1 scrolling in DisplayText, scroll up FAILED
==== Contents of test case:
.t delete 1.0 end
.t insert 1.0 "Line 1"
foreach i {2 3 4 5 6 7 8 9 10 11 12 13 14 15} {
.t insert end "\nLine $i"
}
updateText
.t delete 2.0 3.0
updateText
list $tk_textRelayout $tk_textRedraw
---- Result was:
{2.0 10.0} {2.0 9.0 10.0}
---- Result should have been (exact matching):
{2.0 10.0} {2.0 10.0}
==== textDisp-6.1 FAILED
==== textDisp-8.7 TkTextChanged FAILED
==== Contents of test case:
.t delete 1.0 end
.t insert 1.0 "Line 1 is so long that it wraps around, two times"
foreach i {2 3 4 5 6 7 8 9 10 11 12 13 14 15} {
.t insert end "\nLine $i"
}
updateText
.t delete 1.2 1.end
updateText
list $tk_textRelayout $tk_textRedraw
---- Result was:
{1.0 9.0 10.0} {1.0 8.0 9.0 10.0}
---- Result should have been (exact matching):
{1.0 9.0 10.0} {1.0 9.0 10.0}
==== textDisp-8.7 FAILED
==== textDisp-8.9 TkTextChanged FAILED
==== Contents of test case:
.t delete 1.0 end
.t insert 1.0 "Line 1 is so long that it wraps around, two times"
foreach i {2 3 4 5 6 7 8 9 10 11 12 13 14 15} {
.t insert end "\nLine $i"
}
updateText
.t delete 2.0 3.0
updateText
list $tk_textRelayout $tk_textRedraw
---- Result was:
{2.0 8.0} {2.0 7.0 8.0}
---- Result should have been (exact matching):
{2.0 8.0} {2.0 8.0}
==== textDisp-8.9 FAILED
==== textDisp-9.5 TkTextRedrawTag FAILED
==== Contents of test case:
.t configure -wrap char
.t delete 1.0 end
.t insert 1.0 "Line 1\nLine 2 is long enough to wrap around\nLine 3\nLine 4"
updateText
.t tag add big 2.2 2.end
updateText
.t tag remove big 1.0 end
updateText
list $tk_textRelayout $tk_textRedraw
---- Result was:
{2.0 2.20} {2.0 2.20 4.0 eof}
---- Result should have been (exact matching):
{2.0 2.20} {2.0 2.20 eof}
==== textDisp-9.5 FAILED
==== textDisp-11.2 TkTextSetYView FAILED
==== Contents of test case:
.t yview 30.0
updateText
.t yview 32.0
updateText
list [.t index @0,0] $tk_textRedraw
---- Result was:
32.0 {39.0 40.0 41.0}
---- Result should have been (exact matching):
32.0 {40.0 41.0}
==== textDisp-11.2 FAILED
==== textDisp-11.4 TkTextSetYView FAILED
==== Contents of test case:
.t yview 30.0
updateText
.t yview 31.4
updateText
list [.t index @0,0] $tk_textRedraw
---- Result was:
31.0 {39.0 40.0}
---- Result should have been (exact matching):
31.0 40.0
==== textDisp-11.4 FAILED
==== textDisp-11.8 TkTextSetYView FAILED
==== Contents of test case:
.t yview 30.0
updateText
set tk_textRedraw {}
.t yview -pickplace 41.0
updateText
list [.t index @0,0] $tk_textRedraw
---- Result was:
32.0 {39.0 40.0 41.0}
---- Result should have been (exact matching):
32.0 {40.0 41.0}
==== textDisp-11.8 FAILED
==== textDisp-11.9 TkTextSetYView FAILED
==== Contents of test case:
.t yview 30.0
updateText
set tk_textRedraw {}
.t yview -pickplace 43.0
updateText
list [.t index @0,0] $tk_textRedraw
---- Result was:
38.0 {39.0 40.0 41.0 42.0 43.0 44.0 45.0 46.0 47.0 48.0}
---- Result should have been (exact matching):
38.0 {40.0 41.0 42.0 43.0 44.0 45.0 46.0 47.0 48.0}
==== textDisp-11.9 FAILED
==== textDisp-11.12 TkTextSetYView, wrapped line is off-screen FAILED
==== Contents of test case:
.t insert 10.0 "Long line with enough text to wrap\n"
.t yview 1.0
updateText
set tk_textRedraw {}
.t see 10.30
updateText
list [.t index @0,0] $tk_textRedraw
---- Result was:
2.0 {10.0 10.20}
---- Result should have been (exact matching):
2.0 10.20
==== textDisp-11.12 FAILED
==== textDisp-24.25 TkTextCharLayoutProc, justification and tabs FAILED
==== Contents of test case:
.tt insert end \t9\n\t99\n\t999
updateText
list [.tt bbox 1.1] [.tt bbox 2.2] [.tt bbox 3.3]
---- Result was:
{38 5 7 13} {38 18 7 13} {38 31 7 13}
---- Result should have been (exact matching):
{38 5 7 13} {38 20 7 13} {38 35 7 13}
==== textDisp-24.25 FAILED
textImage.test
textIndex.test
textMark.test
textTag.test
textWind.test
tk.test
unixButton.test
unixEmbed.test
==== unixEmbed-7.1a TkpRedirectKeyEvent procedure, forward keystroke FAILED
==== Contents of test case:
deleteWindows
frame .f1 -container 1 -width 200 -height 50
pack .f1
slave alias w1 winfo id .f1
slave eval {
destroy [winfo child .]
toplevel .t1 -use [w1]
}
focus -force .
bind . <KeyPress> {lappend x {key %A %E}}
set x {}
set y [slave eval {
update
bind .t1 <KeyPress> {lappend y {key %A}}
set y {}
event generate .t1 <KeyPress> -keysym a
set y
}]
update
list $x $y
---- Result was:
{} {}
---- Result should have been (exact matching):
{{key a 1}} {}
==== unixEmbed-7.1a FAILED
==== unixEmbed-8.1 TkpClaimFocus procedure FAILED
==== Contents of test case:
frame .f1 -container 1 -width 200 -height 50
frame .f2 -width 200 -height 50
pack .f1 .f2
dobg "set w1 [winfo id .f1]"
dobg {
eval destroy [winfo child .]
toplevel .t1 -use $w1 -highlightthickness 2 -bd 2 -relief sunken
}
focus -force .f2
update
list [dobg {
focus .t1
set x [list [focus]]
update
after 500
update
lappend x [focus]
}] [focus]
---- Result was:
{.t1 .t1} .f2
---- Result should have been (exact matching):
{{} .t1} .f1
==== unixEmbed-8.1 FAILED
unixFont.test
==== unixfont-8.4 AllocFont procedure: classify characters FAILED
==== Contents of test case:
set x 0
incr x [font measure $courier "\u4000"] ;# 6
incr x [font measure $courier "\002"] ;# 4
incr x [font measure $courier "\012"] ;# 2
incr x [font measure $courier "\101"] ;# 1
set x
---- Result was:
21
---- Result should have been (exact matching):
78
==== unixfont-8.4 FAILED
==== unixfont-8.6 AllocFont procedure: setup widths of special chars FAILED
==== Contents of test case:
set x 0
incr x [font measure $courier "\001"] ;# 4
incr x [font measure $courier "\002"] ;# 4
incr x [font measure $courier "\012"] ;# 2
set x
---- Result was:
15
---- Result should have been (exact matching):
60
==== unixfont-8.6 FAILED
==== unixfont-9.1 GetControlCharSubst procedure: 2 chars subst FAILED
==== Contents of test case:
.b.c dchars $t 0 end
.b.c insert $t 0 "0\a0"
set x {}
lappend x [.b.c index $t @[expr $ax*0],0]
lappend x [.b.c index $t @[expr $ax*1],0]
lappend x [.b.c index $t @[expr $ax*2],0]
lappend x [.b.c index $t @[expr $ax*3],0]
---- Result was:
0 1 2 3
---- Result should have been (exact matching):
0 1 1 2
==== unixfont-9.1 FAILED
==== unixfont-9.2 GetControlCharSubst procedure: 4 chars subst FAILED
==== Contents of test case:
.b.c dchars $t 0 end
.b.c insert $t 0 "0\0010"
set x {}
lappend x [.b.c index $t @[expr $ax*0],0]
lappend x [.b.c index $t @[expr $ax*1],0]
lappend x [.b.c index $t @[expr $ax*2],0]
lappend x [.b.c index $t @[expr $ax*3],0]
lappend x [.b.c index $t @[expr $ax*4],0]
lappend x [.b.c index $t @[expr $ax*5],0]
---- Result was:
0 1 2 3 3 3
---- Result should have been (exact matching):
0 1 1 1 1 2
==== unixfont-9.2 FAILED
unixMenu.test
unixSelect.test
unixWm.test
==== unixWm-9.3 TkWmMapWindow procedure, iconic windows FAILED
==== Contents of test case:
destroy .t
toplevel .t -width 100 -height 300 -bg blue
wm geom .t +0+0
wm iconify .t
sleep 500
winfo ismapped .t
---- Result was:
1
---- Result should have been (exact matching):
0
==== unixWm-9.3 FAILED
==== unixWm-44.7 UpdateGeometryInfo procedure, computing position FAILED
==== Contents of test case:
tkwait visibility .t
wm overrideredirect .t 1
update
wm geometry .t +5-10
update
list [winfo x .t] [winfo y .t]
---- Result was:
5 1327
---- Result should have been (exact matching):
5 1348
==== unixWm-44.7 FAILED
==== unixWm-44.8 UpdateGeometryInfo procedure, computing position FAILED
==== Contents of test case:
tkwait visibility .t
wm overrideredirect .t 1
update
wm geometry .t -30+$Y2
update
list [winfo x .t] [winfo y .t]
---- Result was:
2450 3
---- Result should have been (exact matching):
2450 2
==== unixWm-44.8 FAILED
==== unixWm-45.2 UpdateSizeHints procedure FAILED
==== Contents of test case:
destroy .t
toplevel .t -width 80 -height 60
wm minsize .t 30 40
wm maxsize .t 200 500
wm geometry .t +0+0
tkwait visibility .t
set property [testprop [testwrapper .t] WM_NORMAL_HINTS]
list [expr [lindex $property 5]] [expr [lindex $property 6]]
[expr [lindex $property 7]] [expr [lindex $property 8]] [expr [lindex
$property 9]] [expr [lindex $property 10]]
---- Result was:
30 40 200 500 0 0
---- Result should have been (exact matching):
30 40 200 500 1 1
==== unixWm-45.2 FAILED
==== unixWm-45.4 UpdateSizeHints procedure, not resizable with menu FAILED
==== Contents of test case:
destroy .t
toplevel .t -width 80 -height 60
frame .t.menu -height 23 -width 50
testmenubar window .t .t.menu
wm resizable .t 0 0
wm geometry .t +0+0
tkwait visibility .t
set property [testprop [testwrapper .t] WM_NORMAL_HINTS]
list [winfo height .t] [expr [lindex $property 5]] [expr [lindex
$property 6]] [expr [lindex $property 7]] [expr [lindex $property 8]]
[expr [lindex $property 9]] [expr [lindex $property 10]]
---- Result was:
60 80 83 80 83 0 0
---- Result should have been (exact matching):
60 80 83 80 83 1 1
==== unixWm-45.4 FAILED
==== unixWm-50.1 Tk_CoordsToWindow procedure, finding a toplevel,
x-coords, title bar FAILED
==== Contents of test case:
update
toplevel .t -width 300 -height 400 -bg green
wm geom .t +100+100
tkwait visibility .t
toplevel .t2 -width 100 -height 200 -bg red
wm geom .t2 +200+200
tkwait visibility .t2
raise .t2
update
set x [winfo rootx .t]
set y [winfo rooty .t]
list [winfo containing [expr $x - 30] [expr $y + 250]] [winfo
containing [expr $x - 1] [expr $y + 250]] [winfo containing $x
[expr $y + 250]] [winfo containing [expr $x + 99] [expr $y +
250]] [winfo containing [expr $x + 100] [expr $y + 250]] [winfo
containing [expr $x + 150] [expr $y + 90]] [winfo containing [expr $x
+ 199] [expr $y + 250]] [winfo containing [expr $x + 200] [expr $y +
250]] [winfo containing [expr $x + 220] [expr $y + 250]]
---- Result was:
{} {} .t .t .t2 {} .t2 .t .t
---- Result should have been (exact matching):
{} {} .t {} .t2 {} .t2 {} .t
==== unixWm-50.1 FAILED
==== unixWm-51.7 TkWmRestackToplevel procedure, other window isn't mapped FAILED
==== Contents of test case:
foreach w {.t .t2 .t3} {
destroy $w
update
toplevel $w -width 200 -height 200 -bg green
wm geometry $w +0+0
}
raise .t .t2
sleep 2000
update
set result [list [winfo containing 100 100]]
lower .t3
sleep 2000
lappend result [winfo containing 100 100]
---- Result was:
.t3 .t2
---- Result should have been (exact matching):
.t3 .t
==== unixWm-51.7 FAILED
util.test
visual.test
visual_bb.test
winButton.test
winClipboard.test
winDialog.test
winFont.test
winMenu.test
winMsgbox.test
winSend.test
winWm.test
window.test
winfo.test
==== winfo-9.7 "winfo viewable" command FAILED
==== Contents of test case:
frame .f1 -width 100 -height 100 -relief raised -bd 2
place .f1 -x 0 -y 0
frame .f1.f2 -width 50 -height 50 -relief raised -bd 2
place .f1.f2 -x 0 -y 0
update
wm iconify .
list [winfo viewable .f1] [winfo viewable .f1.f2]
---- Result was:
1 1
---- Result should have been (exact matching):
0 0
==== winfo-9.7 FAILED
wm.test
==== wm-stackorder-5.2 A normal toplevel can't be raised above an
overrideredirect toplevel on unix FAILED
==== Contents of test case:
toplevel .t
tkwait visibility .t
wm overrideredirect .t 1
raise .
update
raiseDelay
wm stackorder . isabove .t
---- Result was:
1
---- Result should have been (exact matching):
0
==== wm-stackorder-5.2 FAILED
==== wm-stackorder-5.3 An overrideredirect window can be explicitly
lowered FAILED
==== Contents of test case:
toplevel .t
tkwait visibility .t
wm overrideredirect .t 1
lower .t
update
raiseDelay
wm stackorder .t isbelow .
---- Result was:
0
---- Result should have been (exact matching):
1
==== wm-stackorder-5.3 FAILED
==== wm-transient-4.1 transient toplevel is withdrawn
when mapped if master is iconic FAILED
==== Contents of test case:
toplevel .master
wm iconify .master
update
toplevel .subject
wm transient .subject .master
update
list [wm state .subject] [winfo ismapped .subject]
---- Result was:
normal 1
---- Result should have been (exact matching):
withdrawn 0
==== wm-transient-4.1 FAILED
==== wm-transient-8.1 transient to withdrawn window, Bug 1163496 FAILED
==== Contents of test case:
# Verifies that transients stay on top of their masters, even if they were
# made transients when those masters were withdrawn.
toplevel .t1; wm withdraw .t1; update
toplevel .t2; wm transient .t2 .t1; update
lappend result [winfo ismapped .t1] [winfo ismapped .t2]
wm deiconify .t1; update
lappend result [winfo ismapped .t1] [winfo ismapped .t2]
raise .t1; update
lappend result [lsearch -all -inline -glob [wm stackorder .] ".t?"]
---- Result was:
0 0 1 1 {.t2 .t1}
---- Result should have been (exact matching):
0 0 1 1 {.t1 .t2}
==== wm-transient-8.1 FAILED
xmfbox.test
|
|
From: Francois V. <fvo...@fr...> - 2019-10-11 20:37:11
|
Le 06/10/2019 à 11:59, Harald Oehlmann a écrit :
> Am 05.10.2019 um 15:58 schrieb Francois Vogel:
>>> ==== bind-34.2 -warp works relatively to the screen FAILED
>>> ==== Contents of test case:
>>>
>>> # Contrary to bind-32.2, we're directly checking screen coordinates
>>> event generate {} <Motion> -x 20 -y 20 -warp 1
>>> update idletasks ; # DoWarp is an idle callback
>>> set res [winfo pointerxy .]
>>> event generate {} <Motion> -x 200 -y 200 -warp 1
>>> update idletasks ; # DoWarp is an idle callback
>>> lappend res {*}[winfo pointerxy .]
>>>
>>> ---- Result was:
>>> 20 19 200 200
>>> ---- Result should have been (exact matching):
>>> 20 20 200 200
>>> ==== bind-34.2 FAILED
>> So the pointer coordinates are erroneously (20,19) when warping to
>> (20,20), but they are correctly (200,200), when warping to (200,200)?
>> There is a difference of 1 unit, in y only, but not always. How come...?
>> That's strange. I don't reproduce this failure on my Vista system but I
>> will think about this.
Harald could you please try this again?
We now have a fix I think. It was for bind-34.1 that failed on Jan's
side, but that fix should also fix your failure with bind-34.2.
For this testing please use the tip of core-8-6-branch (at the time of
this writing the fix is not yet in the rc branch).
Thanks,
Francois
> I can only say, that I did not move the mouse while testing. But the tcl
> tests were running in parallel.
>
> Thank you,
> Harald
|
|
From: Harald O. <har...@el...> - 2019-10-12 08:20:55
|
Dear Francois,
Am 11.10.2019 um 22:36 schrieb Francois Vogel:
> Le 06/10/2019 à 11:59, Harald Oehlmann a écrit :
>> Am 05.10.2019 um 15:58 schrieb Francois Vogel:
>>>> ==== bind-34.2 -warp works relatively to the screen FAILED
>>>> ==== Contents of test case:
>>>>
>>>> # Contrary to bind-32.2, we're directly checking screen
>>>> coordinates
>>>> event generate {} <Motion> -x 20 -y 20 -warp 1
>>>> update idletasks ; # DoWarp is an idle callback
>>>> set res [winfo pointerxy .]
>>>> event generate {} <Motion> -x 200 -y 200 -warp 1
>>>> update idletasks ; # DoWarp is an idle callback
>>>> lappend res {*}[winfo pointerxy .]
>>>>
>>>> ---- Result was:
>>>> 20 19 200 200
>>>> ---- Result should have been (exact matching):
>>>> 20 20 200 200
>>>> ==== bind-34.2 FAILED
>>> So the pointer coordinates are erroneously (20,19) when warping to
>>> (20,20), but they are correctly (200,200), when warping to (200,200)?
>>> There is a difference of 1 unit, in y only, but not always. How come...?
>>> That's strange. I don't reproduce this failure on my Vista system but I
>>> will think about this.
>
> Harald could you please try this again?
>
> We now have a fix I think. It was for bind-34.1 that failed on Jan's
> side, but that fix should also fix your failure with bind-34.2.
> For this testing please use the tip of core-8-6-branch (at the time of
> this writing the fix is not yet in the rc branch).
thank you, Francois, for caring. This is highly appreciated.
Checkout is 440d0d87.
I tested it against 8.6.6rc0
The result for bind-32.2 is now:
==== bind-34.2 -warp works relatively to the screen FAILED
==== Contents of test case:
# Contrary to bind-34.1, we're directly checking screen coordinates
event generate {} <Motion> -x 20 -y 20 -warp 1
update idletasks ; # DoWarp is an idle callback
set res [winfo pointerxy .]
event generate {} <Motion> -x 200 -y 200 -warp 1
update idletasks ; # DoWarp is an idle callback
lappend res {*}[winfo pointerxy .]
---- Result was:
628 651 200 200
---- Result should have been (exact matching):
20 20 200 200
We can not speak any more about an rounding issue...
There is no other difference in tests compared to my last test.
Sorry for this results,
Harald
|
|
From: Francois V. <fvo...@fr...> - 2019-10-12 12:20:16
|
Le 12/10/2019 à 10:07, Harald Oehlmann a écrit :
> Checkout is 440d0d87.
> I tested it against 8.6.6rc0
>
> The result for bind-32.2 is now:
>
> ==== bind-34.2 -warp works relatively to the screen FAILED
> ==== Contents of test case:
>
> # Contrary to bind-34.1, we're directly checking screen coordinates
> event generate {} <Motion> -x 20 -y 20 -warp 1
> update idletasks ; # DoWarp is an idle callback
> set res [winfo pointerxy .]
> event generate {} <Motion> -x 200 -y 200 -warp 1
> update idletasks ; # DoWarp is an idle callback
> lappend res {*}[winfo pointerxy .]
>
> ---- Result was:
> 628 651 200 200
> ---- Result should have been (exact matching):
> 20 20 200 200
This results indicates that the idle callback 'DoWarp' is not executed
at the time the test expects it to be.
The command
event generate {} <Motion> -x 20 -y 20 -warp 1
schedules an idle callback 'DoWarp'.
We want this callback to be serviced before requesting the pointer
position through
set res [winfo pointerxy .]
and that's why I'm calling 'update idletasks' in between these two
statements.
If I remove this 'update idletasks', then I reproduce the behavior
you're seeing, this is normal and expected.
But it shouldn't happen with the 'update idletasks'.
The test works on my system and I simply have no idea why it doesn't on
yours.
Can you start debugging this? It's hard for me to guess since I don't
reproduce.
The first thing to check is that in wish the following command:
event generate {} <Motion> -x 20 -y 20 -warp 1
moves the pointer at the correct position (20,20) in screen coordinates.
I'm sure it does so this should be a timing/event issue specific to the
test. Then, look at how the test can be improved to make it more robust
(against... what exactly...?)
Thanks,
Francois
|
|
From: Francois V. <fvo...@fr...> - 2019-10-12 12:41:43
|
Le 12/10/2019 à 14:19, Francois Vogel a écrit :
> Can you start debugging this? It's hard for me to guess since I don't
> reproduce.
>
> The first thing to check is that in wish the following command:
> event generate {} <Motion> -x 20 -y 20 -warp 1
> moves the pointer at the correct position (20,20) in screen coordinates.
> I'm sure it does so this should be a timing/event issue specific to
> the test. Then, look at how the test can be improved to make it more
> robust (against... what exactly...?)
A possibility could be that the first idle 'Dowarp' not being scheduled
because the '.' window is not mapped (but why would it work then the
second time...) Anyway:
Can you do the following tests and report results:
Add "puts [winfo ismapped .]" in bind-34.2 between lines 637 and 638
just at the beginning of the -body part of the test, run the test and
provide output result.
Really hard guessing, thanks for your help.
F.
|
|
From: Harald O. <har...@el...> - 2019-10-12 13:55:44
|
Am 12.10.2019 um 14:40 schrieb Francois Vogel:
> Le 12/10/2019 à 14:19, Francois Vogel a écrit :
>> Can you start debugging this? It's hard for me to guess since I don't
>> reproduce.
>>
>> The first thing to check is that in wish the following command:
>> event generate {} <Motion> -x 20 -y 20 -warp 1
>> moves the pointer at the correct position (20,20) in screen coordinates.
>> I'm sure it does so this should be a timing/event issue specific to
>> the test. Then, look at how the test can be improved to make it more
>> robust (against... what exactly...?)
>
> A possibility could be that the first idle 'Dowarp' not being scheduled
> because the '.' window is not mapped (but why would it work then the
> second time...) Anyway:
>
> Can you do the following tests and report results:
> Add "puts [winfo ismapped .]" in bind-34.2 between lines 637 and 638
> just at the beginning of the -body part of the test, run the test and
> provide output result.
>
> Really hard guessing, thanks for your help.
> F.
Dear Francois,
it prints "1" independent if it fails or passes.
I will fly to Japan soon for a business trip and will be back in the
office the 31th of October.
Thank you,
Harald
|
|
From: Harald O. <har...@el...> - 2019-10-12 13:56:14
|
Am 12.10.2019 um 14:19 schrieb Francois Vogel:
>
> Le 12/10/2019 à 10:07, Harald Oehlmann a écrit :
>> Checkout is 440d0d87.
>> I tested it against 8.6.6rc0
>>
>> The result for bind-32.2 is now:
>>
>> ==== bind-34.2 -warp works relatively to the screen FAILED
>> ==== Contents of test case:
>>
>> # Contrary to bind-34.1, we're directly checking screen coordinates
>> event generate {} <Motion> -x 20 -y 20 -warp 1
>> update idletasks ; # DoWarp is an idle callback
>> set res [winfo pointerxy .]
>> event generate {} <Motion> -x 200 -y 200 -warp 1
>> update idletasks ; # DoWarp is an idle callback
>> lappend res {*}[winfo pointerxy .]
>>
>> ---- Result was:
>> 628 651 200 200
>> ---- Result should have been (exact matching):
>> 20 20 200 200
>
> This results indicates that the idle callback 'DoWarp' is not executed
> at the time the test expects it to be.
>
> The command
> event generate {} <Motion> -x 20 -y 20 -warp 1
> schedules an idle callback 'DoWarp'.
>
> We want this callback to be serviced before requesting the pointer
> position through
> set res [winfo pointerxy .]
> and that's why I'm calling 'update idletasks' in between these two
> statements.
>
> If I remove this 'update idletasks', then I reproduce the behavior
> you're seeing, this is normal and expected.
>
> But it shouldn't happen with the 'update idletasks'.
> The test works on my system and I simply have no idea why it doesn't on
> yours.
>
> Can you start debugging this? It's hard for me to guess since I don't
> reproduce.
>
> The first thing to check is that in wish the following command:
> event generate {} <Motion> -x 20 -y 20 -warp 1
> moves the pointer at the correct position (20,20) in screen coordinates.
> I'm sure it does so this should be a timing/event issue specific to the
> test. Then, look at how the test can be improved to make it more robust
> (against... what exactly...?)
>
> Thanks,
> Francois
>
I have tried it manually, copy the test into wish: works always
I have tried it multiple times:
nmake -f Makefile.vc test TESTFLAGS="-file bind.test -match bind-34.2
-verbose bte"
Result: 5 ok, 2 failures. So, roughly 1 of 3 fail.
THank you,
Harald
|
|
From: Francois V. <fvo...@fr...> - 2019-10-27 14:32:32
|
Le 12/10/2019 à 15:55, Harald Oehlmann a écrit :
> Am 12.10.2019 um 14:19 schrieb Francois Vogel:
>> Le 12/10/2019 à 10:07, Harald Oehlmann a écrit :
>>> Checkout is 440d0d87.
>>> I tested it against 8.6.6rc0
>>>
>>> The result for bind-32.2 is now:
>>>
>>> ==== bind-34.2 -warp works relatively to the screen FAILED
>>> ==== Contents of test case:
>>>
>>> # Contrary to bind-34.1, we're directly checking screen coordinates
>>> event generate {} <Motion> -x 20 -y 20 -warp 1
>>> update idletasks ; # DoWarp is an idle callback
>>> set res [winfo pointerxy .]
>>> event generate {} <Motion> -x 200 -y 200 -warp 1
>>> update idletasks ; # DoWarp is an idle callback
>>> lappend res {*}[winfo pointerxy .]
>>>
>>> ---- Result was:
>>> 628 651 200 200
>>> ---- Result should have been (exact matching):
>>> 20 20 200 200
>> This results indicates that the idle callback 'DoWarp' is not executed
>> at the time the test expects it to be.
>>
>> The command
>> event generate {} <Motion> -x 20 -y 20 -warp 1
>> schedules an idle callback 'DoWarp'.
>>
>> We want this callback to be serviced before requesting the pointer
>> position through
>> set res [winfo pointerxy .]
>> and that's why I'm calling 'update idletasks' in between these two
>> statements.
>>
>> If I remove this 'update idletasks', then I reproduce the behavior
>> you're seeing, this is normal and expected.
>>
>> But it shouldn't happen with the 'update idletasks'.
>> The test works on my system and I simply have no idea why it doesn't on
>> yours.
>>
>> Can you start debugging this? It's hard for me to guess since I don't
>> reproduce.
>>
>> The first thing to check is that in wish the following command:
>> event generate {} <Motion> -x 20 -y 20 -warp 1
>> moves the pointer at the correct position (20,20) in screen coordinates.
>> I'm sure it does so this should be a timing/event issue specific to the
>> test. Then, look at how the test can be improved to make it more robust
>> (against... what exactly...?)
>>
>> Thanks,
>> Francois
>>
> I have tried it manually, copy the test into wish: works always
> I have tried it multiple times:
>
> nmake -f Makefile.vc test TESTFLAGS="-file bind.test -match bind-34.2
> -verbose bte"
>
> Result: 5 ok, 2 failures. So, roughly 1 of 3 fail.
I could reproduce, but much less often than you (one in 50 times,
approximately).
I have committed a change to help bind-34.* tests to pass on Windows,
please see the associated theory here:
https://core.tcl-lang.org/tk/tktview?name=69b48f427e
Could you please try again core-8-6-branch and report your findings in
the ticket?
Thanks!
Francois
>
> THank you,
> Harald
|
|
From: Donald G P. <don...@ni...> - 2018-10-09 20:36:46
|
On 10/09/2018 03:06 PM, Donald G Porter via Tcl-Core wrote: > Now available at > > https://sourceforge.net/projects/tcl/files/Tcl/8.6.9/ > > is a candidate file making up a pre-release of Tcl 8.6.9. You should find RC0 for Tk 8.6.9 there now too. Also not ready to be a real release yet, but suitable for smoke testing. Report what you find. -- | Don Porter Applied and Computational Mathematics Division | | don...@ni... Information Technology Laboratory | | http://math.nist.gov/~DPorter/ NIST | |______________________________________________________________________| |
|
From: Francois V. <fvo...@fr...> - 2018-10-09 20:56:05
|
Le 09/10/2018 à 22:36, Donald G Porter via Tcl-Core a écrit : > You should find RC0 for Tk 8.6.9 there now too. Also not ready to be a > real release yet, but suitable for smoke testing. Report what you find. > Results for Tk core-8-6-9-rc branch at [86e90061] on Windows Vista: - build fine with MSVC 2008 (I tried with symbols) - tests results: For Tk: all.tcl: Total 9447 Passed 8177 Skipped 1270 Failed 0 For Ttk: all.tcl: Total 466 Passed 452 Skipped 14 Failed 0 Cheers, Francois |
|
From: Kevin W. <kw...@co...> - 2018-10-10 00:07:47
|
On 10/9/18 3:06 PM, Donald G Porter via Tcl-Core wrote: > This will not be the release. A release of Tk is not yet in place. Good thing, too. Tk on the Mac is currently a mess; because of API changes in the just-released macOS 10.14, windows don't display if Tk is built there. They are blank. We are working as quickly as possible on a fix, but it's complicated. You can follow the mac-mojave branch at Fossil for updates. --Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com |
|
From: Steve L. <st...@di...> - 2018-10-10 03:19:43
|
It seems Tk isn’t the only one to encounter problems - see https://github.com/macvim-dev/macvim/issues/751 On 10 Oct 2018, 8:08 AM +0800, Kevin Walzer <kw...@co...>, wrote: > On 10/9/18 3:06 PM, Donald G Porter via Tcl-Core wrote: > > This will not be the release. A release of Tk is not yet in place. > > Good thing, too. Tk on the Mac is currently a mess; because of API > changes in the just-released macOS 10.14, windows don't display if Tk is > built there. They are blank. We are working as quickly as possible on a > fix, but it's complicated. You can follow the mac-mojave branch at > Fossil for updates. > > --Kevin > > -- > Kevin Walzer > Code by Kevin > http://www.codebykevin.com > > > > _______________________________________________ > Tcl-Core mailing list > Tcl...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-core |
|
From: Stefan S. <ste...@wu...> - 2018-10-10 09:29:21
|
>> This will not be the release. A release of Tk is not yet in place. > > Good thing, too. Tk on the Mac is currently a mess; because of API > changes in the just-released macOS 10.14, windows don't display if Tk > is built there. They are blank. We are working as quickly as possible > on a fix, but it's complicated. You can follow the mac-mojave branch > at Fossil for updates. Some are aware, I know, but for the records: Tcl also runs in deprecation warnings starting with 10.12: tcl/macosx/tclMacOSXNotify.c:110:8: warning: 'OSSpinLock' is deprecated: first deprecated in macOS 10.12 - Use os_unfair_lock() from <os/lock.h> instead [-Wdeprecated-declarations] See https://travis-ci.com/nm-wu/nsf/jobs/149657057#L421 Stefan |
|
From: Stefan S. <ste...@wu...> - 2018-10-10 11:45:53
|
> Now available at > > https://sourceforge.net/projects/tcl/files/Tcl/8.6.9/ > > is a candidate file making up a pre-release of Tcl 8.6.9. Results for macOS 10.13.6: - Xcode 9.4.1, clang-902.0.39.2 - Xcode 10 (clang-1000.11.45.2) - gcc-mp-8 (MacPorts gcc8 8.2.0_0) 8.2.0 ./configure && make test ./configure && make CC=gcc-mp-8 test (with and w/o --disable-corefoundation) (with and w/o --enable-dtrace) (with and w/o --enable-framework) > all.tcl: Total 33456 Passed 30359 Skipped 3095 > Failed 2 > Sourced 149 Test Files. Failing ones: ==== macOSXFCmd-2.7 MacOSXSetFileAttribute - rsrclength FAILED ==== Contents of test case: catch {file delete -force -- foo.test} close [open foo.test w] catch { set f [open foo.test/..namedfork/rsrc w] fconfigure $f -translation lf -eofchar {} puts -nonewline $f "foo" close $f } list [catch {file attributes foo.test -rsrclength} msg] $msg [catch {file attributes foo.test -rsrclength 0} msg] $msg [catch {file attributes foo.test -rsrclength} msg] $msg [file delete -force -- foo.test] ---- Result was: 0 3 0 {} 0 3 {} ---- Result should have been (exact matching): 0 3 0 {} 0 0 {} ==== macOSXFCmd-2.7 FAILED ==== macOSXFCmd-4.1 TclMacOSXMatchType FAILED ==== Contents of test case: file mkdir globtest cd globtest foreach f {bar baz foo inv inw .nv reg} { catch {file delete -force -- $f.test} close [open $f.test w] } catch {file delete -force -- dir.test} file mkdir dir.test catch { file attributes bar.test -type FOOT file attributes baz.test -creator FOOC -type FOOT file attributes foo.test -creator FOOC file attributes inv.test -hidden 1 file attributes inw.test -hidden 1 -type FOOT file attributes dir.test -hidden 1 } set res [list [catch {glob *.test} msg] $msg [catch {glob -types FOOT *.test} msg] $msg [catch {glob -types {{macintosh type FOOT}} *.test} msg] $msg [catch {glob -types FOOTT *.test} msg] $msg [catch {glob -types {{macintosh type FOOTT}} *.test} msg] $msg [catch {glob -types {{macintosh type {}}} *.test} msg] $msg [catch {glob -types {{macintosh creator FOOC}} *.test} msg] $msg [catch {glob -types {{macintosh creator FOOC} {macintosh type FOOT}} *.test} msg] $msg [catch {glob -types hidden *.test} msg] $msg [catch {glob -types {hidden FOOT} *.test} msg] $msg ] cd .. file delete -force globtest set res ---- Result was: 0 {foo.test bar.test reg.test baz.test dir.test inv.test inw.test} 0 {bar.test baz.test inw.test} 0 {bar.test baz.test inw.test} 1 {bad argument to "-types": FOOTT} 1 {expected Macintosh OS type but got "FOOTT": } 0 {foo.test reg.test inv.test} 0 {foo.test baz.test} 0 baz.test 0 {.nv.test dir.test inv.test inw.test} 0 inw.test ---- Result should have been (exact matching): 0 {bar.test baz.test dir.test foo.test inv.test inw.test reg.test} 0 {bar.test baz.test inw.test} 0 {bar.test baz.test inw.test} 1 {bad argument to "-types": FOOTT} 1 {expected Macintosh OS type but got "FOOTT": } 0 {foo.test inv.test reg.test} 0 {baz.test foo.test} 0 baz.test 0 {.nv.test dir.test inv.test inw.test} 0 inw.test ==== macOSXFCmd-4.1 FAILED -- Institute for Information Systems and New Media WU Vienna, Austria Welthandelsplatz 1, Building D2, A-1020 Vienna ste...@wu... http://nm.wu.ac.at/en/sobernig t. +43-1-31336-4878 f. +43-1-31336-90-4878 |
|
From: Steve L. <st...@di...> - 2018-10-10 12:12:27
|
Results for macOS Mojave 10.14.1 beta
- Xcode 10.0 / LLVM version 10.0.0 (clang-1000.11.45.2)
cd unix && ./configure && make test
As per Stefan’s earlier mail, lots of build warnings for macosx/tclMacOSXNotify.c about 'OSSpinLockLock' being deprecated: first deprecated in macOS 10.12 - Use os_unfair_lock_lock() instead. Also ld: warning: option -prebind is obsolete and being ignored.
results …
all.tcl: Total 33456 Passed 30355 Skipped 3095 Failed 6
Sourced 149 Test Files.
Files with failing tests: macOSXFCmd.test socket.test
Number of tests skipped for each constraint:
9 !ieeeFloatingPoint
3 asyncPipeChan
76 bigEndian
5 bug-3057639
49 dde
4 dontCopyLinks
64 emptyTest
1 execMknod
5 fullutf
2 hasIsoLocale
1 knownBadTest
41 knownBug
2 largefileSupport
100 localeRegexp
52 longIs32bit
82 memory
46 nonPortable
1 notDarwin9
5 notNetworkFilesystem
1 notValgrind
9 nt
1 pcOnly
1996 serverNeeded
3 singleTestInterp
1 testexprparser && !ieeeFloatingPoint
1 testwinclock
21 testwordend
3 tip389
2 unthreaded
2 wideBiggerThanInt
486 win
4 winVista
6 xdev
Failing tests …
==== macOSXFCmd-2.7 MacOSXSetFileAttribute - rsrclength FAILED
==== Contents of test case:
catch {file delete -force -- foo.test}
close [open foo.test w]
catch {
set f [open foo.test/..namedfork/rsrc w]
fconfigure $f -translation lf -eofchar {}
puts -nonewline $f "foo"
close $f
}
list [catch {file attributes foo.test -rsrclength} msg] $msg [catch {file attributes foo.test -rsrclength 0} msg] $msg [catch {file attributes foo.test -rsrclength} msg] $msg [file delete -force -- foo.test]
---- Result was:
0 3 0 {} 0 3 {}
---- Result should have been (exact matching):
0 3 0 {} 0 0 {}
==== macOSXFCmd-2.7 FAILED
==== macOSXFCmd-4.1 TclMacOSXMatchType FAILED
==== Contents of test case:
file mkdir globtest
cd globtest
foreach f {bar baz foo inv inw .nv reg} {
catch {file delete -force -- $f.test}
close [open $f.test w]
}
catch {file delete -force -- dir.test}
file mkdir dir.test
catch {
file attributes bar.test -type FOOT
file attributes baz.test -creator FOOC -type FOOT
file attributes foo.test -creator FOOC
file attributes inv.test -hidden 1
file attributes inw.test -hidden 1 -type FOOT
file attributes dir.test -hidden 1
}
set res [list [catch {glob *.test} msg] $msg [catch {glob -types FOOT *.test} msg] $msg [catch {glob -types {{macintosh type FOOT}} *.test} msg] $msg [catch {glob -types FOOTT *.test} msg] $msg [catch {glob -types {{macintosh type FOOTT}} *.test} msg] $msg [catch {glob -types {{macintosh type {}}} *.test} msg] $msg [catch {glob -types {{macintosh creator FOOC}} *.test} msg] $msg [catch {glob -types {{macintosh creator FOOC} {macintosh type FOOT}} *.test} msg] $msg [catch {glob -types hidden *.test} msg] $msg [catch {glob -types {hidden FOOT} *.test} msg] $msg ]
cd ..
file delete -force globtest
set res
---- Result was:
0 {foo.test bar.test reg.test baz.test dir.test inv.test inw.test} 0 {bar.test baz.test inw.test} 0 {bar.test baz.test inw.test} 1 {bad argument to "-types": FOOTT} 1 {expected Macintosh OS type but got "FOOTT": } 0 {foo.test reg.test inv.test} 0 {foo.test baz.test} 0 baz.test 0 {.nv.test dir.test inv.test inw.test} 0 inw.test
---- Result should have been (exact matching):
0 {bar.test baz.test dir.test foo.test inv.test inw.test reg.test} 0 {bar.test baz.test inw.test} 0 {bar.test baz.test inw.test} 1 {bad argument to "-types": FOOTT} 1 {expected Macintosh OS type but got "FOOTT": } 0 {foo.test inv.test reg.test} 0 {baz.test foo.test} 0 baz.test 0 {.nv.test dir.test inv.test inw.test} 0 inw.test
==== macOSXFCmd-4.1 FAILED
==== socket_inet-5.1 byte order problems, socket numbers, htons FAILED
==== Contents of test case:
if {![catch {socket -server dodo 0x1} msg]} {
close $msg
return {htons problem, should be disallowed, are you running as SU?}
}
return {couldn't open socket: not owner}
---- Result was:
htons problem, should be disallowed, are you running as SU?
---- Result should have been (exact matching):
couldn't open socket: not owner
==== socket_inet-5.1 FAILED
==== socket_inet-5.3 byte order problems, socket numbers, htons FAILED
==== Contents of test case:
if {![catch {socket -server dodo 21} msg]} {
close $msg
return {htons problem, should be disallowed, are you running as SU?}
}
return {couldn't open socket: not owner}
---- Result was:
htons problem, should be disallowed, are you running as SU?
---- Result should have been (exact matching):
couldn't open socket: not owner
==== socket_inet-5.3 FAILED
==== socket_inet6-5.1 byte order problems, socket numbers, htons FAILED
==== Contents of test case:
if {![catch {socket -server dodo 0x1} msg]} {
close $msg
return {htons problem, should be disallowed, are you running as SU?}
}
return {couldn't open socket: not owner}
---- Result was:
htons problem, should be disallowed, are you running as SU?
---- Result should have been (exact matching):
couldn't open socket: not owner
==== socket_inet6-5.1 FAILED
==== socket_inet6-5.3 byte order problems, socket numbers, htons FAILED
==== Contents of test case:
if {![catch {socket -server dodo 21} msg]} {
close $msg
return {htons problem, should be disallowed, are you running as SU?}
}
return {couldn't open socket: not owner}
---- Result was:
htons problem, should be disallowed, are you running as SU?
---- Result should have been (exact matching):
couldn't open socket: not owner
==== socket_inet6-5.3 FAILED
|
|
From: Christian G. <aur...@gm...> - 2018-10-10 12:21:09
|
That one seems to be a bug in the test code:
Am 10.10.18 um 14:12 schrieb Steve Landers:
> ==== macOSXFCmd-4.1 TclMacOSXMatchType FAILED
> ==== Contents of test case:
>
> file mkdir globtest
> cd globtest
> foreach f {bar baz foo inv inw .nv reg} {
> catch {file delete -force -- $f.test}
> close [open $f.test w]
> }
> catch {file delete -force -- dir.test}
> file mkdir dir.test
> catch {
> file attributes bar.test -type FOOT
> file attributes baz.test -creator FOOC -type FOOT
> file attributes foo.test -creator FOOC
> file attributes inv.test -hidden 1
> file attributes inw.test -hidden 1 -type FOOT
> file attributes dir.test -hidden 1
> }
> set res [list [catch {glob *.test} msg] $msg [catch {glob -types FOOT
> *.test} msg] $msg [catch {glob -types {{macintosh type FOOT}} *.test}
> msg] $msg [catch {glob -types FOOTT *.test} msg] $msg [catch {glob
> -types {{macintosh type FOOTT}} *.test} msg] $msg [catch {glob -types
> {{macintosh type {}}} *.test} msg] $msg [catch {glob -types {{macintosh
> creator FOOC}} *.test} msg] $msg [catch {glob -types {{macintosh creator
> FOOC} {macintosh type FOOT}} *.test} msg] $msg [catch {glob -types
> hidden *.test} msg] $msg [catch {glob -types {hidden FOOT} *.test} msg]
> $msg ]
> cd ..
> file delete -force globtest
> set res
>
> ---- Result was:
> 0 {foo.test bar.test reg.test baz.test dir.test inv.test inw.test} 0
> {bar.test baz.test inw.test} 0 {bar.test baz.test inw.test} 1 {bad
> argument to "-types": FOOTT} 1 {expected Macintosh OS type but got
> "FOOTT": } 0 {foo.test reg.test inv.test} 0 {foo.test baz.test} 0
> baz.test 0 {.nv.test dir.test inv.test inw.test} 0 inw.test
> ---- Result should have been (exact matching):
> 0 {bar.test baz.test dir.test foo.test inv.test inw.test reg.test} 0
> {bar.test baz.test inw.test} 0 {bar.test baz.test inw.test} 1 {bad
> argument to "-types": FOOTT} 1 {expected Macintosh OS type but got
> "FOOTT": } 0 {foo.test inv.test reg.test} 0 {baz.test foo.test} 0
> baz.test 0 {.nv.test dir.test inv.test inw.test} 0 inw.test
> ==== macOSXFCmd-4.1 FAILED
The difference is the order of the *.test files returned. [glob] is not
specified to return it in alphabetical order, in fact this seems to
depend on the underlying filesystem.
Christian
|
|
From: Kevin W. <kw...@co...> - 2018-10-10 12:18:08
|
On 10/10/18 7:45 AM, Stefan Sobernig wrote: >> Now available at >> >> https://sourceforge.net/projects/tcl/files/Tcl/8.6.9/ >> >> is a candidate file making up a pre-release of Tcl 8.6.9. > Results for macOS 10.13.6: > - Xcode 9.4.1, clang-902.0.39.2 > - Xcode 10 (clang-1000.11.45.2) > - gcc-mp-8 (MacPorts gcc8 8.2.0_0) 8.2.0 > > ./configure && make test > ./configure && make CC=gcc-mp-8 test > > (with and w/o --disable-corefoundation) > (with and w/o --enable-dtrace) > (with and w/o --enable-framework) >> all.tcl: Total 33456 Passed 30359 Skipped 3095 >> Failed 2 >> Sourced 149 Test Files. > Failing ones: > > ==== macOSXFCmd-2.7 MacOSXSetFileAttribute - rsrclength FAILED > ==== Contents of test case: > > catch {file delete -force -- foo.test} > close [open foo.test w] > catch { > set f [open foo.test/..namedfork/rsrc w] > fconfigure $f -translation lf -eofchar {} > puts -nonewline $f "foo" > close $f > } > list [catch {file attributes foo.test -rsrclength} msg] $msg [catch > {file attributes foo.test -rsrclength 0} msg] $msg [catch {file > attributes foo.test -rsrclength} msg] $msg [file delete -force -- foo.test] > > ---- Result was: > 0 3 0 {} 0 3 {} > ---- Result should have been (exact matching): > 0 3 0 {} 0 0 {} > ==== macOSXFCmd-2.7 FAILED > > ==== macOSXFCmd-4.1 TclMacOSXMatchType FAILED > ==== Contents of test case: > > file mkdir globtest > cd globtest > foreach f {bar baz foo inv inw .nv reg} { > catch {file delete -force -- $f.test} > close [open $f.test w] > } > catch {file delete -force -- dir.test} > file mkdir dir.test > catch { > file attributes bar.test -type FOOT > file attributes baz.test -creator FOOC -type FOOT > file attributes foo.test -creator FOOC > file attributes inv.test -hidden 1 > file attributes inw.test -hidden 1 -type FOOT > file attributes dir.test -hidden 1 > } > set res [list [catch {glob *.test} msg] $msg [catch {glob -types > FOOT *.test} msg] $msg [catch {glob -types {{macintosh type FOOT}} > *.test} msg] $msg [catch {glob -types FOOTT *.test} msg] $msg [catch > {glob -types {{macintosh type FOOTT}} *.test} msg] $msg [catch {glob > -types {{macintosh type {}}} *.test} msg] $msg [catch {glob -types > {{macintosh creator FOOC}} *.test} msg] $msg [catch {glob -types > {{macintosh creator FOOC} {macintosh type FOOT}} *.test} msg] $msg > [catch {glob -types hidden *.test} msg] $msg [catch {glob -types > {hidden FOOT} *.test} msg] $msg ] > cd .. > file delete -force globtest > set res > > ---- Result was: > 0 {foo.test bar.test reg.test baz.test dir.test inv.test inw.test} 0 > {bar.test baz.test inw.test} 0 {bar.test baz.test inw.test} 1 {bad > argument to "-types": FOOTT} 1 {expected Macintosh OS type but got > "FOOTT": } 0 {foo.test reg.test inv.test} 0 {foo.test baz.test} 0 > baz.test 0 {.nv.test dir.test inv.test inw.test} 0 inw.test > ---- Result should have been (exact matching): > 0 {bar.test baz.test dir.test foo.test inv.test inw.test reg.test} 0 > {bar.test baz.test inw.test} 0 {bar.test baz.test inw.test} 1 {bad > argument to "-types": FOOTT} 1 {expected Macintosh OS type but got > "FOOTT": } 0 {foo.test inv.test reg.test} 0 {baz.test foo.test} 0 > baz.test 0 {.nv.test dir.test inv.test inw.test} 0 inw.test > ==== macOSXFCmd-4.1 FAILED > > I'm not sure why the rsrc and type-and-creator-code tests are being run; that stuff has been obsolete on the Mac for years. The failure of these tests signifies nothing. --Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com |
|
From: Francois V. <fvo...@fr...> - 2018-10-17 20:51:09
|
Le 10/10/2018 à 14:17, Kevin Walzer a écrit : > I'm not sure why the rsrc and type-and-creator-code tests are being > run; that stuff has been obsolete on the Mac for years. The failure of > these tests signifies nothing. In my opinion this signifies that the test suite needs an update, or do I miss something? Francois |
|
From: Harald O. <har...@el...> - 2018-10-12 14:54:54
|
Am 09.10.2018 um 21:06 schrieb Donald G Porter via Tcl-Core: > > Now available at > > https://sourceforge.net/projects/tcl/files/Tcl/8.6.9/ > > is a candidate file making up a pre-release of Tcl 8.6.9. > > This will not be the release. A release of Tk is not yet in place. > None of the bundled packages are in place yet. Release notes and > changes files still require updates. > > At this point I'm looking for build tests on as many platforms as you > can manage, so a real release can happen soon with good confidence it > isn't obviously broken. > > Please report any new troubles you encounter, particularly any that seem > severe enough they should prevent release. Donald, thank you a lot for tcl8.6.9a0. On win 32 with msvc 6 the test result is as follows (compared to tcl/tk8.6.8): tcl: no new failures, cured tests: iortrans-11.1, iortrans-11.2 tk: no new failures, cured tests: textTag-18.1 So, all ok from my side. Harald |
|
From: Francois V. <fvo...@fr...> - 2018-10-12 20:51:12
|
Le 12/10/2018 à 16:54, Harald Oehlmann a écrit : > thank you a lot for tcl8.6.9a0. On win 32 with msvc 6 the test result > is as follows (compared to tcl/tk8.6.8): tcl: no new failures, cured > tests: iortrans-11.1, iortrans-11.2 tk: no new failures, cured tests: > textTag-18.1 Doubtful. On what version of Windows did you test Tk? I think you said previously you are running Win 10? Remember: https://core.tcl.tk/tk/info/69b48f427e94899a This bug was triggered by Win 10 Falls Creator Update and was not fixed by the April 2018 Update. However perhaps this got fixed by the October 2018 Update? Do you already have this october 2018 Update installed? Because MS had kind of a problem with it: https://www.theverge.com/2018/10/9/17957506/microsoft-windows-10-october-2018-update-data-deletion-fix Fortunately the loss of end user data this update brought is obviously compensated by the numerous breakthroughs in this version, e.g. (selected quotes from the changelog https://www.windowscentral.com/windows-10-october-2018-changelog ): - Microsoft Edge now features a subtle drop shadow behind tabs. - Windows Calculator now correctly calculates square roots for perfect squares. - Notepad now features Unix/Linus line endings (LF) and Macintosh line endings (CR.) - Wrap-around find/replace now available in Notepad. - When your volume is muted, the volume icons in the Sound Settings page will also now appear muted - and a lot more !! ROTFL! Seriously: Do you confirm this test textTag-18.1 is fixed for Win10 with the October 2018 Update? Would be surprising but very good news. F. |
|
From: Eric B. <eri...@gm...> - 2018-10-13 13:38:39
Attachments:
tcl_tests_869.txt
tk_tests_869.txt
|
Hi, here are my test results on Win10 1803, compiled with Visual Studio 2010 using (great work done by) APN makefiles 5 failures for Tcl. 0 failures for Tk. Eric Le ven. 12 oct. 2018 à 22:51, Francois Vogel <fvo...@fr...> a écrit : > Le 12/10/2018 à 16:54, Harald Oehlmann a écrit : > > thank you a lot for tcl8.6.9a0. On win 32 with msvc 6 the test result > > is as follows (compared to tcl/tk8.6.8): tcl: no new failures, cured > > tests: iortrans-11.1, iortrans-11.2 tk: no new failures, cured tests: > > textTag-18.1 > > Doubtful. On what version of Windows did you test Tk? I think you said > previously you are running Win 10? Remember: > > https://core.tcl.tk/tk/info/69b48f427e94899a > > This bug was triggered by Win 10 Falls Creator Update and was not fixed > by the April 2018 Update. > > However perhaps this got fixed by the October 2018 Update? Do you > already have this october 2018 Update installed? Because MS had kind of > a problem with it: > > > https://www.theverge.com/2018/10/9/17957506/microsoft-windows-10-october-2018-update-data-deletion-fix > > Fortunately the loss of end user data this update brought is obviously > compensated by the numerous breakthroughs in this version, e.g. > (selected quotes from the changelog > https://www.windowscentral.com/windows-10-october-2018-changelog ): > > - Microsoft Edge now features a subtle drop shadow behind tabs. > - Windows Calculator now correctly calculates square roots for perfect > squares. > - Notepad now features Unix/Linus line endings (LF) and Macintosh line > endings (CR.) > - Wrap-around find/replace now available in Notepad. > - When your volume is muted, the volume icons in the Sound Settings page > will also now appear muted > - and a lot more !! ROTFL! > > Seriously: Do you confirm this test textTag-18.1 is fixed for Win10 with > the October 2018 Update? Would be surprising but very good news. > > F. > > > > _______________________________________________ > Tcl-Core mailing list > Tcl...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-core > |
|
From: Jan N. <jan...@gm...> - 2018-10-18 06:50:32
|
With this commit:
<https://core.tcl.tk/tcl/info/5fbb107638379d35>
all of those 5 test failures for Tcl should be fixed new.
The reason:
set major [string index $tcl_platform(osVersion) 0]
This gives "1" on Windows 10, not the expected "10" ;-)
Op za 13 okt. 2018 om 15:39 schreef Eric Boudaillier
<eri...@gm...>:
>
> Hi, here are my test results on Win10 1803, compiled with Visual Studio 2010 using (great work done by) APN makefiles
>
> 5 failures for Tcl.
> 0 failures for Tk.
>
> Eric
>
> Le ven. 12 oct. 2018 à 22:51, Francois Vogel <fvo...@fr...> a écrit :
>>
>> Le 12/10/2018 à 16:54, Harald Oehlmann a écrit :
>> > thank you a lot for tcl8.6.9a0. On win 32 with msvc 6 the test result
>> > is as follows (compared to tcl/tk8.6.8): tcl: no new failures, cured
>> > tests: iortrans-11.1, iortrans-11.2 tk: no new failures, cured tests:
>> > textTag-18.1
>>
>> Doubtful. On what version of Windows did you test Tk? I think you said
>> previously you are running Win 10? Remember:
>>
>> https://core.tcl.tk/tk/info/69b48f427e94899a
>>
>> This bug was triggered by Win 10 Falls Creator Update and was not fixed
>> by the April 2018 Update.
>>
>> However perhaps this got fixed by the October 2018 Update? Do you
>> already have this october 2018 Update installed? Because MS had kind of
>> a problem with it:
>>
>> https://www.theverge.com/2018/10/9/17957506/microsoft-windows-10-october-2018-update-data-deletion-fix
>>
>> Fortunately the loss of end user data this update brought is obviously
>> compensated by the numerous breakthroughs in this version, e.g.
>> (selected quotes from the changelog
>> https://www.windowscentral.com/windows-10-october-2018-changelog ):
>>
>> - Microsoft Edge now features a subtle drop shadow behind tabs.
>> - Windows Calculator now correctly calculates square roots for perfect
>> squares.
>> - Notepad now features Unix/Linus line endings (LF) and Macintosh line
>> endings (CR.)
>> - Wrap-around find/replace now available in Notepad.
>> - When your volume is muted, the volume icons in the Sound Settings page
>> will also now appear muted
>> - and a lot more !! ROTFL!
>>
>> Seriously: Do you confirm this test textTag-18.1 is fixed for Win10 with
>> the October 2018 Update? Would be surprising but very good news.
>>
>> F.
>>
>>
>>
>> _______________________________________________
>> Tcl-Core mailing list
>> Tcl...@li...
>> https://lists.sourceforge.net/lists/listinfo/tcl-core
>
> _______________________________________________
> Tcl-Core mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-core
|
|
From: Harald O. <har...@el...> - 2018-10-14 11:58:40
|
Francois, thank you for caring ! Am 12.10.2018 um 22:49 schrieb Francois Vogel: > Le 12/10/2018 à 16:54, Harald Oehlmann a écrit : >> thank you a lot for tcl8.6.9a0. On win 32 with msvc 6 the test result >> is as follows (compared to tcl/tk8.6.8): tcl: no new failures, cured >> tests: iortrans-11.1, iortrans-11.2 tk: no new failures, cured tests: >> textTag-18.1 > > Doubtful. On what version of Windows did you test Tk? I think you said > previously you are running Win 10? Remember: > > https://core.tcl.tk/tk/info/69b48f427e94899a I double-checked: textTag-18.1 is successfully tested. It is Windows 10 1803 > However perhaps this got fixed by the October 2018 Update? No, 1803 is the April one. > Seriously: Do you confirm this test textTag-18.1 is fixed for Win10 with > the October 2018 Update? Would be surprising but very good news. No, with the April one. Maybe, there was a hotfix or we changed something, I don't know. Thank you, Harald |
|
From: Francois V. <fvo...@fr...> - 2018-10-14 15:59:07
|
Le 14/10/2018 à 13:58, Harald Oehlmann a écrit : > Am 12.10.2018 um 22:49 schrieb Francois Vogel: >> On what version of Windows did you test Tk? I think you said >> previously you are running Win 10? Remember: >> >> https://core.tcl.tk/tk/info/69b48f427e94899a > I double-checked: textTag-18.1 is successfully tested. > It is Windows 10 1803 How strange. I remember that Ashok confirmed in the above ticket that Win10 1803 (so the April 2018 version) did NOT fix this. Could Ashok perhaps confirm again his findings? > Maybe, there was a hotfix or we changed > something, I don't know. Hmm... I would feel more comfortable if we knew what made this test suddenly pass. Checking the Tk side of things is easy: just bisect between The Tk version at the time the Falls Creator update went in, and the current Tk version. A good candidate for what we changed is [745b43440b2cbe03], that fixed [e20d5ca7cd]. That one was for macOS, however this change (the added 'update') could have fixed the Win10 case as well (however the workaround was to add 'after 50 ; update', not just 'update'). Checking the Win10 side of changes looks more difficult to me. However, Ashok in his analysis of the ticket found the root cause for the failure, and that was in a Windows API call (SetCursorPos) that changes with the Falls Creator Update version of Win 10. Quoting Ashok: "what seems to be happening is that the SetCursorPos call which triggers the Windows WM_MOVEMOUSE message does so after some delay in Windows 10 compared to earlier versions". This problem triggered several reports from users/developers of other applications than Tcl/Tk (Ashok gave the links in the ticket), we could probably check whether these issues are fixed, indicating the root cause that is common with Tk is fixed or not. Regards, Francois |
|
From: Harald O. <har...@el...> - 2018-10-14 16:14:44
|
Francois, I just rechecked 8.6.8 with my current system (Win 10 1803). The failure is still identically there. The test log is identical to (I suppose it was Win10 1703). So, it should be a Tk change between 8.6.8 and 8.6.9a0. Thank you, Harald Am 14.10.2018 um 17:57 schrieb Francois Vogel: > Le 14/10/2018 à 13:58, Harald Oehlmann a écrit : >> Am 12.10.2018 um 22:49 schrieb Francois Vogel: >>> On what version of Windows did you test Tk? I think you said >>> previously you are running Win 10? Remember: >>> >>> https://core.tcl.tk/tk/info/69b48f427e94899a >> I double-checked: textTag-18.1 is successfully tested. >> It is Windows 10 1803 > > How strange. I remember that Ashok confirmed in the above ticket that > Win10 1803 (so the April 2018 version) did NOT fix this. Could Ashok > perhaps confirm again his findings? > >> Maybe, there was a hotfix or we changed >> something, I don't know. > > Hmm... I would feel more comfortable if we knew what made this test > suddenly pass. > > Checking the Tk side of things is easy: just bisect between The Tk > version at the time the Falls Creator update went in, and the current Tk > version. > A good candidate for what we changed is [745b43440b2cbe03], that fixed > [e20d5ca7cd]. That one was for macOS, however this change (the added > 'update') could have fixed the Win10 case as well (however the > workaround was to add 'after 50 ; update', not just 'update'). > > Checking the Win10 side of changes looks more difficult to me. However, > Ashok in his analysis of the ticket found the root cause for the > failure, and that was in a Windows API call (SetCursorPos) that changes > with the Falls Creator Update version of Win 10. Quoting Ashok: "what > seems to be happening is that the SetCursorPos call which triggers the > Windows WM_MOVEMOUSE message does so after some delay in Windows 10 > compared to earlier versions". > This problem triggered several reports from users/developers of other > applications than Tcl/Tk (Ashok gave the links in the ticket), we could > probably check whether these issues are fixed, indicating the root cause > that is common with Tk is fixed or not. > > Regards, > Francois > -- ELMICRON Dr. Harald Oehlmann GmbH Koesener Str. 85 06618 NAUMBURG - Germany Phone: +49 3445 78112-0 Fax: +49 3445 78112-19 www.Elmicron.de German legal references: Geschaeftsfuehrer: Dr. Harald Oehlmann UST Nr. / VAT ID No.: DE206105272 HRB 212803 Stendal |
Thanks for helping keep SourceForge clean.
X