-
-
Notifications
You must be signed in to change notification settings - Fork 154
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
Test case failed - cli/cli-action-conf.sh #258
Comments
Hey @wzyhay, thanks for reporting this, and sorry for the long delay, but I finally figured out why I am not getting email notifications for new issues. Not sure yet what's going on here, but I'll suggest two things to start with:
I suspect it's the missing target snoopy.ini file (i.e. |
Thank you for your reply. I executed the strace command as you said and found that the result was as follows:
The output of another check command is as follows:
|
Hey @wzyhay, thanks for your response. I've just run Snoopy's test suite in a CentOS 7 (x86_64) Docker container and the Not exactly sure yet what's going on, but by the looks of your Can you double check first that you see the Furthermore, here is the (abbreviated) test case #...
### Test for error(s)
#
EXPECTED_STRING="message_format"
if ! $SNOOPY_CLI conf | fgrep "$EXPECTED_STRING" > /dev/null ; then
snoopy_testResult_fail "Expected string not encountered: '$EXPECTED_STRING'"
fi
# ... I think there is something off with the check itself and the way it works in your system. The only line where (by the data I currently have) the test can fail is this one:
By the looks of it, we've narrowed it down to a single line, but I have no idea why this line of code would fail on your system. If you can figure out how to change this test case to make it work on your system too, let me know and I'll consider including the fix with the next release. I am not sure of how much further help I can be without being able to reproduce the issue myself, but if you have questions, ask away. If it turns out that all this is just some weird setting on your system causing this error (i.e. some weird bash settings, or a missing Best of luck! |
I may have stumbled upon this yesterday while working on #270 - it started happening when "system" Snoopy (so the one already installed into the target directory and enabled) was already loaded into the process(es). I'll see if I can actually reproduce this. |
Checklist before starting to submit this support request
I confirm that:
Issue description
Hi, I am currently using version 2.5.1 of snoopy on Centos7. After compiling and installing, I wanted to verify the soundness of the functionality through testing components, so I manually executed the testing command
./configure --enable-everything && make && make tests
Issue reproduction steps
Expected result
All tests passed
Actual result
I don't know why this test failed or what other impact it would have
The text was updated successfully, but these errors were encountered: