[tracker-miners/wip/carlosg/shuffle-libtracker-miner: 101/116] tests: Drop dubious assert
- From: Carlos Garnacho <carlosg src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [tracker-miners/wip/carlosg/shuffle-libtracker-miner: 101/116] tests: Drop dubious assert
- Date: Thu, 12 Dec 2019 10:29:23 +0000 (UTC)
commit 47b5b2d671f32802cb4c8dffebf96d99a5322a04
Author: Carlos Garnacho <carlosg gnome org>
Date: Mon Mar 4 13:31:07 2019 +0100
tests: Drop dubious assert
In the comment above the "may" verb is key. If the monitor does a
good job at coalescing events that would not be the case, we should
admit the flag being either set or unset here.
tests/libtracker-miner/tracker-monitor-test.c | 2 --
1 file changed, 2 deletions(-)
---
diff --git a/tests/libtracker-miner/tracker-monitor-test.c b/tests/libtracker-miner/tracker-monitor-test.c
index 36bb20a2d..26c2c1d26 100644
--- a/tests/libtracker-miner/tracker-monitor-test.c
+++ b/tests/libtracker-miner/tracker-monitor-test.c
@@ -426,9 +426,7 @@ test_monitor_file_event_created (TrackerMonitorTestFixture *fixture,
g_assert_cmpuint ((file_events & MONITOR_SIGNAL_ITEM_MOVED_FROM), ==, 0);
g_assert_cmpuint ((file_events & MONITOR_SIGNAL_ITEM_MOVED_TO), ==, 0);
g_assert_cmpuint ((file_events & MONITOR_SIGNAL_ITEM_DELETED), ==, 0);
-
/* We may get an UPDATE due to the way the file is created */
- g_assert_cmpuint ((file_events & MONITOR_SIGNAL_ITEM_UPDATED), >, 0);
g_assert_cmpuint ((file_events & MONITOR_SIGNAL_ITEM_ATTRIBUTE_UPDATED), ==, 0);
/* Cleanup environment */
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]