This repository was archived by the owner on Feb 17, 2025. It is now read-only.
Conversation
vo-nil
approved these changes
May 24, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, if we choose g++ Relase build within Nix environment, tests using
<boost/test/included/unit_test.hpp>andBOOST_DATA_TEST_CASEare failing due to heap memory issues (valgrind report is attached below). Technically, tests themselves pass, but process still fails on exit.Made some expriments. Turned out the issue is gone either if we use
<boost/test/unit_test.hpp>instead (header for linked Boost setting) or disable linking flags. In other words,<boost/test/included/unit_test.hpp>and linking toBoost::unit_test_frameworkare incompatible in this case.Since in crypto3 we have more
<boost/test/unit_test.hpp>usage, I changed tests to use this header.Valgring Report