|
From: Phillip B. <phi...@um...> - 2026-01-18 23:46:46
|
Is there an easy way to reproduce this without all of the work that you have done Andreas? Perhaps you could create a tarball with the current state of your efforts and some run scripts that isolate the crash. Phil On Sun, Jan 18, 2026 at 11:42 AM Andreas Kupries <and...@gm...> wrote: > > > Why does this have to be so complicated? Why not just use a fossil > tarball > > url <https://fossil-scm.org/draft/help/www/tarball> to download the > > checkins which are being tested, unpack each tarball, build it, and run > the > > tests. (Actually, I would have a separate workflow for each tarball.) > > > > In my experience the tarball url is very fast. It is hugely simpler and > > faster than cloning a big fossil repository. > > The repo mirroring stuff actually precedes the CI work. > Its initial and main purpose is to maintain a backup of Tk on github. > > The CI was then added to that git mirror later, making it trivial to > get the sources it needed. > > > - Marc > > -- > Happy Tcling, > Andreas Kupries <and...@gm...> > <https://core.tcl-lang.org/akupries/> > <https://akupries.tclers.tk/> > Developer @ SUSE Software Solutions Germany GmbH > > ------------------------------------------------------------------------------- > > > > > _______________________________________________ > Tcl-Core mailing list > Tcl...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-core > |