On 06/05/2025 1:33 am, Bill Allombert wrote:
On Tue, May 06, 2025 at 01:12:43AM +0530, Pirate Praveen wrote:I think we have to consider test target in rules differently from build targets as the effect on these on the final binaries we ship is different.I agree the current policy fit well when applied to the build target. As we don't want to ship anything not present / built from the source package. But anything runs in the test target does not affect the final binaries. The only difference that makes is more functionalities are tested. Because of the current policy we are unable to test any functionality that needs an internet connection. So I think the current policy is hiding potential problems that could be discovered early if these tests are actually run during build.That assumes that the buildd operators are willing to let your tests run with network access.
buildds don't need to allow it, only salsa ci and debci need to allow it.
autopkgtest has an option to allow network access, so you can use that. If you need the test to be performed as part of the build, propose a new DEB_BUILD_OPTION 'allownetworktest' and make your tests conditional on that.
that is a good idea so this could be enabled on salsa ci for example.
Cheers,
OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
