On Thu, Feb 15, 2024 at 2:29 AM Sadineni, Harish via lists.openembedded.org <Harish.Sadineni=windriver....@lists.openembedded.org> wrote: > > Hi all, > > > We are analysing the test failures reported by the autobilder at > https://autobuilder.yocto.io/pub/non-release/20240204-3/testresults/qemux86-64-tc/testresults.json > The autobuilder result summary as follows: > ======================================================================= > qemux86-64 PTest Result Summary > ======================================================================= > ----------------------------------------------------------------------- > Recipe | Passed | Failed | Skipped | > ----------------------------------------------------------------------- > gcc | 124420 | 37 | 23809 | > gcc-g++ | 196231 | 39 | 17314 | > gcc-libatomic | 27 | 1 | 27 | > gcc-libgomp | 3407 | 16 | 1981 | > gcc-libitm | 24 | 1 | 24 > | > gcc-libstdc++-v3 | 9705 | 32 | 5464 | > > > > We started with 'gcc.dg' module failures(13 failues, listed below) reported > in > https://autobuilder.yocto.io/pub/non-release/20240204-3/testresults/testresult-report.txt. > ptestresult.gcc.gcc.dg/analyzer/data-model-4.c (test for excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -O0 (test for > excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -O1 (test for > excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -O2 (test for > excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -O2 -flto > -fno-use-linker-plugin -flto-partition=none (test for excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -O3 -g (test for > excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -Os (test for > excess errors)
torture tests could be due to limited memory ( RAM ). how much RAM is available to qemu ? perhaps try to raise it and see if that helps. > ptestresult.gcc.gcc.dg/pr56837.c scan-tree-dump-times optimized "memset > ..c, 68, 16384.;" 1 > ptestresult.gcc.gcc.dg/vect/vect-ifcvt-18.c scan-tree-dump vect > "vectorized 3 loops" > ptestresult.gcc.gcc.dg/vect/vect-simd-clone-10.c (test for excess errors) > ptestresult.gcc.gcc.dg/vect/vect-simd-clone-16f.c scan-tree-dump-times > vect "[\\n\\r] [^\\n]* = foo\\.simdclone" 2 > ptestresult.gcc.gcc.dg/vect/vect-simd-clone-17f.c scan-tree-dump-times > vect "[\\n\\r] [^\\n]* = foo\\.simdclone" 2 > ptestresult.gcc.gcc.dg/vect/vect-simd-clone-18f.c scan-tree-dump-times > vect "[\\n\\r] [^\\n]* = foo\\.simdclone" 2 > vect-simd-clone depends on avx runtime I think. so maybe thats the issue here. > > > Out of these, except 'gcc.gcc.dg/vect/vect-simd-clone-10.c' all others are > fialed in gcc upstream. > > > We've analyzed the failed case 'vect-simd-clone-10.c' and find the root > cause, it is the bug is in gcc test suite. > > GCC Bug raised - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113899 > > > We are working on other module failures (g++,libatomic...), keep you posted > here. > > > Thanks and Regards, > Harish sadineni > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195691): https://lists.openembedded.org/g/openembedded-core/message/195691 Mute This Topic: https://lists.openembedded.org/mt/104370247/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
