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 682651 - Skip certain tests with --disable-debug
Skip certain tests with --disable-debug
Status: RESOLVED INCOMPLETE
Product: gcr
Classification: Core
Component: General
3.5.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-08-25 08:42 UTC by Priit Laes (IRC: plaes)
Modified: 2019-02-22 11:58 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
gcr-failing-tests-without-debug.patch (3.48 KB, patch)
2012-08-25 09:56 UTC, Priit Laes (IRC: plaes) 		needs-work Details | Review

Description Priit Laes (IRC: plaes) 2012-08-25 08:42:13 UTC 
When compiling gcr-3.5.90 from tarball I also ran tests which resulted in following failure:
TEST: test-subject-public-key... (pid=20135)
  /gcr/subject-public-key/rsa/cert-attributes:                         **
ERROR:test-subject-public-key.c:100:setup_attributes: assertion failed (klass == CKO_CERTIFICATE): (0x00000000 == 0x00000001)
FAIL
GTester: last random seed: R02S5a410c9e821358ec3f1274dc2fd220eb


This is on Gentoo ~amd64.
Comment 1 Priit Laes (IRC: plaes) 2012-08-25 08:49:18 UTC 
Only the tests in the for loop fail, other two tests complete fine:
/gcr/subject-public-key/load-failure-lookup: OK
/gcr/subject-public-key/load-failure-build: OK
Comment 2 Priit Laes (IRC: plaes) 2012-08-25 09:37:13 UTC 
This only happens within clean environment.
Comment 3 Priit Laes (IRC: plaes) 2012-08-25 09:53:43 UTC 
Duh.. this is due to --disable-debug.

Would it be possible to skip this test if debugging is disabled?
Comment 4 Priit Laes (IRC: plaes) 2012-08-25 09:56:01 UTC 
Created attachment 222382 [details] [review]
gcr-failing-tests-without-debug.patch

"Fixes" needed for testsuite to pass with --disable-debug.
Comment 5 Stef Walter 2013-06-18 14:36:53 UTC 
Very strange. I'm unable to duplicate this issue, and this is the only time I've ever heard about this. Are you building with strange options? What do your build logs look like? What does the entire test output look like? Could you run the test in question under valgrind and see what gets output?
Comment 6 Alexandre Franke 2017-07-17 18:35:05 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!