Re: [Linaro-TCWG-CI] glibc-2.38.9000-528-g6bd0e4efcc: FAIL: 1 regressions on arm
Hi Arjun, This is not a real regression. We have a problem in our CI that causes container tests fail for 32-bit ARM. Therefore, any new container test shows up as a regression. We are working on fixing this. Thanks, -- Maxim Kuvyrkov https://www.linaro.org > On Jan 31, 2024, at 06:42, ci_not...@linaro.org wrote: > > Dear contributor, our automatic CI has detected problems related to your > patch(es). Please find some details below. If you have any questions, > please follow up on linaro-toolchain@lists.linaro.org mailing list, Libera's > #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on > the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or > reproduce the issue locally. If you can't get what you need from our CI > within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1138 , > please let us know if you are looking at the problem and/or when you have a > fix. > > In glibc_check master-arm after: > > | commit glibc-2.38.9000-528-g6bd0e4efcc > | Author: Arjun Shankar > | Date: Mon Jan 15 17:44:43 2024 +0100 > | > | syslog: Fix heap buffer overflow in __vsyslog_internal (CVE-2023-6246) > | > | __vsyslog_internal did not handle a case where printing a SYSLOG_HEADER > | containing a long program name failed to update the required buffer > | size, leading to the allocation and overflow of a too-small buffer on > | the heap. This commit fixes that. It also adds a new regression test > | that uses glibc.malloc.check. > | ... 4 lines of the commit log omitted. > > FAIL: 1 regressions > > regressions.sum: > === glibc tests === > > Running glibc:misc ... > FAIL: misc/tst-syslog-long-progname > > > You can find the failure logs in *.log.1.xz files in > - > https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/892/artifact/artifacts/00-sumfiles/ > The full lists of regressions and progressions as well as configure and make > commands are in > - > https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/892/artifact/artifacts/notify/ > The list of [ignored] baseline and flaky failures are in > - > https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/892/artifact/artifacts/sumfiles/xfails.xfail > > The configuration of this build is: > CI config tcwg_glibc_check master-arm > > -8<--8<--8<-- > The information below can be used to reproduce a debug environment: > > Current build : > https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/892/artifact/artifacts > Reference build : > https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/890/artifact/artifacts > > Reproduce last good and first bad builds: > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/sha1/6bd0e4efcc78f3c0115e5ea9739a1642807450da/tcwg_glibc_check/master-arm/reproduction_instructions.txt > > Full commit : > https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=6bd0e4efcc78f3c0115e5ea9739a1642807450da > > List of configurations that regressed due to this commit : > * tcwg_glibc_check > ** master-arm > *** FAIL: 1 regressions > *** > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/sha1/6bd0e4efcc78f3c0115e5ea9739a1642807450da/tcwg_glibc_check/master-arm/details.txt > *** > https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/892/artifact/artifacts ___ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
Re: [Linaro-TCWG-CI] gcc patch #85019: FAIL: 29 regressions on aarch64
On Tue, Jan 30, 2024 at 5:45 PM wrote: > > Dear contributor, our automatic CI has detected problems related to your > patch(es). Please find some details below. If you have any questions, > please follow up on linaro-toolchain@lists.linaro.org mailing list, Libera's > #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on > the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or > reproduce the issue locally. If you can't get what you need from our CI > within minutes, let us know and we will be happy to help. > > In gcc_check master-aarch64 after: > > | gcc patch https://patchwork.sourceware.org/patch/85019 > | Author: H.J. Lu > | Date: Tue Jan 30 04:56:44 2024 -0800 > | > | Handle private COMDAT function symbol reference in readonly data > section > | > | For a private COMDAT function symbol reference in readonly data > section, > | instead of putting it in .data.rel.ro or .rodata.cst section, call > | function_rodata_section to get the read-only or relocated read-only > | data section associated with the function DECL so that the COMDAT > | section will be used for the private COMDAT function symbol. > | ... 14 lines of the commit log omitted. > | ... applied on top of baseline commit: > | f2061b2a964 c++: avoid -Wdangling-reference for std::span-like classes > [PR110358] > > FAIL: 29 regressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.c-torture/execute/execute.exp ... > FAIL: gcc.c-torture/execute/pr79286.c -Os (internal compiler error: > Segmentation fault) > FAIL: gcc.c-torture/execute/pr79286.c -Os (test for excess errors) > UNRESOLVED: gcc.c-torture/execute/pr79286.c -Os compilation failed to > produce executable > > Running gcc:gcc.dg/torture/dg-torture.exp ... > FAIL: gcc.dg/torture/pr67109.c -O3 -fomit-frame-pointer -funroll-loops > -fpeel-loops -ftracer -finline-functions (internal compiler error: > Segmentation fault) > FAIL: gcc.dg/torture/pr67109.c -O3 -fomit-frame-pointer -funroll-loops > -fpeel-loops -ftracer -finline-functions (test for excess errors) > ... and 25 more entries I can't reproduce it with a cross compiler on x86-64 configured with --target=aarch64-linux But I sent out the v2 patch: https://patchwork.sourceware.org/project/gcc/list/?series=30393 to check decl non-null before dereferencing it. -- H.J. ___ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
Re: [Linaro-TCWG-CI] gdb-14-branchpoint-1426-gb960445a459: FAIL: 1 regressions on arm
Hi All, This is a false positive, obviously. We do our best to filter out flaky tests, but in this case "gdb.threads/staticthreads.exp: up 10" PASSed twice in the previous run, and then FAILed twice in the next run. Sneaky! Re. the FAIL, the testcase expects to be " in main .*" after "up 10", but ends up in pthread_join() instead: === up 10 #4 0x0001b864 in pthread_join () (gdb) FAIL: gdb.threads/staticthreads.exp: up 10 === See [1] for details. [1] https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/artifacts/00-sumfiles/gdb.log.1.xz . Hi Thiago, Would you please investigate whether ending up in pthread_join() is expected/reasonable for 32-bit ARM? In other words, whether we have a GDB bug exposed by staticthreads.exp or the testcase needs to be generalized a bit. Thank you, -- Maxim Kuvyrkov https://www.linaro.org > On Jan 31, 2024, at 01:30, ci_not...@linaro.org wrote: > > Dear contributor, our automatic CI has detected problems related to your > patch(es). Please find some details below. If you have any questions, > please follow up on linaro-toolchain@lists.linaro.org mailing list, Libera's > #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on > the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or > reproduce the issue locally. If you can't get what you need from our CI > within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1137 , > please let us know if you are looking at the problem and/or when you have a > fix. > > In gdb_check master-arm after: > > | commit gdb-14-branchpoint-1426-gb960445a459 > | Author: GDB Administrator > | Date: Tue Jan 30 00:00:26 2024 + > | > | Automatic date update in version.in > > FAIL: 1 regressions > > regressions.sum: > === gdb tests === > > Running gdb:gdb.threads/staticthreads.exp ... > FAIL: gdb.threads/staticthreads.exp: up 10 > > > You can find the failure logs in *.log.1.xz files in > - > https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/artifacts/00-sumfiles/ > The full lists of regressions and progressions as well as configure and make > commands are in > - > https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/artifacts/notify/ > The list of [ignored] baseline and flaky failures are in > - > https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/artifacts/sumfiles/xfails.xfail > > The configuration of this build is: > CI config tcwg_gdb_check master-arm > > -8<--8<--8<-- > The information below can be used to reproduce a debug environment: > > Current build : > https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/artifacts > Reference build : > https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/751/artifact/artifacts > > Reproduce last good and first bad builds: > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/b960445a45981873c5b1718824ea9d3b5749433a/tcwg_gdb_check/master-arm/reproduction_instructions.txt > > Full commit : > https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=b960445a45981873c5b1718824ea9d3b5749433a > > List of configurations that regressed due to this commit : > * tcwg_gdb_check > ** master-arm > *** FAIL: 1 regressions > *** > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/b960445a45981873c5b1718824ea9d3b5749433a/tcwg_gdb_check/master-arm/details.txt > *** > https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/752/artifact/artifacts ___ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
[Linaro-TCWG-CI] glibc-2.38.9000-528-g6bd0e4efcc: FAIL: 1 regressions on arm
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain@lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. We track this report status in https://linaro.atlassian.net/browse/GNU-1138 , please let us know if you are looking at the problem and/or when you have a fix. In glibc_check master-arm after: | commit glibc-2.38.9000-528-g6bd0e4efcc | Author: Arjun Shankar | Date: Mon Jan 15 17:44:43 2024 +0100 | | syslog: Fix heap buffer overflow in __vsyslog_internal (CVE-2023-6246) | | __vsyslog_internal did not handle a case where printing a SYSLOG_HEADER | containing a long program name failed to update the required buffer | size, leading to the allocation and overflow of a too-small buffer on | the heap. This commit fixes that. It also adds a new regression test | that uses glibc.malloc.check. | ... 4 lines of the commit log omitted. FAIL: 1 regressions regressions.sum: === glibc tests === Running glibc:misc ... FAIL: misc/tst-syslog-long-progname You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/892/artifact/artifacts/00-sumfiles/ The full lists of regressions and progressions as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/892/artifact/artifacts/notify/ The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/892/artifact/artifacts/sumfiles/xfails.xfail The configuration of this build is: CI config tcwg_glibc_check master-arm -8<--8<--8<-- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/892/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/890/artifact/artifacts Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/sha1/6bd0e4efcc78f3c0115e5ea9739a1642807450da/tcwg_glibc_check/master-arm/reproduction_instructions.txt Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=6bd0e4efcc78f3c0115e5ea9739a1642807450da List of configurations that regressed due to this commit : * tcwg_glibc_check ** master-arm *** FAIL: 1 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/sha1/6bd0e4efcc78f3c0115e5ea9739a1642807450da/tcwg_glibc_check/master-arm/details.txt *** https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/892/artifact/artifacts ___ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
