[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: autopkgtest requiring large data sets (pique, hinge)



On 12/21/21 9:00 PM, Pierre Gruet wrote:
On 21/12/2021 14:33, Lance Lin wrote:
Debian Medical Team,

I have started looking at adding autopkgtest suites for a variety of packages. Two of the packages (hinge, pique) require very large data sets to run their included examples. The sizes are several GB.

That's a bit of a problem. Usually very large datasets unless present in tree source itself are hard to manage. Can you try some sort of
compression algorithm on it (converting to .xz etc) and see if you are able to manage the size to few megs?

It also looks like they may be graphical in nature.

Yeah, however sometimes it is possible to manage the graphical tests with xvfb, provided you don't need to explicitly
click buttons on the UI.

Thanks for working on adding tests to the packages. For sure this is always useful!

+1

Is it permissible for autopkgtest suites to download such large amounts of data from the internet? Or should they be included in the repo?

Autopkgtests must be able to run on a minimal system with only the unpacked source tree, the dependencies of the binary packages, and no access to the Internet. This implies that one cannot rely on downloading while running the tests:

No, not really. autopkgtest has a `needs-internet` restriction, so you can access internet to get stuff. See here:

https://people.debian.org/~eriberto/README.package-tests.html

the data that you use have to be included in the installed binary packages or to lie in the source tree.

But yeah, this is usually better, since the server you fetch data from might choke someday, or might turn unresponsive or maybe block IPs if you do several `get` requests to it (which the CI machines would do) and so on,
then that's a problem.
If so, I am happy to continue to look at these packages to include some basic level of testing.

Yes please, making efforts to write tests is definitely worth it. From my experience, you might contact upstream developers to ask them for meaningful commands requiring no more data that the ones that are in the source tree. Friendly upstreams usually <ill try to answer!

I would second that. If possible, ask upstream for sensible data size that is manageable under a few MBs.

Regards,
Nilesh

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


Reply to: