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 <ar...@redhat.com>
>  | 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

Reply via email to