[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <BN0P110MB2067885EE6266EE45CEEDD46F3D3A@BN0P110MB2067.NAMP110.PROD.OUTLOOK.COM>
Date: Wed, 5 Aug 2026 14:03:40 +0000
From: "Weber (US), Matthew L" <matthew.l.weber3@...ing.com>
To: "musl@...ts.openwall.com" <musl@...ts.openwall.com>,
Szabolcs Nagy
<nsz@...t70.net>
CC: "Shotwell (US), Clayton" <clayton.shotwell@...ing.com>
Subject: RE: RE: [EXTERNAL] Re: [PATCH 1/3 libc-test]
functional:time:clock_nanosleep test
> -----Original Message-----
> From: Szabolcs Nagy <nsz@...t70.net>
> Sent: Wednesday, December 4, 2024 3:43 PM
> To: Ward, Ryan C <ryan.c.ward3@...ing.com>
> Cc: musl@...ts.openwall.com
> Subject: Re: [musl] RE: [EXTERNAL] Re: [musl] [PATCH 1/3 libc-test] functional:time:clock_nanosleep test
>
[snip]
> > EXT email: be mindful of links/attachments.
> > > Gardner, Ryan P <ryan.p.gardner@...ing.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.
> >
> > Hi, we have now pushed some scripts we have used during development to
> > to our external staging branch, located here:
> >
> > https://github.com/Boeing/libc-test/tree/boeing-staging-next-libc-test
> > /rfc/rfc_add_testing_scripts
> >
> thanks for doing this.
> fyi i'm travelling and my laptop got stolen.
>
> will be able to recover. but it will take a while.
> the integrity of the repo is not in danger.
Hi, I finally got back to looking at the additional pending patches on our fork as part of adding a Buildroot runtime test that uses the libc-test package to check MUSL and GLIBC. In that submission I'll have a single patch that you could apply with all the latest (rebase/fixed up) test cases.
Is there anything I should consider as I do this? I'll send a patchwork link once things are sent.
Regards,
Matt
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
