summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEmilio Pozuelo Monfort <pochu@debian.org>2017-02-05 10:28:11 +0000
committerNiels De Graef <nielsdegraef@gmail.com>2020-11-07 16:29:51 +0000
commit006f04ce05c41c9ebf78a02c94adad3f32919fbc (patch)
tree237031bb9a9f6b8c2d6315ff064688afde64adb6
parenta23d3948fbc4ae174f10592a150bdbb11a430243 (diff)
downloadgcr-wip/smcv/timeout.tar.gz
Increase test-gnupg-collection timeoutwip/smcv/timeout
The timeout length in the current test is too low and can make the test fail if the system is too slow or too loaded. This test correctly stops waiting when a result is received, so the timeout will not actually be reached unless there is a problem. [smcv: Expand commit message] Fixes: https://gitlab.gnome.org/GNOME/gcr/issues/29 Bug-Debian: https://bugs.debian.org/846728 Signed-off-by: Simon McVittie <smcv@debian.org>
-rw-r--r--gcr/test-gnupg-collection.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/gcr/test-gnupg-collection.c b/gcr/test-gnupg-collection.c
index e8b9cba..e65900a 100644
--- a/gcr/test-gnupg-collection.c
+++ b/gcr/test-gnupg-collection.c
@@ -210,7 +210,7 @@ test_reload (Test *test, gconstpointer unused)
GcrGnupgKey *key;
_gcr_gnupg_collection_load_async (test->collection, NULL, on_async_ready, test);
- egg_test_wait_until (2500);
+ egg_test_wait_until (500000);
g_assert (test->result);
_gcr_gnupg_collection_load_finish (test->collection, test->result, &error);
g_assert_no_error (error);