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

Failing test on Raspberry Pi: Server is able to generate a stack trace on selected systems #3546

Closed
niemda opened this issue Oct 9, 2016 · 2 comments

Comments

@niemda
Copy link

@niemda niemda commented Oct 9, 2016

I just compiled redis 3.2.4 on Raspberry Pi (3rd gen, raspbian jessie w/o any custom packages) and have one failing test.

!!! WARNING The following tests failed:

*** [err]: Server is able to generate a stack trace on selected systems in tests/integration/logging.tcl
expected stack trace not found into log file
Cleanup: may take some time... OK
Makefile:215: recipe for target 'test' failed
make[1]: *** [test] Error 1
make[1]: Leaving directory '/home/pi/compile/redis-3.2.4/src'
Makefile:6: recipe for target 'test' failed
make: *** [test] Error 2

My raspberry reports this:

pi@blackbox-dev0:~ $ cat /etc/debian_version
8.0
pi@blackbox-dev0:~ $ uname -a
Linux blackbox-dev0 4.4.21-v7+ #911 SMP Thu Sep 15 14:22:38 BST 2016 armv7l GNU/Linux
pi@blackbox-dev0:~ $
@xhuacmer
Copy link

@xhuacmer xhuacmer commented Dec 29, 2020

Is there any solution for this problem? I want to know the what impact this problem.

@oranagra
Copy link
Contributor

@oranagra oranagra commented Dec 29, 2020

this is a real old version of redis, and the issue is already resolved.
please upgrade to redis 6.0 which should be fine in that respect.
or if your only problem is the failing test, just skip or delete that test.
this failed test does not indicate a problem in redis, just meant that crash report logs may be missing some info.

@oranagra oranagra closed this Dec 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants