Dear contributor,

Our automatic CI successfully passed with your patch(es). Please find some details below.

In gdb_check master-aarch64, after:
  | 4 patches in gdb
  | Patchwork URL: https://patchwork.sourceware.org/patch/139468
  | b2bfa78f73a [PATCHv7 4/4] gdb: cache program space entry point information
  | d3a1cdfd02f [PATCHv7 3/4] gdb: allow 'until' to work in outermost frame
  | bfe95a0886d [PATCHv7 2/4] gdb: introduce program_space::get_entry_point_info function
  | fa9f7839a6b [PATCHv7 1/4] gdb: rename program_space::entry_point_address* functions
  | ... applied on top of baseline commit:
  | cef1fbf3b02 Change contact details for updating the sourceware crontab entry for the binutils.


Used configuration :
 *CI config* tcwg_gdb_check master-aarch64
 *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu

If you have any questions regarding this report, please ask on linaro-toolchain@lists.linaro.org mailing list.

-----------------8<--------------------------8<--------------------------8<--------------------------

The information below contains the details of the failures, and the ways to reproduce a debug environment:

You can find the failure logs in *.log.1.xz files in
 * http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-aarch64-precommit/builds/10534/archive/artifacts/artifacts.precommit/00-sumfiles/
The full lists of regressions and improvements as well as configure and make commands are in
 * http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-aarch64-precommit/builds/10534/archive/artifacts/artifacts.precommit/notify/
The list of [ignored] baseline and flaky failures are in
 * http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-aarch64-precommit/builds/10534/archive/artifacts/artifacts.precommit/sumfiles/xfails.xfail

Current build   : http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-aarch64-precommit/builds/10534/archive/artifacts/
Reference build : http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-aarch64-build/builds/10349/archive/artifacts/

Warning: we do not enable maintainer-mode nor automatically update
generated files, which may lead to failures if the patch modifies the
master files.