From bca19d74e8819672ad121fd4cb74eb27088d0bdf Mon Sep 17 00:00:00 2001 From: Jonathan Lebon Date: Tue, 14 Apr 2020 16:44:04 -0400 Subject: [PATCH] tests/compose: Don't use lockfiles by default Otherwise, it muddles testing in `test-lockfile.sh` where we want to be in full control of all the lockfiles fed to `rpm-ostree compose tree`. --- tests/compose/libcomposetest.sh | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/tests/compose/libcomposetest.sh b/tests/compose/libcomposetest.sh index 39e7cb9a..555570f6 100644 --- a/tests/compose/libcomposetest.sh +++ b/tests/compose/libcomposetest.sh @@ -60,9 +60,7 @@ else: export compose_base_argv="\ --unified-core \ --repo=${repo} \ - --cachedir=${test_tmpdir}/cache \ - --ex-lockfile=config/manifest-lock.x86_64.json \ - --ex-lockfile=config/manifest-lock.overrides.x86_64.yaml" + --cachedir=${test_tmpdir}/cache" # and create this now for tests which only use `compose_base_argv` mkdir -p cache