From 162c0d3ee30790ec5a75e20b0e2e8bc61ed92375 Mon Sep 17 00:00:00 2001
From: Anders Svensson <anders@erlang.org>
Date: Mon, 26 Sep 2011 18:05:38 +0200
Subject: Explicit {init,end}_per_group/2 to work around ct bug

Without these functions the result pages are currently mangled.
The overview page shows that no suites have run, even though all
in fact are, and diameter-specific page is truncated after the
dict suite, which is the first suite that relied on an implicit
{init,end}_per_group/2. This is apparently the result of a recent
common_test commit.
---
 lib/diameter/test/diameter_sync_SUITE.erl | 8 ++++++++
 1 file changed, 8 insertions(+)

(limited to 'lib/diameter/test/diameter_sync_SUITE.erl')

diff --git a/lib/diameter/test/diameter_sync_SUITE.erl b/lib/diameter/test/diameter_sync_SUITE.erl
index ecd935bd98..84f77b6066 100644
--- a/lib/diameter/test/diameter_sync_SUITE.erl
+++ b/lib/diameter/test/diameter_sync_SUITE.erl
@@ -26,6 +26,8 @@
 -export([suite/0,
          all/0,
          groups/0,
+         init_per_group/2,
+         end_per_group/2,
          init_per_suite/1,
          end_per_suite/1]).
 
@@ -57,6 +59,12 @@ tc() ->
      timeout,
      flush].
 
+init_per_group(_, Config) ->
+    Config.
+
+end_per_group(_, _) ->
+    ok.
+
 init_per_suite(Config) ->
     ok = diameter:start(),
     Config.
-- 
cgit v1.2.3