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

issues:questions cFS Cannot Find Unit-Test Excecutables #508

Closed
DBprod opened this issue Jun 13, 2022 · 2 comments
Closed

issues:questions cFS Cannot Find Unit-Test Excecutables #508

DBprod opened this issue Jun 13, 2022 · 2 comments
Labels

Comments

@DBprod
Copy link

DBprod commented Jun 13, 2022

When attempting to run unit-tests on a cFS project with 1 custom application modeled closely after the Sample_App template the output of running "make test" fails as it cannot find the test executable's. It would be great to know if the steps I am following below are insufficient to properly run the unit tests, or if the error in my log files below indicates another issue?

To Reproduce
Steps to reproduce the behavior:

  1. make distclean
  2. make SIMULATION=native ENABLE_UNIT_TESTS=true prep
  3. make
  4. make test

Expected behavior
All unit-tests pass.

System observed on:

  • OS: VMware Ubuntu 22.04
  • Versions: cFS v6.7.0a

Output of Command
The actual output I receive is the following for every possible test:

lcov --capture --initial --directory build/native --output-file build/native/coverage_base.info
Capturing coverage data from build/native
Subroutine read_intermediate_text redefined at /usr/bin/geninfo line 2623.
Subroutine read_intermediate_json redefined at /usr/bin/geninfo line 2655.
Subroutine intermediate_text_to_info redefined at /usr/bin/geninfo line 2703.
Subroutine intermediate_json_to_info redefined at /usr/bin/geninfo line 2792.
Subroutine get_output_fd redefined at /usr/bin/geninfo line 2872.
Subroutine print_gcov_warnings redefined at /usr/bin/geninfo line 2900.
Subroutine process_intermediate redefined at /usr/bin/geninfo line 2930.
Found gcov version: 11.2.0
Using intermediate gcov format
Scanning build/native for .gcno files ...
geninfo: WARNING: no .gcno files found in build/native - skipping!
Finished .info-file creation
(cd build/native && ctest -O ctest.log)
Test project /home/daniel/fp_cfs_vrcs/build/native
Start 1: bin-sem-flush-test
Could not find executable bin-sem-flush-test
Looked in the following places:
bin-sem-flush-test
bin-sem-flush-test
Release/bin-sem-flush-test
Release/bin-sem-flush-test
Debug/bin-sem-flush-test
Debug/bin-sem-flush-test
MinSizeRel/bin-sem-flush-test
MinSizeRel/bin-sem-flush-test
RelWithDebInfo/bin-sem-flush-test
RelWithDebInfo/bin-sem-flush-test
Deployment/bin-sem-flush-test
Deployment/bin-sem-flush-test
Development/bin-sem-flush-test
Development/bin-sem-flush-test
Unable to find executable: bin-sem-flush-test
1/24 Test #1: bin-sem-flush-test ...............***Not Run 0.00 sec
Start 2: bin-sem-test

Then at the end of 24 messages like this, I receive this message:

0% tests passed, 24 tests failed out of 24

Total Test time (real) = 0.12 sec

The following tests FAILED:
1 - bin-sem-flush-test (Not Run)
2 - bin-sem-test (Not Run)
3 - bin-sem-timeout-test (Not Run)
4 - count-sem-test (Not Run)
5 - file-api-test (Not Run)
6 - mutex-test (Not Run)
7 - osal-core-test (Not Run)
8 - queue-timeout-test (Not Run)
9 - sem-speed-test (Not Run)
10 - symbol-api-test (Not Run)
11 - timer-test (Not Run)
12 - osal_core_UT (Not Run)
13 - osal_loader_UT (Not Run)
14 - osal_filesys_UT (Not Run)
15 - osal_file_UT (Not Run)
16 - osal_network_UT (Not Run)
17 - osal_timer_UT (Not Run)
18 - my_app-my_app (Not Run)
19 - cfe_core_default_cpu1_es_UT (Not Run)
20 - cfe_core_default_cpu1_sb_UT (Not Run)
21 - cfe_core_default_cpu1_evs_UT (Not Run)
22 - cfe_core_default_cpu1_tbl_UT (Not Run)
23 - cfe_core_default_cpu1_time_UT (Not Run)
24 - cfe_core_default_cpu1_fs_UT (Not Run)
Errors while running CTest
Output from these tests are in: /home/daniel/fp_cfs_vrcs/build/native/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
make: *** [Makefile:132: test] Error 8

@skliper
Copy link
Contributor

skliper commented Jun 13, 2022

This behavior is typically observed when the make step fails to build the tests, so it's likely an issue from before you even run make test. Likely need to debug the build.

@DBprod DBprod closed this as completed Jun 14, 2022
@DBprod
Copy link
Author

DBprod commented Jun 14, 2022

Yes this was indeed the case, thank you for the help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants