From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: t/cindex.t "associate w/o search" test hangs for me
Date: Tue, 14 Nov 2023 22:46:57 +0000 [thread overview]
Message-ID: <20231114224657.M270072@dcvr> (raw)
In-Reply-To: <20231114-prompt-sage-bobcat-0e6bec@nitro>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Tue, Nov 14, 2023 at 10:16:53PM +0000, Eric Wong wrote:
> > Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> > > └─-cindex -u --al,4432
> > > ├─cidx shard[0],4646
> > > └─cidx shard[1],4647
> > >
> > > Anything I can do to figure out why this is happening?
> >
> > You can show me strace and lsof +E of the processes (any other
> > processes (join|sort|awk|perl)?). This code is highly in flux,
> > so it's also fine to rm the test for now since nothing
> > public-facing is using -cindex, yet...
>
> Yeah, but I figured I'll poke a bit in case it's helpful.
>
> I can't do +E because that's not available to me under CentOS7 (I can't wait
> until we move on, but just when we think the yak is fully shaved, we find more
> clumps of thick fur we hadn't considered). Is the output of the regular "lsof
> -p" helpful at all?
Sure.
> Strace for all three processes (-cindex, cidx shard[0], cidx shard[1]) just
> sits at:
>
> select(24, [13 16], NULL, NULL, NULL
OK, that's still useful. One FD is signalfd, the others would
be a SOCK_SEQPACKET socket, I think...
> As far as I can see, there are no other processes other than cidx.
OK. Hmm.. Perhaps `kill -CHLD' on the top-level cindex process
can move it along? There's still some weird timeout/sleep
behavior leftover from Danga::Socket that should probably be
removed:
-------8<------
Subject: [PATCH] ds: run @post_loop_do if any user-queued events run
---
We can probably kill more hacky wakeup behavior throughout
cindex and maybe other places with this patch...
lib/PublicInbox/DS.pm | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/lib/PublicInbox/DS.pm b/lib/PublicInbox/DS.pm
index da26efc4..4c8b502f 100644
--- a/lib/PublicInbox/DS.pm
+++ b/lib/PublicInbox/DS.pm
@@ -144,13 +144,14 @@ sub next_tick () {
# https://rt.perl.org/Public/Bug/Display.html?id=114340
blessed($obj) ? $obj->event_step : $obj->();
}
+ 1;
}
# runs timers and returns milliseconds for next one, or next event loop
sub RunTimers {
- next_tick();
+ my $ran = next_tick();
- return ($nextq ? 0 : $loop_timeout) unless @Timers;
+ return ($nextq || $ran ? 0 : $loop_timeout) unless @Timers;
my $now = now();
@@ -159,10 +160,11 @@ sub RunTimers {
my $to_run = shift(@Timers);
delete $UniqTimer{$to_run->[1] // ''};
$to_run->[2]->(@$to_run[3..$#$to_run]);
+ $ran = 1;
}
# timers may enqueue into nextq:
- return 0 if $nextq;
+ return 0 if $nextq || $ran;
return $loop_timeout unless @Timers;
next prev parent reply other threads:[~2023-11-14 22:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 21:50 t/cindex.t "associate w/o search" test hangs for me Konstantin Ryabitsev
2023-11-14 22:16 ` Eric Wong
2023-11-14 22:30 ` Konstantin Ryabitsev
2023-11-14 22:46 ` Eric Wong [this message]
2023-11-14 23:05 ` Konstantin Ryabitsev
2023-11-14 23:46 ` Eric Wong
2023-11-14 23:51 ` Konstantin Ryabitsev
2023-11-15 0:07 ` Konstantin Ryabitsev
2023-11-15 1:06 ` Eric Wong
2023-11-15 1:43 ` Konstantin Ryabitsev
2023-11-15 3:09 ` Eric Wong
2023-11-15 13:21 ` Konstantin Ryabitsev
2023-11-15 19:30 ` Eric Wong
2023-11-25 20:43 ` libgit2 [was: Re: t/cindex.t "associate w/o search" test hangs for me] Eric Wong
2023-11-15 1:11 ` t/cindex.t "associate w/o search" test hangs for me Eric Wong
2023-11-15 5:55 ` [PATCH] cindex: fix test when missing time(1) executable Eric Wong
2023-11-15 13:25 ` Konstantin Ryabitsev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231114224657.M270072@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).