From: Dipl. I. S. G. B. <se...@us...> - 2024-08-21 18:24:57
|
If the mentioned costs are about GHA (CI), then it is correct... (however one could surely speed-up several tests and make the test-suite fewer expensive). If the costs means the fossil2git process - well, it is also possible to optimize. Just use export- & import-marks on fossil and git side. Then the whole export/import stuff is thousand times faster and generates a lot fewer traffic. The simplest script for the latter looks like this: {fossil export --git --import-marks .git/.fossil2git-fssl --export-marks .git/.fossil2git-fssl.tmp | git fast-import $@ --import-marks=.git/.fossil2git-git --export-marks=.git/.fossil2git-git.tmp } && {mv .git/.fossil2git-fssl.tmp .git/.fossil2git-fssl; mv .git/.fossil2git-git.tmp .git/.fossil2git-git} This would firstly create marks in *.tmp and if gets ready and succeeds would replace last marks from that tmp-state. To do first export creating initial marks state, simply use it without --import-marks ... for both sides, so it'd generate initial export-marks, that can be used by further runs. Besides performance this has additional pros, the important one is - it guarantees persistence of the tree - already processed revisions will be untouched anymore, so the tree remain unchanged, even if fossil, for example after update (as already few times happened), abrupt starts to generate a bit different stream/hash/whatever by some revision, so causing a tree rebuilt without marks from that ancestor. $@ in git args allows to supply additional arguments, e. g. --force to overwrite branches/tags like mistake (which are non unique on fossil). By the way, if this marks become public, everyone can use them to push it to GH from local repository (whole diff or single branch). Hope this helps, Serg. 21.08.2024 19:36, Brian Griffin wrote: > From what I recall, it is limited due to cost. > > My development process uses a MacBookPro, running two virtual machines, Linux and Windows 10. The source files are shared from the mac file system. I run only one at a time for performance reasons. Once done, I feel confident checking in. > > -Brian > (from mobile device) > >> On Aug 21, 2024, at 12:05, apnmbx-public--- via Tcl-Core <tcl...@li...> wrote: > >> Would if be possible to increase the frequency of github pushes (and correspondingly the action runs) to at least twice a day? >> >> I find the turnaround time to ensure commits work on all platforms before merging into trunk to be an impendiment. By the time Github actions verify the branch, the trunk has often moved on significantly. >> >> Of course, an alternative would be to commit to trunk after local verification on one platform for one build type 😊 >> >> /Ashok _______________________________________________ >> 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 [1] Links: ------ [1] https://lists.sourceforge.net/lists/listinfo/tcl-core |