user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: "Štěpán Němec" <stepnem@smrk.net>
Cc: meta@public-inbox.org
Subject: Re: imapd.t failing on OpenBSD, bisects to 13a2088c74fd (kqnotify: drop EV_CLEAR (edge triggering))
Date: Wed, 18 Oct 2023 21:23:18 +0000	[thread overview]
Message-ID: <20231018212319.M51504@dcvr> (raw)
In-Reply-To: <20231018211801+0200.254938-stepnem@smrk.net>

Štěpán Němec <stepnem@smrk.net> wrote:
> Hm, thanks.  I've been only using, 'make test' and prove
> (no -j) so far, so that's not it.

Alright, I've reverted it and reinstated EV_CLEAR use
(commit cbb4498df289f9874fc9475b86310958826360e8).

In my experience, EV_CLEAR and EPOLLET tend to exacerbate
sporadic problems like these, not cause them...

Though I am curious if it's a red herring or not...  If you have
spare cycles to test on 7.3 or 7.4, it'd be greatly appreciated
(but no obligations to do so)

I know there is some wonkiness in signal handling in NetReader +
(Mail::IMAPClient|Net::NNTP) code that needs to be resolved.
NetBSD had sporadic failures with EINTR in tests which needs to
be fixed.  But I also don't know why it'd even see EINTR on
some tests...

AFAIK none of these problems affected FreeBSD.  I test and do
occasional development on FreeBSD significantly more than the
other BSDs, though.

  reply	other threads:[~2023-10-18 21:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 15:01 imapd.t failing on OpenBSD, bisects to 13a2088c74fd (kqnotify: drop EV_CLEAR (edge triggering)) Štěpán Němec
2023-10-18 19:06 ` Eric Wong
2023-10-18 19:18   ` Štěpán Němec
2023-10-18 21:23     ` Eric Wong [this message]
2023-10-19  8:43       ` Štěpán Němec
2023-10-23 19:58         ` Eric Wong
2023-11-27 11:20           ` OpenBSD debugging Štěpán Němec
2023-11-29 22:38             ` Eric Wong

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=20231018212319.M51504@dcvr \
    --to=e@80x24.org \
    --cc=meta@public-inbox.org \
    --cc=stepnem@smrk.net \
    /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).