Adam Williamson b8fddfa265 Fix the logic for skipping _repo_setup_updates ... Just checking for the package update list is wrong in a couple of ways: 1. It goes wrong for child tests that inherit the main disk from the parent test, but not the second disk where the actual update repo lives. They'll have the package list, but not the repo. So we should test for both the package list and the repo dir. 2. It goes wrong for side tag tests, because we don't write a package list (or create an update repo) on that path. So on that path let's check whether we already created the repo definition we use on that path. Signed-off-by: Adam Williamson <awilliam@redhat.com>		2024-03-13 10:49:05 -07:00
..
anaconda.pm	Run update repo setup steps from a serial console	2024-01-11 12:09:59 -08:00
anacondatest.pm	Run update repo setup steps from a serial console	2024-01-11 12:09:59 -08:00
bugzilla.pm	Add a perltidy check and apply it to the entire codebase	2022-07-28 14:38:38 -07:00
cockpit.pm	Clean up minimal browser environment setup	2023-03-02 13:51:08 -08:00
disks.pm	disks: drop a workaround we did not hit for a long time	2024-01-09 17:48:28 -08:00
fedoradistribution.pm	Run update repo setup steps from a serial console	2024-01-11 12:09:59 -08:00
freeipa.pm	Add a needle cleanup script, enhance the needle check script	2023-05-04 09:57:15 -07:00
installedtest.pm	Run update repo setup steps from a serial console	2024-01-11 12:09:59 -08:00
modularity.pm	Add a perltidy check and apply it to the entire codebase	2022-07-28 14:38:38 -07:00
packagetest.pm	Run base tests on ELN	2023-06-23 11:53:11 +02:00
tapnet.pm	tapnet: don't double-declare @forwards	2022-05-26 14:49:57 -07:00
utils.pm	Fix the logic for skipping _repo_setup_updates	2024-03-13 10:49:05 -07:00