Pre-shared-memory support test execution: No code changes involved. #611
Conversation
This file contains 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
✅ Deploy Preview for splinterdb canceled.
|
Update test.sh comment, to re-fire CI jobs.
gapisback
force-pushed
the
agurajada/pre-shmem-SHA-2fb4d7c9
branch
from
caf0116 to
49cf11c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change-set resets SHA back to
2fb4d7c9, which is the commit just prior to the 1st commit that added shared memory support to SplinterDB, i.e., prior to this one:This PR is created to trigger CI-jobs so we get a baseline of all testing coverage existing in Splinter code base before the large expansion and new test-coverage added as part of Shared memory support dev work.