Test installation of a very large lazily-synced package
Some of the largest packages, such as TensorFlow, can be as large as 340 megabytes in size . Some may even be larger.
If such packages are lazily-synced, and a user tries to install them from Pulp, we should ensure that any delays incurred by Pulp in the process of downloading these packages in the background does not interfere with the operation of the client making the request to Pulp.
A manual test would be acceptable, but an automated test that is not part of the standard CI suite would be better.
Please register to edit this issue