We have recently added a new test to t7900 that exercises whether git-maintenance(1) fails as expected when the "schedule.lock" file exists. The test depends on whether or not the host has the required executables present to schedule maintenance tasks in the first place, like systemd or launchctl -- if not, the test fails with an unrelated error before even checking for the lock file. This fails for example in our CI systems, where macOS images do not have launchctl available. Fix this issue by creating a stub systemctl(1) binary and using the systemd scheduler. Reported-by: Jeff King <peff@xxxxxxxx> Signed-off-by: Patrick Steinhardt <ps@xxxxxx> --- Oh, true, thanks for reporting. This here should fix it. Patrick t/t7900-maintenance.sh | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/t/t7900-maintenance.sh b/t/t7900-maintenance.sh index 6d6ffaaf37..4bbc171958 100755 --- a/t/t7900-maintenance.sh +++ b/t/t7900-maintenance.sh @@ -1012,10 +1012,15 @@ test_expect_success 'repacking loose objects is quiet' ' ' test_expect_success 'maintenance aborts with existing lock file' ' - test_when_finished "rm -rf repo" && + test_when_finished "rm -rf repo script" && + mkdir script && + write_script script/systemctl <<-\EOF && + true + EOF + git init repo && : >repo/.git/objects/schedule.lock && - test_must_fail git -C repo maintenance start 2>err && + test_must_fail env PATH="$PWD/script:$PATH" git -C repo maintenance start --scheduler=systemd 2>err && test_grep "Another scheduled git-maintenance(1) process seems to be running" err ' base-commit: 2f2daa412d02135a1f1f00da3f424217467f8d16 -- 2.47.0.274.g962d0b743d.dirty
