1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
|
From: Santiago Vila <sanvila@debian.org>
Date: Wed, 9 Apr 2025 16:17:47 +0200
Subject: Disable test which segfaults on some systems
On some systems, the test below aborts with segfault, like this:
18/43 gcr:gck / object FAIL 0.02s killed by signal 11 SIGSEGV
This apparently happens on single-CPU systems with very high probability, but it
has been also observed on machines with 2 CPUs.
[smcv: Modified to use g_test_skip() instead of omitting this test case
completely, and allow it to be re-enabled with a Debian-specific
environment variable]
Bug-Debian: https://bugs.debian.org/1057562
Forwarded: https://gitlab.gnome.org/GNOME/gcr/-/issues/119
---
gck/test-gck-object.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/gck/test-gck-object.c b/gck/test-gck-object.c
index 7b23f12..0f3df3f 100644
--- a/gck/test-gck-object.c
+++ b/gck/test-gck-object.c
@@ -318,6 +318,11 @@ test_set_attributes (Test *test, gconstpointer unused)
gchar *value = NULL;
gboolean ret;
+ if (g_getenv ("DEB_ALLOW_FLAKY_TESTS") == NULL) {
+ g_test_skip ("https://gitlab.gnome.org/GNOME/gcr/-/issues/119");
+ return;
+ }
+
gck_builder_add_ulong (&builder, CKA_CLASS, 6);
gck_builder_add_string (&builder, CKA_LABEL, "CHANGE TWO");
|
