Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests are failing #71

Closed
ignatenkobrain opened this issue Oct 7, 2017 · 1 comment
Closed

tests are failing #71

ignatenkobrain opened this issue Oct 7, 2017 · 1 comment
Assignees

Comments

@ignatenkobrain
Copy link
Contributor

+ ctest -VV
UpdateCTestConfiguration  from :/home/brain/rpmbuild/BUILD/libnitrokey-7f7cfeb45b579204e0bc94bea37e2c810d2e5ec9/x86_64-redhat-linux-gnu/DartConfiguration.tcl
Parse Config file:/home/brain/rpmbuild/BUILD/libnitrokey-7f7cfeb45b579204e0bc94bea37e2c810d2e5ec9/x86_64-redhat-linux-gnu/DartConfiguration.tcl
UpdateCTestConfiguration  from :/home/brain/rpmbuild/BUILD/libnitrokey-7f7cfeb45b579204e0bc94bea37e2c810d2e5ec9/x86_64-redhat-linux-gnu/DartConfiguration.tcl
Parse Config file:/home/brain/rpmbuild/BUILD/libnitrokey-7f7cfeb45b579204e0bc94bea37e2c810d2e5ec9/x86_64-redhat-linux-gnu/DartConfiguration.tcl
Test project /home/brain/rpmbuild/BUILD/libnitrokey-7f7cfeb45b579204e0bc94bea37e2c810d2e5ec9/x86_64-redhat-linux-gnu
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 1
    Start 1: runs

1: Test command: /home/brain/rpmbuild/BUILD/libnitrokey-7f7cfeb45b579204e0bc94bea37e2c810d2e5ec9/x86_64-redhat-linux-gnu/test_C_API
1: Test timeout computed to be: 1500
1: 
1: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1: test_C_API is a Catch v1.10.0 host application.
1: Run with -? for options
1: 
1: -------------------------------------------------------------------------------
1: C API connect
1: -------------------------------------------------------------------------------
1: /home/brain/rpmbuild/BUILD/libnitrokey-7f7cfeb45b579204e0bc94bea37e2c810d2e5ec9/unittest/test_C_API.cpp:10
1: ...............................................................................
1: 
1: /home/brain/rpmbuild/BUILD/libnitrokey-7f7cfeb45b579204e0bc94bea37e2c810d2e5ec9/unittest/test_C_API.cpp:12: FAILED:
1:   REQUIRE( login != 0 )
1: with expansion:
1:   0 != 0
1: 
1: -------------------------------------------------------------------------------
1: Check retry count
1: -------------------------------------------------------------------------------
1: /home/brain/rpmbuild/BUILD/libnitrokey-7f7cfeb45b579204e0bc94bea37e2c810d2e5ec9/unittest/test_C_API.cpp:21
1: ...............................................................................
1: 
1: /home/brain/rpmbuild/BUILD/libnitrokey-7f7cfeb45b579204e0bc94bea37e2c810d2e5ec9/unittest/test_C_API.cpp:21: FAILED:
1: due to a fatal error condition:
1:   SIGSEGV - Segmentation violation signal
1: 
1: ===============================================================================
1: test cases: 2 | 2 failed
1: assertions: 2 | 2 failed
1: 
1/1 Test #1: runs .............................***Exception: SegFault  0.14 sec
@szszszsz
Copy link
Member

szszszsz commented Oct 7, 2017

Hi! Indeed I have set online tests as a default - will be switched to testing offline library behavior instead of the communication library<->device.

sgued pushed a commit to sgued/libnitrokey that referenced this issue Feb 14, 2022
Add link to NetHSM documentation to README
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants