From 0faddbbfecaa784c584d3a625628c288fe9316c7 Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Fri, 31 Jul 2020 21:36:18 +0000 Subject: improve error handling on import fork / lock failures v?fork failures seems to be the cause of locks not getting released in -watch. Ensure lock release doesn't get skipped in ->done for both v1 and v2 inboxes. We also need to do everything we can to ensure DB handles, pipes and processes get released even in the face of failure. While we're at it, make failures around `git update-server-info' non-fatal, since smart HTTP seems more popular anyways. v2 changes: - spawn: show failing command - ensure waitpid is synchronous for inotify events - teardown all fast-import processes on exception, not just the failing one - beef up lock_release error handling - release lock on fast-import spawn failure --- t/psgi_search.t | 1 + 1 file changed, 1 insertion(+) (limited to 't/psgi_search.t') diff --git a/t/psgi_search.t b/t/psgi_search.t index 64f8b1ac..2d12ba6a 100644 --- a/t/psgi_search.t +++ b/t/psgi_search.t @@ -14,6 +14,7 @@ my @mods = qw(DBD::SQLite Search::Xapian HTTP::Request::Common Plack::Test require_mods(@mods); use_ok($_) for (qw(HTTP::Request::Common Plack::Test)); use_ok 'PublicInbox::WWW'; +use_ok 'PublicInbox::SearchIdx'; my ($tmpdir, $for_destroy) = tmpdir(); my $ibx = PublicInbox::Inbox->new({ -- cgit v1.2.3-24-ge0c7