I am not.
On 2024-04-22 01:46, Christophe Lyon wrote: > Hi Pedro, > > As you may have noticed, this patch caused new failures on arm. > Are you working on a fix? > > Thanks, > > Christophe > > On Sat, 13 Apr 2024 at 16:59, <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-1198 >> , 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-2094-gc223d373883 >> | Author: Pedro Alves <pe...@palves.net> >> | Date: Tue May 2 15:04:28 2023 +0100 >> | >> | Fix setting watchpoints when current thread is running >> | >> | Currently, when the current thread is running, you can print global >> | variables. However, if you try to set a watchpoint on the same >> | globals, GDB errors out, complaining that the selected thread is >> | running. Like so: >> | >> | ... 37 lines of the commit log omitted. >> >> FAIL: 5 regressions >> >> regressions.sum: >> === gdb tests === >> >> Running gdb:gdb.base/watchpoint-running.exp ... >> FAIL: gdb.base/watchpoint-running.exp: all-stop: hardware: watch global_var >> FAIL: gdb.base/watchpoint-running.exp: all-stop: hardware: watchpoint hit >> (timeout) >> FAIL: gdb.base/watchpoint-running.exp: non-stop: hardware: watch global_var >> FAIL: gdb.base/watchpoint-running.exp: non-stop: hardware: watchpoint hit >> (timeout) >> >> Running gdb:gdb.threads/signal-command-handle-nopass.exp ... >> FAIL: gdb.threads/signal-command-handle-nopass.exp: step-over no: signal >> SIGUSR1 >> ... and 1 more entries >> >> You can find the failure logs in *.log.1.xz files in >> - >> https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/1050/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/1050/artifact/artifacts/notify/ >> The list of [ignored] baseline and flaky failures are in >> - >> https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/1050/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/1050/artifact/artifacts >> Reference build : >> https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/1047/artifact/artifacts >> >> Reproduce last good and first bad builds: >> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/c223d3738832011ced54e8415fa218934aebd0e4/tcwg_gdb_check/master-arm/reproduction_instructions.txt >> >> Full commit : >> https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=c223d3738832011ced54e8415fa218934aebd0e4 >> >> List of configurations that regressed due to this commit : >> * tcwg_gdb_check >> ** master-arm >> *** FAIL: 5 regressions >> *** >> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/c223d3738832011ced54e8415fa218934aebd0e4/tcwg_gdb_check/master-arm/details.txt >> *** >> https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/1050/artifact/artifacts > _______________________________________________ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
