From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 2D93F3858D35 for ; Fri, 16 Jun 2023 10:08:16 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 2D93F3858D35 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1686910095; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=FKKFgtcYVD51QXQCXoG5eePOF7LYf8NPKmJMMsoL1vw=; b=QwiUhTjwELR/XdmhhUirHComcOQgqoR4sRf9q/dlBcNOImXaAAAEzsNLmBKMvir3W1bM6F AkSTs9X91H5YcHkRPbIXIjexp4VAaFnBe8vg9j6VhO1th3Ebn5Z4nLgsb8XdrxCxtMqo+y 7bwEtoqCY9JbvRK8qseQx0DAe3wplig= Received: from mail-wr1-f71.google.com (mail-wr1-f71.google.com [209.85.221.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-665-VxslVz__Pq6pHFG2Fm0QeQ-1; Fri, 16 Jun 2023 06:08:14 -0400 X-MC-Unique: VxslVz__Pq6pHFG2Fm0QeQ-1 Received: by mail-wr1-f71.google.com with SMTP id ffacd0b85a97d-30e5c497f90so200217f8f.2 for ; Fri, 16 Jun 2023 03:08:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686910093; x=1689502093; h=content-transfer-encoding:in-reply-to:subject:from:content-language :references:to:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=FKKFgtcYVD51QXQCXoG5eePOF7LYf8NPKmJMMsoL1vw=; b=Hr9Ku22J1jpb6PgKVY5jzCXNt9syJcVNO3NCEf3fLzOhqi/tmHTBvTuXmmpwuI2so+ NnB3XDmkAAoAzg7FTKhG3BfTIUGXp/p2Tl/IeTmZBaIdOzhbpYMIZrsTA7lHOKKrdN0n lk1EV1J8XDO0np+VI3Scu0NjTATrXs2QPKgh0YlOZ2LdNb8wOMJCfwL+zOCLjpa1kdwE qHh52TudqRPX173k75OuKxElK6ze3eLp4+O7H/HOzAZv5zfvOjR4tdJ8wSAzsx5PIHfj /O7IXEHseZnmeH40BnYIrEgwX/jAKHAqhei5+sb/QxxdlZRfOoD57LHTfZmhmcoNV4fg xzRg== X-Gm-Message-State: AC+VfDyNHr04mAss53TWfDG6U8YQnx0XrVVew0Hszc19Xr8dNM+Ed3XL RGD3nDITqY2ZFydsldVglUlM7jOXL03W0J/djG3ufHGVh0CZ2l8xeUwOlTpGo1U553NzlPya2xE IZSgzDgc4K9DQtqYf6LPYnEDCwA== X-Received: by 2002:adf:f244:0:b0:309:4999:7549 with SMTP id b4-20020adff244000000b0030949997549mr932425wrp.46.1686910092822; Fri, 16 Jun 2023 03:08:12 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6jTJm1Xpb3vPd41NN8csbpWqGB4KnUiKD90UhLXUsxaUX+kdTA1TxxewL/lrrv2JTInmDspQ== X-Received: by 2002:adf:f244:0:b0:309:4999:7549 with SMTP id b4-20020adff244000000b0030949997549mr932408wrp.46.1686910092495; Fri, 16 Jun 2023 03:08:12 -0700 (PDT) Received: from [192.168.1.7] ([80.168.198.238]) by smtp.gmail.com with ESMTPSA id t1-20020adfe101000000b0030e5a63e2dbsm23468863wrz.80.2023.06.16.03.08.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 16 Jun 2023 03:08:12 -0700 (PDT) Message-ID: <85bd5f2f-f1bf-ce13-13f6-af60e9089184@redhat.com> Date: Fri, 16 Jun 2023 11:08:06 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 To: Ruud van der Pas , "binutils@sourceware.org" References: From: Nick Clifton Subject: Re: The use of the name tmpdir in the tests In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-GB Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi Ruud, > This is an absolute detail, but as I am working on the test suite > for gprofng, I noticed the use of a directory called "tmpdir". > The thing is that in the case of gprofng at least, this is far from > a temporary directory. It is going to contain the generated experiment > data that is crucial for troubleshooting in case of a failure. Wouldn't it be better for gprofng to store the data in a directory named after the experiment ? That way if the user runs multiple, different experiments it would still be possible to determine which directory contains the relevant data. > Of course we could place those experiments elsewhere, but my idea > was to give tmpdir a more meaningful name. > > Are there any objections against doing so? For example, will > certain scripts fail? Probably. There are lots of places in the binutils sources where the "tmpdir" directory name is explicitly referenced, so you would need a large patch to change them all. Plus I would not be at all surprised to find that there are users of the binutils who expect to find certain things in the tmpdir directories. So renaming would definitely cause them problems. > If not, any suggestion what would be a good name? I'm not that > creative so don't get any further than "results" or "expresults" > and am definitely open to suggestions. How about "tmpdir-" or "resultdir-" ? Cheers Nick