On Mon, 05 May 2025 14:53:27 -0600 Sam Hartman <hartm...@debian.org> wrote:
I think we absolutely do not want a failure in an external service to cause a package to FTBFS either on buildds or for individual users. Ideally we would replicate the network side of a test and run against a mocked component. When that is not done (it's a lot of work), I would much rather disable tests than introduce fragility by having tests that can sometimes fail when an external service is down.
I also believe the privacy exposure of having code contact external services is great enough that we should disable tests by default rather than accept that exposure.
ok so the risks out weigh the benefit here to be run by default.
I agree with the option of creating a build option to allow network access for tests if there are tests you would find useful to run say from salsa-ci.
I have opened https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104764 for this.
OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
