From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: t/cindex.t "associate w/o search" test hangs for me
Date: Tue, 14 Nov 2023 20:43:33 -0500 [thread overview]
Message-ID: <20231114-proficient-able-collie-9aa5c0@nitro> (raw)
In-Reply-To: <20231115010642.M607610@dcvr>
On Wed, Nov 15, 2023 at 01:06:42AM +0000, Eric Wong wrote:
> Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> > Looks like the last time I am able to successfully run "make test" is before
> > this commit:
> >
> > b231d91f42d791becf7b6861e723833d71e73237 is the first bad commit
> >
> > The error I start getting after this commit is:
> >
> > t/extsearch.t ................ 160/?
> > # Failed test 'lei_err=unindexed extindex /tmp/pi-extsearch-12765-FmsY/extindex not supported
> > #
> > # Argument "-TERM" isn't numeric in kill at /home/mricon/public-inbox-test/blib/lib/PublicInbox/IPC.pm line 442.
>
> Thanks, that (and another bug) should be fixed with:
> https://public-inbox.org/meta/20231115010457.1047199-1-e@80x24.org/
Thanks, that is indeed much better! But I still get a few errors.
First a non-critical:
t/gcf2_client.t .............. 1/? Can't locate object method "fail" via package "PublicInbox::Gcf2Client" at /home/mricon/public-inbox-test/blib/lib/PublicInbox/Git.pm line 269.
(in cleanup) Can't locate object method "fail" via package "PublicInbox::Gcf2Client" at /home/mricon/public-inbox-test/blib/lib/PublicInbox/Git.pm line 269.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 65280 just after 2.
t/gcf2_client.t .............. Dubious, test returned 255 (wstat 65280, 0xff00)
Then just a bit later this one:
t/imapd.t .................... 2/? Bailout called. Further testing stopped: FETCH socket closed while reading data from server
FAILED--Further testing stopped: FETCH socket closed while reading data from server
make: *** [test_dynamic] Error 255
This one looks odd but I do see it happen every time I run the test.
-K
next prev parent reply other threads:[~2023-11-15 1:43 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
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 [this message]
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=20231114-proficient-able-collie-9aa5c0@nitro \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.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).