Bug 100241 - p11-kit 0.20.7 build problems on EL6
Summary: p11-kit 0.20.7 build problems on EL6
Status: NEW
Alias: None
Product: p11-glue
Classification: Unclassified
Component: p11-kit (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Stef Walter
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-16 21:40 UTC by Alvin Cura
Modified: 2017-03-16 21:40 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Alvin Cura 2017-03-16 21:40:52 UTC
EL build of p11-kit 0.20.7 failure.

1..45
ok 1 /managed/test_initialize_finalize
ok 2 /managed/test_initialize_fail
ok 3 /managed/test_separate_close_all_sessions
ok 4 /managed/fork-and-reinitialize
test-managed: test-mock.c:59: test_get_info: Assertion `memcmp (&info, &MOCK_INFO, sizeof (CK_INFO)) == 0' failed.
/bin/sh: line 5: 31514 Aborted                 (core dumped) ${dir}$tst
FAIL: test-managed
1..41
test-log: test-mock.c:59: test_get_info: Assertion `memcmp (&info, &MOCK_INFO, sizeof (CK_INFO)) == 0' failed.
/bin/sh: line 5: 31522 Aborted                 (core dumped) ${dir}$tst
FAIL: test-log
============================================================================
2 of 13 tests failed
Please report to https://bugs.freedesktop.org/enter_bug.cgi?product=p11-glue
============================================================================
make[3]: *** [check-TESTS] Error 1
make[3]: Leaving directory `/tmp/p11-kit/BUILD/p11-kit-0.20.7/p11-kit/tests'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/tmp/p11-kit/BUILD/p11-kit-0.20.7/p11-kit/tests'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/tmp/p11-kit/BUILD/p11-kit-0.20.7/p11-kit'
make: *** [check-recursive] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.xlVBpa (%check)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.xlVBpa (%check)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.