-
Notifications
You must be signed in to change notification settings - Fork 306
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-6903 Test: Fix regression in NVMe health test code. (#4832) #5240
Conversation
Ci Test result can be found from https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-5240/1/artifact/Functional_Hardware_Medium/nvme/ |
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.
lgtm
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.
LGTM
@ravalsam , can we run all func tests? you can skip unit testing |
I was mention not to run all tests when we Cherry-pick instead only which impacts the tests. is that changed now? NVMe IO has been worked out in another PR because of getting issue in the DAOS side and that was the reason I did not ran part of Ci in this PR. |
Signed-off-by: Samir Raval <samir.raval@intel.com>
4c5de4e
to
dbed2f0
Compare
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.
LGTM. No errors found by checkpatch.
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.
LGTM.
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.
LGTM
Quick-Functional: true
Test-tag: csum_error_log nvme_health der_enospace
Signed-off-by: Samir Raval samir.raval@intel.com