> -----Original Message----- > From: sundeep.kokkonda@gmail.com > Sent: 08 July 2022 10:20 > To: 'Adhemerval Zanella' > Cc: 'Libc-help' > Subject: RE: glibc test procedure needed > > > > > -----Original Message----- > > From: Adhemerval Zanella > > Sent: 05 July 2022 18:13 > > To: sundeep.kokkonda@gmail.com > > Cc: Libc-help > > Subject: Re: glibc test procedure needed > > > > > > > > > On 5 Jul 2022, at 03:09, sundeep.kokkonda--- via Libc-alpha > alpha@sourceware.org> wrote: > > > > > > Hello, > > > > > > > > > > > > I need some info on glibc testing. > > > > > > > > > > > > In the Yocto project we're updating glibc frequently and so we need > > > to ensure the updated glibc is not introduced any issues, by > > > performing the testing. > > > > > > Can you let me know how can I test glibc? Is there any standardized > > > test procedure available to do full test/regression test? > > > > > > > The usual ‘make check’ should cover all the required testing, you > > might need to use ‘run-built-tests=yes’ additional directive if you > > are cross-compiling to force the make to issues the built tests (for > > instance on architecture that support multiple ABI, like x86, or to force the use > of some emulation like qemu-user). > > > > We are still fixing up some clunky tests and there are some broken > > environment (for instance broken syscall filtering) where some tests might > advertise a failure. > > Hello, > > I tried with 'Testing with a cross-compiler' method and test is aborted when the > flag '-Wformat-security' is enabled. When this flag is removed the test is > executed successfully. Is it a known issue? (The error log make-check.out is > attached for reference) Also, can anyone share the list of known test failures (if > any). > Hello, Can I get some info regarding my query. > > Thanks, > Sundeep K.