You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// It looks like mNotificationManager.notify(iterableNotification.requestCode, iterableNotification.build());
70
+
// is the culprit here for the flaky tests. This thread is spun up by the android system. Unless we do dependency injection and mock the notificationManager, it'll be hard to make this unflake.
71
+
Thread.sleep(1000);
72
+
if (android.os.Build.VERSION.SDK_INT >= android.os.Build.VERSION_CODES.M) {
// It looks like mNotificationManager.notify(iterableNotification.requestCode, iterableNotification.build());
67
89
// is the culprit here for the flaky tests. This thread is spun up by the android system. Unless we do dependency injection and mock the notificationManager, it'll be hard to make this unflake.
@@ -78,8 +100,8 @@ public void testMessage() throws Exception {
// It looks like mNotificationManager.notify(iterableNotification.requestCode, iterableNotification.build());
84
106
// is the culprit here for the flaky tests. This thread is spun up by the android system. Unless we do dependency injection and mock the notificationManager, it'll be hard to make this unflake.
85
107
Thread.sleep(100);
@@ -96,8 +118,8 @@ public void testMessage() throws Exception {
// It looks like mNotificationManager.notify(iterableNotification.requestCode, iterableNotification.build());
102
124
// is the culprit here for the flaky tests. This thread is spun up by the android system. Unless we do dependency injection and mock the notificationManager, it'll be hard to make this unflake.
0 commit comments