Thanks, Christian and Hakan! It's a good idea to keep the automatic tests to a useful minimum, at least for the time being. Cheers, Michael On 24.08.2022 11:26, Hakan Bayındır wrote:
Hi Christian,
Let me take a look at it. I’ll let you know if I can make progress on that.
Cheers,
Hakan
On 24 Aug 2022, at 12:24, c.buhtz@posteo.jp wrote:
Hello,
does anyone of you have experience with the continuous integration system "Travis" used by GitHub? If so it would be great if you could modify the configuration and offer this as an PR.
I assume this is the relevant configuration file for that: https://github.com/bit-team/backintime/blob/master/.travis.yml The file seems quit easy but I don't want to mess around with it if there is someone with a bit more experience.
I would like to remove the "python-nightly" from the tests. It seems interesting to know how the BiT code works with the next Python version. But currently we don't have resources for that and problems there are not urgent. We always should test the code manually when a new release candidate comes out. This is IMHO enough. Python 3.10 is fresh out and will stay for some times. Let's concentrate on more urgent problems.
Doing this automatically distracts the users offering PRs and often gets red travis errors. As an example: https://github.com/bit-team/backintime/pull/1274/checks?check_run_id=7981781... The problem here is that BiT use the deprecated `unittest.TestCase.assertEquals()` with an 's' at the end instead of the without the 's' at the end. No big deal and not relevant for the code that was changed by the PR. The user invested time do offer us a PR so we should give him the damn good feeling of green test indicators. ;)
So please someone remove "python-nightly". Also "python3.9-dev" isn't needed anymore because 3.9 is stable. Current is 3.9.13 and maybe there will come a 3.9.14 someday but the modifications shouldn't break our builds. So no need to check a dev/rc/pre version here.
And why does python 3.6 and 3.10 are happens two times here? https://github.com/bit-team/backintime/pull/1274/checks?check_run_id=7981781...
Is there a good reason for this or can we drop this and reduce resources (time, energy and CO2) on the GitHub server?
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: hakan@bayindir.org
_______________________________________________ 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