Since the entire upstream test suite was added in autopkgtests, I haven't seen `repo.aptly.info` being flaky or unreliable, which is obviously what triggered both the failures you reported.
I'll keep an eye out for future failures, but at this point I don't think there is value in the tradeoff of disabling every single test touching the remote repo. I'm happy to keep this bug opened, adding to it when there are more features, or you can close it and I'll track future regressions in new, more specific bugreports. Cheers, -- Seb
