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
new memory leaks detected #2113
Comments
@KurtMi Can you please have a look? This seems to be a rather strange issue, since the tests for commit 1c4a21b already ran successfully. I disabled the test for the |
right. i failed to mention: the docker image changed because it was a new month and hence a fresh build was issued. Since unstable does not really 'pin' versions something probably changed upstream. |
|
The plugin test ( |
I think for now it is ok. In my opinion the problem is not semlock, it is the test suite that has no uniform way to exclude stuff. |
closed via #2117 |
Builds on master started to fail on unstable + valgrind combinations due to a new memory leak.
It seems to be related to the semlock plugin and the testkdb_allplugins test.
https://build.libelektra.org/jenkins/job/libelektra/job/master/138/artifact/artifacts/debian-unstable-full/DynamicAnalysis.xml
The text was updated successfully, but these errors were encountered: