Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Tom Tromey <tom@tromey.com>
Cc: <gdb-patches@sourceware.org>,
	 Andrew Burgess <aburgess@redhat.com>,
	Simon Marchi <simark@simark.ca>
Subject: Re: [PATCH] Skip gdb.dap/pause.exp on Solaris [PR34548]
Date: Sat, 22 Aug 2026 22:25:06 +0200	[thread overview]
Message-ID: <yddecfpgaxp.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <87fr07tupw.fsf@tromey.com> (Tom Tromey's message of "Fri, 21 Aug 2026 08:27:07 -0600")

Hi Tom,

>>>>>> "Rainer" == Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
>
> Rainer> As detailed in PR PR dap/34548, the gdb.dap/pause.exp test runs
> Rainer> indefinitely on Solaris.  To allow make check to finish, it needs to be
> Rainer> terminated manually.
>
> Rainer> To avoid this, this patch skips the test.
>
> Rainer> Tested on x86_64-pc-solaris2.11, sparcv9-sun-solaris2.11, and
> Rainer> x86_64-pc-linux-gnu.
>
> Rainer> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=34548
>
> Rainer> Ok for trunk?
>
> This is fine, but in the bug you mentioned other reports about target
> async not working.

not actually reports, just ca. 100 instances of the

Asynchronous execution not supported on this target.

message in the full testsuite log.  Some of them already turn the tests
UNSUPPORTED, while others cause the tests to FAIL.

> So maybe DAP testing should be entirely disabled for Solaris?

Like just returning 0 from allow_dap_tests on Solaris?  Or doing so for
all targets lacking async support?

Here's a breakdown of gdb.dap results on Solaris:

      8 ERROR
     11 FAIL
    713 PASS
      8 PATH
      8 UNRESOLVED
      2 UNSUPPORTED

I can't tell if it's still useful this way.

> Rainer> This might also be a candidate for the gdb-18 branch.
>
> It's fine by me.

Thanks.  I'll way for approval from a release manager then.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2026-08-22 20:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 14:18 Rainer Orth
2026-08-21 14:27 ` Tom Tromey
2026-08-22 20:25   ` Rainer Orth [this message]
2026-08-24  9:42     ` Andrew Burgess
2026-08-25  8:19       ` Rainer Orth
2026-08-25  8:22         ` Rainer Orth
2026-08-27 15:42         ` Tom Tromey
2026-08-28  8:49           ` [PATCH v2] Require async support for DAP tests [PR34548] Rainer Orth
2026-08-27 18:59         ` [PATCH] Skip gdb.dap/pauseR.exp on Solaris [PR34548] Andrew Burgess
2026-08-28  8:52           ` Rainer Orth

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=yddecfpgaxp.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --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