|
From: Marc C. <cul...@gm...> - 2025-11-14 10:53:17
|
In fact, it is not uncommon for test failures to be related to race conditions and timings are often different for the development build versus the deployment build. - Marc On Thu, Nov 13, 2025, 3:00 PM Torsten Berg <be...@ty...> wrote: > Ah, that's interesting. Yes, this sounds like a valid explanation for > running tests twice. Thanks for sharing! > > > Am 13.11.2025 um 17:21 schrieb Erik Leunissen <el...@xs...>: > > > > On 11/13/25 01:17, Torsten Berg wrote: > >> I just wonder why the tests run twice (and for me it also seems that > during the build things are done multiple teimes) but that may just be my > lack of wisdom regarding the build process. > > > > When I invoke "make test" on macOS from the source code dir, tests are > run twice: > > A. optimized (no symbols), indicated by "Deployment" > > B. unoptimized with debugging symbols, indicated by "Development" > > > > I am able to run just one of them when invoking "make test" from the > respective build directories (siblings of the source directory) [*]: > > build/Tcl/Deployment > > build/Tcl/Development > > > > That's just what I found out about how things are organized on my > system. I'm too > > unfamiliar with macOS to be able to say whether that is how it's > supposed to be, > > or whether other setups/invocations are advised. > > > > Regards, > > Erik Leunissen. > > -- > > [*] the setup for Tk is analoguous > > > > > > _______________________________________________ > Tcl-Core mailing list > Tcl...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-core > |