libhashkit2 yml workflow#175
Closed
BridgerVoss wants to merge 1 commit into
Closed
Conversation
BridgerVoss
force-pushed
the
libhashkit
branch
2 times, most recently
from
b18e4db to
9721eae
Compare
Author
|
retest this please jenkins |
aidangarske
reviewed
Jul 9, 2025
Member
There was a problem hiding this comment.
Actually @BridgerVoss, it looks like you and Paul have conflicting PR's. Can we close in favor of #195?
Author
@aidangarske yeah that's fine as long TEST_RESULT=2 is okay as that is what Makefile returns on force fail in #195 . Doesn't really matter logic wise just didn't know if we want that for consistency or not |
Member
|
Okay ya I see that I will fix it in 195 |
Author
|
continued in #195 |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Added wolfProvider tests for libhashkit2 which is a part of the bigger repository, libmemcached.