From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 108333 invoked by alias); 22 Jul 2015 09:17:12 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org Received: (qmail 108301 invoked by uid 48); 22 Jul 2015 09:17:11 -0000 From: "ciro.santilli at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug testsuite/18704] New: Don't run bigcore test by default on make check Date: Wed, 22 Jul 2015 09:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: testsuite X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: ciro.santilli at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-q3/txt/msg00089.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=18704 Bug ID: 18704 Summary: Don't run bigcore test by default on make check Product: gdb Version: HEAD Status: NEW Severity: enhancement Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: ciro.santilli at gmail dot com Target Milestone: --- When I run the testsuite, gdb.base/bigcore.exp takes a very long time, and worse: almost stalls my machine because it runs out of memory, and produces a 16Gb file. I wish that this test would not be run by default as it just puts way more strain on the machine than any other. I have seen projects that put all slow / intensive tests in a separate directory and you need a separate command to do them, e.g.: make perf I'm not sure if such test category currently exists: performance tests are typical candidates for such category, but they are acceptably slow. If I could all tests but one that would be great as well, but gmake's wildcard does not seem to support it easily: https://www.gnu.org/software/make/manual/html_node/Wildcards.html Old issue that does an analogous thing on Frisk: https://sourceware.org/bugzilla/show_bug.cgi?id=1852 Possibly related: Yao Qi's profiling proposal: https://sourceware.org/ml/gdb-patches/2013-08/msg00380.html -- You are receiving this mail because: You are on the CC list for the bug.