-
Notifications
You must be signed in to change notification settings - Fork 5
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
[1.0] various different signedness warning fixes #625
Conversation
@@ -233,7 +233,7 @@ BOOST_AUTO_TEST_CASE(snapshot_scheduler_old_json) { | |||
unsigned found = 0; | |||
for(const std::filesystem::directory_entry& dir_entry : std::filesystem::directory_iterator(temp / "snapshots")) | |||
found += std::regex_search(dir_entry.path().filename().string(), snapshotfile_regex); | |||
BOOST_REQUIRE_GE(found, 3); | |||
BOOST_REQUIRE_EQUAL(found, 3u); |
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.
The test was originally more sloppy and it's why it was >=3
; I forgot to change this to ==3
after making it more strict. Not a big enough deal to go back to 5.0 to fix this imo
ah crud sorry I got way to trigger happy and forgot to merge in chainbase first |
Note:start |
grabbag of different signedness warning fixes I noticed. I'm fine sending these to main instead, but most/all of these were introduced at the 11th hour before cutting 1.0.0 rc
Needs AntelopeIO/chainbase#53