public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
To: tom@tromey.com, Jonathan Wakely <jwakely@redhat.com>
Cc: gdb-testers@sourceware.org,
	Linaro Toolchain Working Group
	<linaro-toolchain@lists.linaro.org>
Subject: Re: [Linaro-TCWG-CI] gdb-14-branchpoint-1411-g033bc67bdb0: FAIL: 2 regressions on arm
Date: Mon, 11 Mar 2024 20:38:02 +0400	[thread overview]
Message-ID: <74C444DC-7CEE-408D-822A-2DD63CF93C32@linaro.org> (raw)
In-Reply-To: <578038658.1014.1706641415312@jenkins.jenkins>

> On Jan 30, 2024, at 23:03, ci_notify@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-1136 , please let us know if you are looking at the problem and/or when you have a fix.
> 
> In  master-arm after:
> 
>  | commit gdb-14-branchpoint-1411-g033bc67bdb0
>  | Author: Tom Tromey <tom@tromey.com>
>  | Date:   Tue Sep 19 17:39:31 2023 -0600
>  | 
>  |     Only search types in cp_lookup_rtti_type
>  |     
>  |     This changes cp_lookup_rtti_type to only search for types -- not
>  |     functions or variables.  Due to the symbol-matching hack, this could
>  |     just use SEARCH_TYPE_DOMAIN, but I think it's better to be clear; also
>  |     I hold on to some hope that perhaps the hack can someday be removed.
> 
> FAIL: 2 regressions
> 
> regressions.sum:
> === libstdc++ tests ===
> 
> Running libstdc++:libstdc++-prettyprinters/prettyprinters.exp ...
> FAIL: libstdc++-prettyprinters/cxx11.cc print ecmiaow
> FAIL: libstdc++-prettyprinters/cxx11.cc print emiaow

Hi Tom,
Hi Jonathan,

After the above GDB patch I see 2 new failures both for aarch64-linux-gnu and arm-linux-gnueabihf in GCC's libstdc++ testsuite.  The log [1] says:
===
$35 = warning: RTTI symbol not found for class 'main::custom_cat'
warning: RTTI symbol not found for class 'main::custom_cat'
got: $35 = warning: RTTI symbol not found for class 'main::custom_cat'
FAIL: libstdc++-prettyprinters/cxx11.cc print emiaow
skipping: warning: RTTI symbol not found for class 'main::custom_cat'
std::error_code = {std::_V2::error_category: 42}
skipping: std::error_code = {std::_V2::error_category: 42}
$36 = warning: RTTI symbol not found for class 'main::custom_cat'
warning: RTTI symbol not found for class 'main::custom_cat'
got: $36 = warning: RTTI symbol not found for class 'main::custom_cat'
FAIL: libstdc++-prettyprinters/cxx11.cc print ecmiaow
===

Which way should I dig -- GDB or libstdc++?  Does this look like libstdc++ testcase needs an update?

[1] https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/lastSuccessfulBuild/artifact/artifacts/00-sumfiles/libstdc++.log.xz 

Thanks!

--
Maxim Kuvyrkov
https://www.linaro.org


> 
> 
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/987/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_gnu_native_check_gcc--master-arm-build/987/artifact/artifacts/notify/
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/987/artifact/artifacts/sumfiles/xfails.xfail
> 
> The configuration of this build is:
> CI config tcwg_gnu_native_check_gcc master-arm
> 
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
> 
> Current build   : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/987/artifact/artifacts
> Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/986/artifact/artifacts
> 
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/033bc67bdb0c74d1c63a1998a7e9679a408ba6e4/tcwg_gnu_native_check_gcc/master-arm/reproduction_instructions.txt
> 
> Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=033bc67bdb0c74d1c63a1998a7e9679a408ba6e4
> 
> List of configurations that regressed due to this commit :
> * tcwg_gnu_native_check_gcc
> ** master-arm
> *** FAIL: 2 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sha1/033bc67bdb0c74d1c63a1998a7e9679a408ba6e4/tcwg_gnu_native_check_gcc/master-arm/details.txt
> *** https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/987/artifact/artifacts



  reply	other threads:[~2024-03-11 16:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 19:03 ci_notify
2024-03-11 16:38 ` Maxim Kuvyrkov [this message]
2024-03-11 16:52   ` Jonathan Wakely
2024-03-13  5:49     ` Maxim Kuvyrkov
2024-03-13 20:53       ` Tom Tromey
2024-03-13 23:57         ` Jonathan Wakely

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=74C444DC-7CEE-408D-822A-2DD63CF93C32@linaro.org \
    --to=maxim.kuvyrkov@linaro.org \
    --cc=gdb-testers@sourceware.org \
    --cc=jwakely@redhat.com \
    --cc=linaro-toolchain@lists.linaro.org \
    --cc=tom@tromey.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).