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/rbd_mirror: "use of uninitialised value" valgrind warning #19437
Conversation
The `on_call` context serves as a barrier and should be completed after the `on_start_ctx` context is assigned. The warning was observed sporadically e.g. by repeating WaitingOnNonLeaderAcquireLeader test under valgrind. Signed-off-by: Mykola Golub <to.my.trociny@gmail.com>
Should this target mimic-dev1? (Is the failure in http://pulpito.ceph.com/sage-2017-12-04_18:01:15-rbd-mimic-dev1-distro-basic-smithi/) |
@liewegas The fix is for unittest_rbd_mirror, which we do not run on teuthology, only on jenkins. And I only stepped on it running locally under valgrind. So not sure we need to backport this. As for failures you mentioned, actually the test scripts succeeded in all the cases but the teuthology failed due to the cluster health check failed. It does not look rbd related to me. |
@liewegas One of the failures [1] was due to an osd crash:
And some log entries before the crash that look relevant:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
The
on_call
context serves as a barrier and should be completedafter the
on_start_ctx
context is assigned.The warning was observed sporadically e.g. by repeating
WaitingOnNonLeaderAcquireLeader test under valgrind.
Signed-off-by: Mykola Golub to.my.trociny@gmail.com