From 1b764e164151ee3a84f81736b820b601e4ef0088 Mon Sep 17 00:00:00 2001 From: Paul Beckingham Date: Tue, 28 Jul 2015 16:54:10 -0400 Subject: [PATCH] Test: Reverted change, because deletion propagates, and that's okay --- test/recurrence.t | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/test/recurrence.t b/test/recurrence.t index a1d62c174..7b145db07 100755 --- a/test/recurrence.t +++ b/test/recurrence.t @@ -153,11 +153,10 @@ class TestRecurrenceUntil(TestCase): # propagated to the instances, and expires them also. This is certainly # the way it has been behaving for a while, but is not the original # intention. Perhaps it is now the de facto functionality, in which - # change the 3 to a 0. The change to 0 also implies use of runError as - # exit code for empty filters is always != 0 + # the 3 becomes a 0. self.t.faketime("+24h") code, out, err = self.t("list rc.verbose:nothing") - self.assertEqual(out.count("one"), 3) + self.assertEqual(out.count("one"), 0) class TestRecurrenceTasks(TestCase):