From 12d96249ae82012b8ce37c2b30227099d4f329af Mon Sep 17 00:00:00 2001
From: Jules Aguillon <jules@j3s.fr>
Date: Tue, 26 Sep 2023 16:48:51 +0200
Subject: [PATCH] 'make bench' target that prints result to stdout

Unfortunately, it's hard to distinguish between a failed build or a
change to be promoted in the driver source.

I chose not to check for the driver exit status as it's likely to break
often.
---
 Makefile | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/Makefile b/Makefile
index e6c5b6b535..012a281927 100644
--- a/Makefile
+++ b/Makefile
@@ -13,6 +13,15 @@ publish-docs:
 test :
 	dune runtest
 
+# Echo is disabled as the benchmarks results are printed on stdout.
+# '@bench' exit status is not checked as it's very likely to fail due to
+# needing promotion rather than because it really failed.
+.PHONY : bench
+bench:
+	-@dune build @bench
+	@dune promote driver-benchmarks.json
+	@cat driver-benchmarks.json
+
 .PHONY : coverage
 coverage :
 	dune build --instrument-with bisect_ppx @test/runtest --no-buffer -j 1 --force || true