-
Notifications
You must be signed in to change notification settings - Fork 301
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
DAOS-15643 test: Enable dfuse register cleanup model #14215
Merged
Merged
Changes from all commits
Commits
Show all changes
27 commits
Select commit
Hold shift + click to select a range
8d680c5
DAOS-15643 test: Enable dfuse register cleanup model
phender 57a430a
Merge branch 'master' into pahender/DAOS-15643
phender e84c963
Merge branch 'master' into pahender/DAOS-15643
phender 85c9925
Additional file changes.
phender 06652cf
Merge branch 'master' into pahender/DAOS-15643
phender 7176e50
Moving changhes for DAOS-15616 into its own PR.
phender 9761177
Revert copyright updates for unchanged files.
phender 0cf2ecd
Merge branch 'master' into pahender/DAOS-15643
phender ecb1d9d
Merge with blocking changes.
phender cfae3fd
Merge branch 'master' into pahender/DAOS-15643
phender 7a31d3d
Merge branch 'master' into pahender/DAOS-15643
phender b2b40f5
Test fixes.
phender 7cb3d4a
Fix erasurecode/rebuild_fio.py
phender ee96567
EcodFioRebuild cleanup.
phender 298a360
Merge branch 'master' into pahender/DAOS-15643
phender 344d1e2
Merge branch 'master' into pahender/DAOS-15643
phender 77a6ea2
Fix failing tests.
phender 1297b46
Applying feedback.
phender 3ca23d8
Merge branch 'master' into pahender/DAOS-15643
phender 70bac35
Fix class rename in previous merge.
phender beabd59
Merge branch 'master' into pahender/DAOS-15643
phender 5806cc8
Fix test failures.
phender 239aa88
Merge branch 'master' into pahender/DAOS-15643
phender 201ac08
Reinstating the run_ior_with_pool(stop_dfuse=True) argument.
phender edf2078
Remove uneccessary changes.
phender d5dfc6d
Cleanup changes.
phender fa1bd6f
Fix run_ior_with_pool dfuse stop.
phender File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Sorry to ask such a high level question when you're so close to getting this working but why is
start_dfuse
a function, not a method on the DFuse class?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.
IMO
start_dfuse
is a stepping stone between where we are and where we want to be. That function already exists before this PR. We could look at changing behavior todfuse.start
but it would require a little more refactoring that I think could be handled later.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.
It could, but if we're making a interface change that affects the entire suite isn't it better to make that change once rather than planning a second wholesale change as well?
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.
I see what you mean. It depends on how complicated it is now vs later. I'm talking with @phender about this now.
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.
I obviously don't know the details but overall one change is better than two. I am really glad to see this kind of work progressing though.