Hi, Norbert Preining <norb...@preining.info> writes:
> I would like to collect opinions concerning Salsa CI testing: > > I contemplate disabling the whole salsa-ci for now, since all tests > always fail, and we only take a lot of computing power for tests > that nobody looks into, and hundreds of emails. > > I have no intention to fix the salsa-ci stuff, so I would like to > disable it. > > If someone wants to work on getting the CI testing working again, we can > reenable it again. > > What do you think? > I agree 100% and second this motion. It's also worth mentioning that unused and unmaintained CI runs waste electricity, electricity has a carbon footprint, and thus unused and unmaintained CI contributes nothing--except to global warming and associated natural disasters. It's also a problem if all tests need to be updated for every release, because that means that uploads of new releases will stall until a hypothetical volunteer for CI work fixes the tests...if we use CI as a "ready for upload" indicator. If we're not using it for that, then it's a waste of electricity. I'm also concerned that the situation is fundamentally wrong: If tests need to be updated with every new release, something is wrong with the tests, or the infrastructure... Tests and infrastructure are supposed to be the controls that enable meaningful results when testing for correct functionality in the face of changes. eg: Imho, changing the tests or infrastructure for every new release is bad methodology that does not provide meaningful results. Regards, Nicholas
signature.asc
Description: PGP signature
