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: Mon, 23 Oct 2023 19:58:18 +0000	[thread overview]
Message-ID: <20231023195818.M543558@dcvr> (raw)
In-Reply-To: <20231019104320+0200.219147-stepnem@smrk.net>

Štěpán Němec <stepnem@smrk.net> wrote:
> On Wed, 18 Oct 2023 21:23:18 +0000
> Eric Wong wrote:
> 
> > 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 downgraded the VM to 7.3, ran tests (this time updated to
> 848dedde919 (lei: simplify startq/au_done wakeup
> notifications), just with the EV_CLEAR re-removal on top),
> then upgraded to 7.4, ran tests.  I see the same failure
> pattern everywhere, so I really don't think the OpenBSD
> version is a factor here.

Thanks for the info.  Just curious, what HW specs (ncpus, RAM)
is available on that system?  I wonder if that affects timing
somehow...

> (And again, if you want to have a look yourself, I'd be
> happy to give you access to the machine; still the same
> testing OC VM.)

Unfortunately, my *BSD debugging knowledge is far behind my
Linux; so I'm not sure how much help it'd be...

Some examples of things I miss on OpenBSD:

* /proc/$PID/fdinfo/$FD_OF_EPOLL on Linux is immensely helpful
  for knowing what and how epoll is watching target FDs.  I'm
  not sure if there's a way to introspect kqueue like that

* Linux strace decodes more struct args info than kdump

* ability to control pathname of core dumps

... probably a few other things, but been sick a few days and
brain still foggy :<

  reply	other threads:[~2023-10-23 19:59 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
2023-10-19  8:43       ` Štěpán Němec
2023-10-23 19:58         ` Eric Wong [this message]
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=20231023195818.M543558@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).