From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: "Ijaz, Abdul B" <abdul.b.ijaz@intel.com>,
"Marchi, Simon" <Simon.Marchi@amd.com>
Cc: "blarsen@redhat.com" <blarsen@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 1/1] testsuite, btrace: update btrace testsuite to test all btrace recording methods
Date: Tue, 9 Apr 2024 09:54:52 +0000 [thread overview]
Message-ID: <DM8PR11MB57497645A9E46E7563BD41E6DE072@DM8PR11MB5749.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM8PR11MB5749AEA76C437EEF19617A7BDE352@DM8PR11MB5749.namprd11.prod.outlook.com>
>>With this change, gdb.btrace will, instead of selecting the
>>default recording method, run all tests for all available and
>>applicable methods. This increases testing coverage.
Linux does not allow BTS and PT to be used at the same time.
This change, which was requested by Simon some time ago,
does not work with 'make check-parallel' when two gdb.btrace
tests are executed concurrently.
Is there a way to teach make check-parallel to run gdb.btrace
sequentially?
There are a few python tests that use btrace, but they could be
moved to gdb.btrace.
Regards,
Markus.
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2024-04-09 9:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 8:23 [PATCH 0/1] update btrace tests to test all " Abdul Basit Ijaz
2024-03-04 8:23 ` [PATCH 1/1] testsuite, btrace: update btrace testsuite to test all btrace " Abdul Basit Ijaz
2024-03-26 9:16 ` Metzger, Markus T
2024-04-09 9:54 ` Metzger, Markus T [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-12 16:26 [PATCH 0/1] update btrace tests to test all " Abdul Basit Ijaz
2024-02-12 16:26 ` [PATCH 1/1] testsuite, btrace: update btrace testsuite to test all btrace " Abdul Basit Ijaz
2024-02-13 10:16 ` Guinevere Larsen
2024-02-15 10:19 ` Ijaz, Abdul B
2024-02-15 12:14 ` Metzger, Markus T
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=DM8PR11MB57497645A9E46E7563BD41E6DE072@DM8PR11MB5749.namprd11.prod.outlook.com \
--to=markus.t.metzger@intel.com \
--cc=Simon.Marchi@amd.com \
--cc=abdul.b.ijaz@intel.com \
--cc=blarsen@redhat.com \
--cc=gdb-patches@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: 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