Hi, Christian! I agree, every commit pushed to a PR causes quite a cascade of Tavis jobs. To find obvious problems like Syntax errors, one platform is enough. We can do more thorough testing when we get closer to releasing. Cheers, Michael On Wed, Nov 09, 2022 at 10:20:32AM +0000, c.buhtz@posteo.jp wrote:
Hi Folks,
it is just an idea because our credits on TravisCI are free but not unlimited.
Each PR and each new commit on such a PR do create 5 testing jobs (in fact running containers) eating our Travis credits. I propose to deactivate 4 jobs and just keep Python 3.10 on AMD64 as the one and only testing job until we prepare the next release.
For myself I sometimes create PR's against my own forked repo to run TravisCI with my own credits just to be sure.
What do you think? It could spare a lot of credits.
Kind Christian _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: foss@michael-bueker.de