public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "doko at debian dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/27826] New: 10000 timeouts running the testsuite on arm-linux-gnueabihf Date: Wed, 05 May 2021 10:38:03 +0000 [thread overview] Message-ID: <bug-27826-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27826 Bug ID: 27826 Summary: 10000 timeouts running the testsuite on arm-linux-gnueabihf Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: doko at debian dot org Target Milestone: --- trying to run the testsuite on arm-linux-gnueabihf for 10.2 and trunk 20210502, I see around 10000 test failures, not seen on other architectures using the same build environment (amd64, arm64, i386, ppc64el, s390x) see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 the build environment is binutils 2.36.1, gcc 10.3, glibc 2.33 (updated to the 2.33 branch). the build log show all the test cases which are timing out, there still seems to be at least another running test, as the whole build times out. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-05-05 10:38 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-05 10:38 doko at debian dot org [this message] 2021-05-05 11:54 ` [Bug gdb/27826] " luis.machado at linaro dot org 2021-05-07 12:40 ` luis.machado at linaro dot org 2021-05-07 16:14 ` doko at debian dot org 2021-05-07 20:56 ` luis.machado at linaro dot org 2021-05-07 21:44 ` sergiodj at sergiodj dot net 2022-05-13 23:41 ` luis.machado at arm dot com
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=bug-27826-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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).