user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
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:16:53 +0000	[thread overview]
Message-ID: <20231114221653.M550291@dcvr> (raw)
In-Reply-To: <20231114-idealistic-marvellous-dove-dd143e@nitro>

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...

  reply	other threads:[~2023-11-14 22:16 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 [this message]
2023-11-14 22:30   ` Konstantin Ryabitsev
2023-11-14 22:46     ` Eric Wong
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: http://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=20231114221653.M550291@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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).