[gnome-keyring: 1/2] Remove tap-gtester, rely on GLib 2.38+ built-in TAP output instead
- From: Daiki Ueno <dueno src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-keyring: 1/2] Remove tap-gtester, rely on GLib 2.38+ built-in TAP output instead
- Date: Thu, 26 Sep 2019 14:30:43 +0000 (UTC)
commit e8291902185e02a20f4542b40c3fdb3a9f07a13b
Author: Simon McVittie <smcv debian org>
Date: Fri Sep 13 10:28:44 2019 +0100
Remove tap-gtester, rely on GLib 2.38+ built-in TAP output instead
GLib 2.62+ outputs TAP by default, which breaks the tap-gtester
script's expectations. In older GLib versions since 2.38, --tap is an
opt-in to the TAP output mode, so use that.
This is essentially the same issue as
https://github.com/cockpit-project/cockpit/pull/11998 (cockpit was the
source of the tap-gtester script), GNOME/gcr!19, and GNOME/libsecret!5.
Signed-off-by: Simon McVittie <smcv debian org>
Bug-Debian: https://bugs.debian.org/940157
Makefile.am | 3 +-
build/tap-gtester | 206 ------------------------------------------------------
2 files changed, 1 insertion(+), 208 deletions(-)
---
diff --git a/Makefile.am b/Makefile.am
index 640c0e98..d753fd22 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -64,7 +64,7 @@ asn1-reparse:
# Default executable tests
LOG_DRIVER = $(srcdir)/build/tap-driver
LOG_DRIVER_FLAGS = --format=tap
-LOG_COMPILER = $(srcdir)/build/tap-gtester
+LOG_COMPILER = sh -c 'exec "$$0" "$$@" --tap'
VALGRIND_ARGS = --trace-children=no --quiet --error-exitcode=33 \
--suppressions=valgrind-suppressions --gen-suppressions=all \
@@ -181,7 +181,6 @@ EXTRA_DIST = \
HACKING \
$(ASN1_FILES) \
build/tap-driver \
- build/tap-gtester \
$(VALGRIND_SUPPRESSIONS) \
$(NULL)
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]