-
Notifications
You must be signed in to change notification settings - Fork 30
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
OSAL path length variables cause tests to fail #111
Comments
Updating the matching There will still be a single DS test failing (with 3 asserts) after the above change, but this is only because that test is testing for a 'too long' filename, while it is only set up to be 'too long' with the default config values. Updating that test to make the passed-in string longer will cause the test to pass (i.e. an error will be returned). This is the test string that needs to be made longer: Line 967 in 2a6c6a2
As an aside - FM, MD & MM will also fail some tests for similar reasons with these config parameters set to the higher values. |
Fix #111: Use correct length filename for too large test
Checklist (Please check before submitting)
Describe the bug
A clear and concise description of what the bug is.
For certain values of
OSAL_CONFIG_MAX_FILE_NAME
andOSAL_CONFIG_MAX_PATH_LEN
, DS tests fail.To Reproduce
Steps to reproduce the behavior:
OSAL_CONFIG_MAX_FILE_NAME
set to 64 andOSAL_CONFIG_MAX_PATH_LEN
set to 128ctest coverage -VV --test-dir build/intel64/default_intel64/ -R coverage-ds-ds_file
Expected behavior
A clear and concise description of what you expected to happen.
Expect test to pass.
Code snips
If applicable, add references to the software.
System observed on:
Additional context
Add any other context about the problem here.
Related cFE issue: nasa/cFE#2372
Reporter Info
Full name and company/organization if applicable
Isaac Rowe, JSC/Jacobs Technology
The text was updated successfully, but these errors were encountered: