From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from secure.elehost.com (secure.elehost.com [185.209.179.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6019819E7F7 for ; Fri, 31 Oct 2025 01:03:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.209.179.11 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761872583; cv=none; b=SzX08cEqIp/S5ZTc9mAOV+tSOVzy3jFcczCQLc98WCCduV81prLE7y/QSnzvVP/qKi4GiS7Q3CRqSw1v6yDA6oQIOII+B7E207eyvpqIw06R9eoOeYAChLWkFnqIO6wiIrdthjNXR/RsEwBDkGNz8EPKk1OknwWj8yYYZVs6GZc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761872583; c=relaxed/simple; bh=lrM0UZUz/JhGARvpeucZNOZb9OkDiSAkHzQZjGCgsI4=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=gQvc1pITjnGctlTDZtOIgDy2M1KOmvlQeEE/JGXh/CI5vMq+MqrdgpunmQ3XZMfv+wcODOLzyBePjGnqX3Q826KpDk32yMccFd7wD7nv5xsYKMDkamQzmq2KUvzbBRH6RNbRR4gLhGGOCBJiQSNrvhu49E5V9zLK4EyCjmYQyHQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=nexbridge.com; spf=pass smtp.mailfrom=nexbridge.com; arc=none smtp.client-ip=185.209.179.11 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=nexbridge.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=nexbridge.com X-Virus-Scanned: Debian amavisd-new at secure.elehost.com Received: from Mazikeen (pool-99-228-67-183.cpe.net.cable.rogers.com [99.228.67.183]) (authenticated bits=0) by secure.elehost.com (8.15.2/8.15.2/Debian-22ubuntu3) with ESMTPSA id 59V12oYj2078086 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 31 Oct 2025 01:02:50 GMT Reply-To: From: To: "=?utf-8?Q?'SZEDER_G=C3=A1bor'?=" Cc: "'Kristoffer Haugsbakk'" , "'Junio C Hamano'" , References: <000d01dc4831$ff049500$fd0dbf00$@nexbridge.com> <729f9bbf-b75b-4161-b8aa-505ff906bb8a@app.fastmail.com> <3dad5cb9-976b-4e60-9e6e-05c12c7d9f2d@app.fastmail.com> <009f01dc49e6$98c5ae30$ca510a90$@nexbridge.com> In-Reply-To: Subject: RE: [BUGS] Git v2.51.2 on NonStop5 Date: Thu, 30 Oct 2025 21:02:45 -0400 Organization: Nexbridge Inc. Message-ID: <00c401dc4a02$14ae4eb0$3e0aec10$@nexbridge.com> Precedence: bulk X-Mailing-List: git@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQGUZTuwh66ijI7aIz2t8Y1znRjrdQMi5nLUAqyTHv8CtpTgNQGF/rGCAO35pZgBI7rTqbUKSw+w Content-Language: en-ca X-Antivirus: Norton (VPS 251030-6, 10/30/2025), Outbound message X-Antivirus-Status: Clean On October 30, 2025 6:31 PM, SZEDER G=C3=A1bor wrote: >On Thu, Oct 30, 2025 at 05:46:01PM -0400, rsbecker@nexbridge.com wrote: >> On October 30, 2025 4:26 PM, Kristoffer Haugsbakk wrote: >> >On Thu, Oct 30, 2025, at 20:42, Junio C Hamano wrote: >> >> "Kristoffer Haugsbakk" writes: >> >> >> >>> On Tue, Oct 28, 2025, at 18:40, rsbecker@nexbridge.com wrote: >> >>>>[snip] >> >>> >> >>> Would it make sense for maintenance releases to have a small >> >>> release candidate pre-release? Both of these maintenance = releases >> >>> have had issues. >> >> >> >> Well, that is usually called "the tip of 'master'". Has NonStop >> >> been having issues with the tip of 'master'? For how long? Why >> >> haven't we heard about it at all? After things are merged there >> >> (which requires them to be cooking in 'next'---oh, has NonStop = been >> >> having issues with 'next'? For how long?), only fixes are chosen = and merged to >'maint' >> >> to be the next maintenance release. >> >> ... >> >> I doubt any pre-release on 'maint' has much value in that anybody >> >> who are not testing the tip of 'master' would not be testing it = either. >> > >> >You are probably 99.9% likely to be correct. >> >> We tried setting up a CI/CD process for git on NonStop. The problem = is >> that we use Jenkins, which gets triggered each time a change is made = on a branch. >> The actual difficulty is that a single run takes more than a day. = Once >> the committer adds each commit to a branch, we end up with a queue >> that is >> 2-3 weeks long, so end up not running a continuous process. Instead, >> we run about 1 a week, which should catch things. The difficulty is >> with the latest release is that 2.25.2 came out before our cycle and >> the breaks were in there because of changes to one test that just did >> not end up dequeuing in time. NonStop is building and testing fine = now >> after Peff's suggestion on SHELL_PATH, but that was only apparent at >> 2.52.2. 2.51.1 did not have this issue with our inadvertent use of = ksh to run each >test script. > >Neither the test library nor t7900 changed in the last two maintenance >releases: > > $ git rev-list --count v2.51.0..v2.51.2 -- t/test-lib.sh = t/test-lib-functions.sh >t/t7900-maintenance.sh > 0 Honestly, I do not know. I am just reporting my experience from my own CI/CD system. All builds are from scratch. Given that I am now using = bash, the situation is resolved as far as I am concerned. If the team wants me = to try to do a bisect, I can, but it will take weeks to do this based on = how long the compile/test cycles are.