From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8355 invoked by alias); 23 Aug 2013 20:36:56 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 8306 invoked by uid 89); 23 Aug 2013 20:36:55 -0000 X-Spam-SWARE-Status: No, score=-7.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Fri, 23 Aug 2013 20:36:55 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r7NKasia003985 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 23 Aug 2013 16:36:54 -0400 Received: from barimba.redhat.com (ovpn-113-142.phx2.redhat.com [10.3.113.142]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r7NKarxN017513 for ; Fri, 23 Aug 2013 16:36:53 -0400 From: Tom Tromey To: gdb-patches@sourceware.org Subject: [PATCH 00/13] test suite parallel safety Date: Fri, 23 Aug 2013 20:36:00 -0000 Message-Id: <1377290210-483-1-git-send-email-tromey@redhat.com> X-SW-Source: 2013-08/txt/msg00696.txt.bz2 This is the final series to make the test suite parallel-safe. As a reminder, here parallel safety just means that a given test will not write (or delete) files outside of the subdirectory assigned by the gdb test harness. Even after this series there are stragglers: First, I only seriously tried this on a single architecture. So, there are bound to be issues for other arches. These are generally easy to fix; and, if you have inotifytools easy to diagnose as well. I'll work on this as time permits. I think this is less serious than it may sound, as there aren't really that many arch-specific tests that are likely to have clashes. Second, Fortran: Running ../../../archer/gdb/testsuite/gdb.fortran/library-module.exp ... ./ CREATE lib.mod0 ./ DELETE lib.mod0 ./ CREATE libmany.mod0 ./ DELETE libmany.mod0 Running ../../../archer/gdb/testsuite/gdb.fortran/module.exp ... ./ CREATE mod1.mod0 ./ DELETE mod1.mod0 ./ CREATE mod2.mod0 ./ DELETE mod2.mod0 ./ CREATE modmany.mod0 ./ DELETE modmany.mod0 ./ CREATE moduse.mod0 ./ DELETE moduse.mod0 This happens because the compiler generates these files. I don't know of a good, portable (across Fortran compilers) way to fix this. This is only an issue in practice if we have multiple Fortran modules with the same name. And, finally: Running ../../../archer/gdb/testsuite/gdb.trace/save-trace.exp ... ./ CREATE savetrace.tr ./ DELETE savetrace.tr This is a test for a directory-less save. It seemed wrong to change it. I regression tested this series on x86-64 Fedora 18, both with GDB_PARALLEL set and without. After this series, I think we're ready to enable the new parallel code. Tom