From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id KMp7FAnffmNR/xsAWB0awg (envelope-from ) for ; Wed, 23 Nov 2022 22:03:37 -0500 Received: by simark.ca (Postfix, from userid 112) id 509291E124; Wed, 23 Nov 2022 22:03:37 -0500 (EST) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=IVO8njnx; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-4.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, RDNS_DYNAMIC,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 0A13D1E0CB for ; Wed, 23 Nov 2022 22:03:37 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 34FD5384F031 for ; Thu, 24 Nov 2022 03:03:36 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 34FD5384F031 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1669259016; bh=q/wAVtoiLjWeSmE1OmXc9fBmwBPFOwFCM2os/6/UJRI=; h=Date:To:Cc:Subject:In-Reply-To:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=IVO8njnxKWIUEArMejxEmA00SpOGU9NOGgpzkvqkO+S9xtPCmLAyB46PrWrIOw2Fl 3CRuGYz4M7nQX+FHZU5okNIQ7LIykh5SSaq8onE9aQM4VH/ZDO2BYZcH+FjJZ/sQCT DlRPasAEsaNvfaQcwyqaRVAX8VrmC9ej+zh/CBhA= Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 0A6BA384F481 for ; Thu, 24 Nov 2022 03:03:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 0A6BA384F481 Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-649-qnyQmE86MvmHIisxznuirA-1; Wed, 23 Nov 2022 22:03:07 -0500 X-MC-Unique: qnyQmE86MvmHIisxznuirA-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 02BF68339C1; Thu, 24 Nov 2022 03:03:07 +0000 (UTC) Received: from f35-zws-nvidia (unknown [10.2.17.12]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 2F0B94EA4E; Thu, 24 Nov 2022 03:03:06 +0000 (UTC) Date: Wed, 23 Nov 2022 20:03:02 -0700 To: Simon Marchi via Gdb-patches Cc: Simon Marchi Subject: Re: [PATCH 00/14] Break up gdb.base/break.exp in multiple procs Message-ID: <20221123200302.34d78f05@f35-zws-nvidia> In-Reply-To: <20221123183959.2476477-1-simon.marchi@polymtl.ca> References: <20221123183959.2476477-1-simon.marchi@polymtl.ca> Organization: Red Hat MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Kevin Buettner via Gdb-patches Reply-To: Kevin Buettner Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" Hi Simon, On Wed, 23 Nov 2022 13:39:45 -0500 Simon Marchi via Gdb-patches wrote: > The test gdb.base/break.exp feels like a big house of cards that will > crumble the second you touch it. It is very long and it's really not > clear which test depends on the state left by which previous test. This > series aims at making it more manageable by breaking it up into many > procs, each starting with a fresh GDB. So you can be confident that the > tests in a proc only depends on the state of GDB resulting of other > tests in the same proc. > > Simon Marchi (14): > gdb/testsuite/gdb.base/break.exp: split test_break_commands_clear > gdb/testsuite/gdb.base/break.exp: split > test_break_file_line_convenience_var > gdb/testsuite/gdb.base/break.exp: split test_rbreak_shlib > gdb/testsuite/gdb.base/break.exp: split test_break_optimized_prologue > gdb/testsuite/gdb.base/break.exp: use proc_with_prefix for > test_next_with_recursion > gdb/testsuite/gdb.base/break.exp: split test_finish_arguments > gdb/testsuite/gdb.base/break.exp: split test_break_user_call > gdb/testsuite/gdb.base/break.exp: split > test_break_line_convenience_var > gdb/testsuite/gdb.base/break.exp: split test_break_silent_and_more > gdb/testsuite/gdb.base/break.exp: split test_break_default > gdb/testsuite/gdb.base/break.exp: split test_break_nonexistent_line > gdb/testsuite/gdb.base/break.exp: split test_no_break_on_catchpoint > gdb/testsuite/gdb.base/break.exp: split test_tbreak > gdb/testsuite/gdb.base/break.exp: split test_break > > gdb/testsuite/gdb.base/break.exp | 1191 +++++++++++++++--------------- > 1 file changed, 615 insertions(+), 576 deletions(-) Thanks for doing this! I looked at each patch in this series. LGTM. Kevin