mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: "Gardner, Ryan P" <ryan.p.gardner@boeing.com>
Cc: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: Re: [musl] [PATCH 1/3 libc-test] functional:time:clock_nanosleep test
Date: Sun, 10 Nov 2024 12:45:27 +0100	[thread overview]
Message-ID: <20241110114527.GK2724612@port70.net> (raw)
In-Reply-To: <88f3122170794590afdbeb4d86d394f9@boeing.com>

* Gardner, Ryan P <ryan.p.gardner@boeing.com> [2024-11-07 04:39:59 +0000]:
> Szabolcs Nagy <nsz@...t70.net> writes:
> 
> > thanks
> > patches look good. but it will take a week or two
> > for me to be able to test and apply them.
> 
> Thank you for the quick response. We appreciate your timeline for testing and applying the patches.
> 
> Our plan is to submit tests for the majority of functions that currently lack coverage within libc-test. 
> We already have a significant number of tests written and ready for submission. To avoid overwhelming
> you with patches, do you have a preferred cadence for the submission of these tests?
> 

over the next month im only in front of a computer sporadically

but code style or quality of tests are less strict than for libc,
so i dont expect many iterations. just post the patches so when i
can take a look i can comment or apply them.

btw if there is a repo with a branch i can cherrypick from that
is a bit easier for me than handling mails. then i think you
dont even have to post "obvious" patches to the list. i can pick
them from the branch.

> Additionally, we are planning to setup runtime tests in collaboration with the Buildroot community. This
> would facilitate testing across various embedded configurations and processor architectures. Once up 
> and running, when we submit new test patches we can reference a fork of Buildroot that shows the tests 
> passing on various hardware configurations.

nice.

the infra in libc-test is not amazing for continous tests.
when i get to it i will try to improve it.

> 
> Looking forward to your guidance,
> Ryan Gardner

  reply	other threads:[~2024-11-10 11:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07  4:39 Gardner, Ryan P
2024-11-10 11:45 ` Szabolcs Nagy [this message]
2024-11-13 11:51 ` Szabolcs Nagy
  -- strict thread matches above, loose matches on Subject: below --
2024-11-15  5:16 Gardner, Ryan P
2024-11-05 22:44 Ryan Gardner
2024-11-06  7:38 ` Szabolcs Nagy

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=20241110114527.GK2724612@port70.net \
    --to=nsz@port70.net \
    --cc=musl@lists.openwall.com \
    --cc=ryan.p.gardner@boeing.com \
    /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://git.vuxu.org/mirror/musl/

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