RFC PATCH: contrib/test_summary mode for submitting testsuite results to bunsen
Frank Ch. Eigler
fche@redhat.com
Tue Sep 17 15:13:34 GMT 2024
Hi -
> [...]
> I pretty much only use `contrib/test_summary` via the
> `mail-report.log` target in the top-level Makefile; maybe add a
> `bunsen` target to the top-level Makefile, too, to simplify invoking
> it?
Something like this: ?
diff --git a/Makefile.in b/Makefile.in
index 966d60454960..41651e7592d2 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -2852,6 +2852,14 @@ mail-report-with-warnings.log: warning.log
chmod +x $@
echo If you really want to send e-mail, run ./$@ now
+bunsen-report.log:
+ if test x'$(BOOT_CFLAGS)' != x''; then \
+ BOOT_CFLAGS='$(BOOT_CFLAGS)'; export BOOT_CFLAGS; \
+ fi; \
+ $(srcdir)/contrib/test_summary -b >$@
+ chmod +x $@
+ echo If you really want to send to bunsen, run ./$@ now
+
# Local Vim config
$(srcdir)/.local.vimrc:
diff --git a/Makefile.tpl b/Makefile.tpl
index da38dca697ad..e2c3f6bf6ca5 100644
--- a/Makefile.tpl
+++ b/Makefile.tpl
@@ -1034,6 +1034,14 @@ mail-report-with-warnings.log: warning.log
chmod +x $@
echo If you really want to send e-mail, run ./$@ now
+bunsen-report.log:
+ if test x'$(BOOT_CFLAGS)' != x''; then \
+ BOOT_CFLAGS='$(BOOT_CFLAGS)'; export BOOT_CFLAGS; \
+ fi; \
+ $(srcdir)/contrib/test_summary -b >$@
+ chmod +x $@
+ echo If you really want to send to bunsen, run ./$@ now
+
# Local Vim config
$(srcdir)/.local.vimrc:
More information about the Bunsen
mailing list