We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This project has a czmq4 branch set up to test compilations against both our current standard fork of czmq-v3.0.2 and the upstream czmq4. Builds of the latter fail with many "definitely leaked" entries in valgrind, see e.g. https://travis-ci.org/jimklimov/fty-metric-composite/builds/236341368 and https://travis-ci.org/jimklimov/fty-metric-composite/builds/236341368 in particular.
czmq4
This is a blocker for updating the baseline of 42ity project to use only the maintained upstream czmq.
As can be seen in the comparison at https://github.com/42ity/fty-metric-composite/compare/master...czmq4?expand=1 there is no C/C++ codebase change in the branch, just added recipes to try both CZMQ versions in different runs.
The text was updated successfully, but these errors were encountered:
Fixed by zeromq/czmq#1675
Sorry, something went wrong.
jimklimov
No branches or pull requests
This project has a
czmq4
branch set up to test compilations against both our current standard fork of czmq-v3.0.2 and the upstream czmq4. Builds of the latter fail with many "definitely leaked" entries in valgrind, see e.g. https://travis-ci.org/jimklimov/fty-metric-composite/builds/236341368 and https://travis-ci.org/jimklimov/fty-metric-composite/builds/236341368 in particular.This is a blocker for updating the baseline of 42ity project to use only the maintained upstream czmq.
As can be seen in the comparison at https://github.com/42ity/fty-metric-composite/compare/master...czmq4?expand=1 there is no C/C++ codebase change in the branch, just added recipes to try both CZMQ versions in different runs.
The text was updated successfully, but these errors were encountered: