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 ADA2D14F9C4 for ; Wed, 31 Jul 2024 20:37:51 +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=1722458273; cv=none; b=lvQx5fnFCXlmyclP0FNS12MVQFOyfnUSemIL66m6BDZPxLXOdubqwtE+Ts5ex4Uij3R3cKAH54MvtTrCFXjCi8W40jug8GNuIBef1i7wKOh2tNMISYi8IcV77NGMLoCvwYSCEEHDh5Q9TvGv4rC9z7YBP4DB54qxxahAk5XJYss= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1722458273; c=relaxed/simple; bh=46V9nT7GlSjZkRJoFYggTc9j17pK0sEvzsvkDgq6GFc=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=r2XRPJr+qyvO8A5wpwyvKffaApudDqaeka4mJiul5rfyUXf8Dxt++a046A0Bwc3IAyr/vLaSwvCzdc7y7eqHG/0hh3wLgPAujeBI7NrvYetT06BbALUeGO7FZbp3Oho0uNSjvhOmLOqJG5q5rFNzq6tkr1dXnBS8LGIeVWnSpyA= 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-12-196.cpe.net.cable.rogers.com [99.228.12.196]) (authenticated bits=0) by secure.elehost.com (8.15.2/8.15.2/Debian-22ubuntu3) with ESMTPSA id 46VKbgNx3315698 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 31 Jul 2024 20:37:43 GMT Reply-To: From: To: , "'Junio C Hamano'" Cc: "'Patrick Steinhardt'" , , "=?utf-8?Q?'Ren=C3=A9_Scharfe'?=" , "'Kyle Lippincott'" , "'Phillip Wood'" , "'Josh Steadmon'" References: <008901dae362$386ae280$a940a780$@nexbridge.com> <00a901dae387$c68f6f70$53ae4e50$@nexbridge.com> In-Reply-To: <00a901dae387$c68f6f70$53ae4e50$@nexbridge.com> Subject: RE: [RFC PATCH 0/3] Introduce clar testing framework Date: Wed, 31 Jul 2024 16:37:37 -0400 Organization: Nexbridge Inc. Message-ID: <00ba01dae389$7ecb2c40$7c6184c0$@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 Content-Language: en-ca Thread-Index: AQE2Q9x0fuag13GoRDOLG7kBaq5wcQG2RBBYApODSOMCbGq0BQFRLUR9sxpPVYA= On Wednesday, July 31, 2024 4:25 PM, I wrote: >On Wednesday, July 31, 2024 12:53 PM, Junio C Hamano wrote: >> writes: >> >>> I'm sorry for being so behind the curve... what is clar and where = does it run? >> >>We have t/unit-test/test-lib.[ch] that are our home-grown unit test >>framework. A handful of tests have been written to use it, when you >>say "make test", or "(cd t && make)", unit tests binaries linked with = the home- >grown unit test framework run. >> >>clar is a _potential_ replacement for our home-grown framework, >>suggested here because it would be nicer if we can use off-the-shelf >>component instead of having to enhance and maintain our own. >> >>Where and how it runs does not change even after clar turns out to be >>good enough for our purpose and we commit to replace our home-grown >>unit test framework with it. > >Well... I would like to be able to see whether this can be built/used = on NonStop just >so I can stay ahead of the curve or be far enough in advance of it to = request any >required fixes to make it work on platform. After checking out clar, I would say it has potential, but needs to be = slightly more portable to depend on more than gcc CFLAGS (specifically -Wall). I will = ask that of that team. It does look like it might be possible, but it should = integrate with the config.mak.uname settings, so c99 or c11 (or soon c17) could be used = with other CFLAGS from that file so maintainers only have to worry about one = location. --Randall