After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 791932 - Tests not deterministic
Tests not deterministic
Status: RESOLVED OBSOLETE
Product: gnome-keyring
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-12-24 19:08 UTC by Jan Tojnar
Modified: 2021-06-18 10:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gkm-timer: Use monotonic time exclusively (1.69 KB, patch)
2018-03-01 16:21 UTC, Daiki Ueno
committed Details | Review

Description Jan Tojnar 2017-12-24 19:08:56 UTC
Tests sometimes fail and sometimes run okay.

In one build build https://hydra.nixos.org/build/66446594#tabs-summary there was this failure.

** (./test-data-der:15412): CRITICAL **: egg_symkey_generate_pkcs12: assertion 'iterations > 0' failed
FAIL: test-data-der 16 /gkm/data-der/write_pkcs8_encrypted
ERROR: test-data-der process failed: 251

In other I saw:

ERROR:pkcs11/gkm/test-timer.c:97:test_cancel: assertion failed: (timer != NULL) FAIL: test-timer 3 /gkm/timer/cancel

That one is also mentioned in https://bugzilla.gnome.org/show_bug.cgi?id=754633
Comment 1 Daiki Ueno 2018-03-01 16:21:03 UTC
Created attachment 369150 [details] [review]
gkm-timer: Use monotonic time exclusively

Previously, it used g_get_real_time(), g_get_current_time(), and
g_get_monotonic_time() in a mixed manner.  To measure the ellapsed
time, it would be sufficient to use g_get_monotonic_time() only.
--
When I see the test-timer failure, I observe a strange time jump in g_get_real_time() in timer_thread_func().  I am not sure why this happens, but using monotonic time instead should fix the issue.
Comment 2 Daiki Ueno 2018-03-02 09:30:59 UTC
Comment on attachment 369150 [details] [review]
gkm-timer: Use monotonic time exclusively

Attachment 369150 [details] pushed as 1864f1e - gkm-timer: Use monotonic time exclusively
Comment 3 Vladimír Čunát 2018-08-30 07:55:27 UTC
For reference, the first FAIL is still happening with 3.28.2: https://nix-cache.s3.amazonaws.com/log/hk2zp7my151ncl3axdd9q2vprp5422af-gnome-keyring-3.28.2.drv
Comment 4 André Klapper 2021-06-18 10:40:46 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/

Thank you for your understanding and your help.