diff options
author | Emilio Pozuelo Monfort <pochu@debian.org> | 2017-02-05 10:28:11 +0000 |
---|---|---|
committer | Niels De Graef <nielsdegraef@gmail.com> | 2020-11-07 19:02:58 +0000 |
commit | 2eb18facbcc769ec4bf62f19435a43656e0365bc (patch) | |
tree | ff34a729cb41a2ad44dcb6bac911b44f29a38bb6 /gcr | |
parent | b96463c1423ecf94c0fc81f6353f47273edcfd81 (diff) | |
download | gcr-2eb18facbcc769ec4bf62f19435a43656e0365bc.tar.gz |
Increase test-gnupg-collection 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>
Diffstat (limited to 'gcr')
-rw-r--r-- | gcr/test-gnupg-collection.c | 2 |
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); |