From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.0 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: from second.openwall.net (second.openwall.net [193.110.157.125]) by inbox.vuxu.org (Postfix) with SMTP id E96A024BF8 for ; Sun, 10 Nov 2024 12:45:41 +0100 (CET) Received: (qmail 7332 invoked by uid 550); 10 Nov 2024 11:45:37 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com x-ms-reactions: disallow Received: (qmail 7297 invoked from network); 10 Nov 2024 11:45:36 -0000 Date: Sun, 10 Nov 2024 12:45:27 +0100 From: Szabolcs Nagy To: "Gardner, Ryan P" Cc: "musl@lists.openwall.com" Message-ID: <20241110114527.GK2724612@port70.net> Mail-Followup-To: "Gardner, Ryan P" , "musl@lists.openwall.com" References: <88f3122170794590afdbeb4d86d394f9@boeing.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <88f3122170794590afdbeb4d86d394f9@boeing.com> Subject: Re: [musl] [PATCH 1/3 libc-test] functional:time:clock_nanosleep test * Gardner, Ryan P [2024-11-07 04:39:59 +0000]: > Szabolcs Nagy 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