public inbox for developer@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
From: Ryan Zezeski <ryan@zinascii.com>
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] Review: 13918 Want kernel test facility (IPD 20)
Date: Fri, 24 Feb 2023 10:18:50 -0700	[thread overview]
Message-ID: <m2o7pjkman.fsf@zinascii.com> (raw)
In-Reply-To: <m2mtqwt9o8.fsf@zinascii.com>


Almost two years later and I finally got around to addressing CR. I am
sorry for such an extreme delay.

Coming back to this with fresh eyes gave me a new perspective on some
aspects of the implementation. I think it's now a bit simpler. I also
added man pages for the command and kernel APIs. I have a more thorough
list in the CR comments. Speaking of the CR, given the length of time
between updates the diff view seems very confused if you diff patchset
#1 and #3. I'm happy to create an entirely new CR if that's desired.

There's certainly still rough spots in places, but I thought that's
where the list could help me out. I'd like to get the initial version in
that is "good enough" so that this is no longer something just sitting
on a branch and others can improve on it without waiting for my slow
ass.

I also updated the IPD to reflect the changes I've made in the
implementation.

CR: https://code.illumos.org/c/illumos-gate/+/1585
Ticket: https://www.illumos.org/issues/13918
IPD: https://github.com/illumos/ipd/blob/master/ipd/0020/README.adoc

-Ryan

Ryan Zezeski <ryan@zinascii.com> writes:

> I would appreciate anyone who can look at my proposed implementation of
> the Kernel Test Facility (aka ktest), as described in IPD 20. I would
> have liked to include more tests out of the gate, but honestly I think
> this chunk of work is already large enough as it is, and there are those
> who would have made use of ktest a year ago had it been ready. I also
> left a few TODOs in there, all of which I feel would be best done as
> follow-up changes.
>
> CR: https://code.illumos.org/c/illumos-gate/+/1585
> Ticket: https://www.illumos.org/issues/13918
> IPD: https://github.com/illumos/ipd/blob/master/ipd/0020/README.adoc
>
> -Ryan
>
> ------------------------------------------
> illumos: illumos-developer
> Permalink: https://illumos.topicbox.com/groups/developer/T95078dcc9ecf4b91-M04f4542d95a640830ced6d9b
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription


  reply	other threads:[~2023-02-24 17:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-09  4:04 Ryan Zezeski
2023-02-24 17:18 ` Ryan Zezeski [this message]
2024-02-05  4:03   ` [developer] " Ryan Zezeski
2024-02-15  5:38     ` Robert Mustacchi
2024-07-14 17:24     ` Ryan Zezeski

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2o7pjkman.fsf@zinascii.com \
    --to=ryan@zinascii.com \
    --cc=developer@lists.illumos.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 NNTP newsgroup(s).