|
From: Phillip B. <phi...@um...> - 2026-08-17 16:43:27
|
I see a similar failure. I have drives C: along with N: and T: which both
mount to a Synology NAS.
If I add an empty USB drive that calls itself D:, I get a different failure:
Baseline case, with no D: drive:
PS C:\Users\PHILB\tcl-tk\tcl\tests> ..\win\Release_AMD64_VC1950\tclsh91.exe
.\winFCmd.test
==== winFCmd-16.10 Windows file normalization FAILED
==== Contents of test case:
file norm ${d}:foo
---- Test setup failed:
couldn't change working directory to "D:": no such file or directory
---- errorInfo(setup): couldn't change working directory to "D:": no such
file or directory
while executing
"cd ${dd}:"
("uplevel" body line 2)
invoked from within
"uplevel 1 $setup"
---- errorCode(setup): POSIX ENOENT {no such file or directory}
==== winFCmd-16.10 FAILED
winFCmd.test: Total 234 Passed 112 Skipped 121 Failed 1
Number of tests skipped for each constraint:
9 cdrom
3 emptyTest
13 englishLocale
2 exdev
1 knownMsvcBug
1 nonPortable
2 testchmod
90 testfile
Adding the USB D: drive:
PS C:\Users\PHILB\tcl-tk\tcl\tests> ..\win\Release_AMD64_VC1950\tclsh91.exe
.\winFCmd.test
==== winFCmd-16.10 Windows file normalization FAILED
==== Contents of test case:
file norm ${d}:foo
---- Result was:
C:/foo
---- Result should have been (exact matching):
C:/Users/PHILB/tcl-tk/tcl/tests/foo
==== winFCmd-16.10 FAILED
winFCmd.test: Total 234 Passed 112 Skipped 121 Failed 1
Number of tests skipped for each constraint:
9 cdrom
3 emptyTest
13 englishLocale
1 knownMsvcBug
1 nonPortable
2 testchmod
92 testfile
PS C:\Users\PHILB\tcl-tk\tcl\tests>
I have been seeing this failure in both forms for quite a while.
Phil
On Mon, Aug 17, 2026 at 9:02 AM Paul Obermeier <pa...@po...> wrote:
> I have drives C: and Z: (which mounts my Synology NAS). Both are
> accessible.
>
> Paul
>
> Am 17.08.2026 um 16:07 schrieb apnmbx-public--- via Tcl-Core:
> > The Windows exec errors are (as Paul said) due to assumption of English
> error messages. Not sure how to fix the tests other than constraint to code
> page 1033. (Changing to just a generic * wild card match is too loose.)
> >
> > The winFCmd-16.10 test is also a test case bug, not a core Tcl bug. I
> will have to look at it as I thought there was already a check based on
> drives available on the system before running the test. Paul, could you
> post which drives are present on the system and whether they are actually
> accessible (and not a unplugged pendrive, for example).
> >
> > In any case, neither of the failures need hold up the beta.
> >
> > /Ashok
> >
> > -----Original Message-----
> > From: Paul Obermeier <pa...@po...>
> > Sent: Sunday, August 16, 2026 10:50 PM
> > To: tcl...@li...
> > Subject: Re: [TCLCORE] Tcl 9.1b1 RC0 Release Candidate
> >
> > Here are the results of the TclTk 9.1b1 test suites using my BAWT build
> environments.
> >
> > Operating system Arch. Compiler Tcl-Errors Tk-Errors
> > ------------------------------------------------------------------
> > MacOS 15.7.7 M2 clang 17.0.0 0 3
> > Suse 15.6 x86_64 gcc 7.5.0 0 67
> > Raspberry Pi OS arm64 gcc 12.2.0 0 38
> > Windows 11 x86 gcc 15.2.0 4 0
> > Windows 11 x86_64 gcc 15.2.0 4 0
> > Windows 11 x86_64 VS2026 4 0
> >
> > Windows failures. The first 3 related to German output messages of
> Windows commands:
> >
> > ==== exec-win-6.3 exec - verify execution of exe in path masquerading as
> .com FAILED
> > ==== Contents of test case:
> >
> > exec chcp
> >
> > ---- Result was:
> > Aktive Codepage: 850.
> > ---- Result should have been (glob matching):
> > Active code*
> > ==== exec-win-6.3 FAILED
> >
> >
> > ==== exec-win-7.1 exec - verify Windows directory checked before PATH
> FAILED
> > ==== Contents of test case:
> >
> > # Verify path is correct by calling testApp and then
> > # the real attrib is picked up though not on path
> > list [exec testApp.exe -path] [exec attrib.exe /?]
> >
> > ---- Result was:
> >
> {C:\BawtBuilds\TclMinimal\TclMinimal-vs2026-9.1.0-9.1.0-Dynamic\vs2026\x64\Release\Build\Tcl\win\exec-win-7.1\testApp.exe}
> {Zeigt Dateiattribute an oder \uFFFDndert sie.
> >
> > ATTRIB [+R | -R] [+A | -A] [+S | -S] [+H | -H] [+O | -O] [+I | -I] [+X |
> -X] [+P | -P] [+U | -U]
> > [Laufwerk:][Pfad][Dateiname] [/S [/D]] [/L]
> > <More output skipped>
> >
> > ---- Result should have been (glob matching):
> > *testApp.exe*Displays or changes*
> > ==== exec-win-7.1 FAILED
> >
> >
> > ==== exec-win-7.3 exec - verify Windows program with dummy PATH FAILED
> > ==== Contents of test case:
> >
> > exec attrib /?
> >
> > ---- Result was:
> > Zeigt Dateiattribute an oder \uFFFDndert sie.
> >
> > ATTRIB [+R | -R] [+A | -A] [+S | -S] [+H | -H] [+O | -O] [+I | -I] [+X |
> -X] [+P | -P] [+U | -U]
> > [Laufwerk:][Pfad][Dateiname] [/S [/D]] [/L]
> > <More output skipped>
> >
> > ---- Result should have been (glob matching):
> > *Displays or changes file attributes*
> > ==== exec-win-7.3 FAILED
> >
> >
> > ==== winFCmd-16.10 Windows file normalization FAILED
> > ==== Contents of test case:
> >
> > file norm ${d}:foo
> >
> > ---- Test setup failed:
> > couldn't change working directory to "D:": no such file or directory
> > ---- errorInfo(setup): couldn't change working directory to "D:": no
> such file or directory
> > while executing
> > "cd ${dd}:"
> > ("uplevel" body line 2)
> > invoked from within
> > "uplevel 1 $setup"
> > ---- errorCode(setup): POSIX ENOENT {no such file or directory}
> > ==== winFCmd-16.10 FAILED
> >
> >
> > macOS failures:
> >
> > === imgPhInstance-1.1 fully opaque photo replaces the destination FAILED
> > ==== Contents of test case:
> >
> > .c create image 10 10 -anchor nw -image photo.opaque
> > update
> > list [pixelNear .c 15 15 #ff8000] [pixelNear .c 45 15 $bg]
> >
> > ---- Result was:
> > 1 0
> > ---- Result should have been (exact matching):
> > 1 1
> > ==== imgPhInstance-1.1 FAILED
> >
> >
> > === imgPhInstance-1.2 fully transparent photo leaves the destination
> untouched FAILED
> > ==== Contents of test case:
> >
> > .c create image 10 10 -anchor nw -image photo.clear
> > update
> > pixelNear .c 15 15 $bg
> >
> > ---- Result was:
> > 0
> > ---- Result should have been (exact matching):
> > 1
> > ==== imgPhInstance-1.2 FAILED
> >
> >
> > === imgPhInstance-2.1 binary alpha: opaque cells copy, clear cells show
> through FAILED
> > ==== Contents of test case:
> >
> > .c create image 10 10 -anchor nw -image photo.checker
> > update
> > list [pixelNear .c 14 14 #ff8000] [pixelNear .c 22 14 $bg]
> >
> > ---- Result was:
> > 1 0
> > ---- Result should have been (exact matching):
> > 1 1
> > ==== imgPhInstance-2.1 FAILED
> >
> >
> > Am 14.08.2026 um 21:53 schrieb Donald G Porter via Tcl-Core:
> >> Now available at
> >>
> >> https://sourceforge.net/projects/tcl/files/Tcl/9.1b1/
> >>
> >> are RC0 candidate source code distribution pre-releases of Tcl 9.1b1.
> >>
> >> These are the first candidate releases leading to the release of Tcl
> 9.1b1.
> >>
> >> The Tcl pre-release includes a pre-release of the package Thread 3.0.7.
> >> The released packages sqlite3 3.53.0, Itcl 4.3.8, and TDBC* 1.1.14 are
> also included.
> >>
> >> Please test these candidates on your platforms and report any blocking
> issues
> >> you discover.
> >>
> >> Please also report any known pending changes to Tcl that ought to be
> beta tested
> >> before a stable release. We want 9.1b1 to be the final beta release
> and it should
> >> contain all code needing beta testing.
> >>
> >> Thank you for your contributions and assistance.
> >>
> >
> >
> > _______________________________________________
> > 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
>
>
>
> _______________________________________________
> Tcl-Core mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-core
>
|