-
Notifications
You must be signed in to change notification settings - Fork 304
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-15744 ddb: Fixes for Coverity Issues #14275
Conversation
Ticket title is 'Resolve DDB Coverity Issues' |
2555532 2555534 2555543 2555544 2555546 2555540 2555528 2555522 2555521 2555518 Also added 'ddb' to VALID_COMPONENTS for jira query. After moving ddb into utils dir 'ddb' isn't automatically a valid component. Required-githooks: true Signed-off-by: Ryon Jensen <[email protected]> Skip-func-hw-test: true
2555532 2555534 2555543 2555544 2555546 2555540 2555528 2555522 2555521 2555518 Also added 'ddb' to VALID_COMPONENTS for jira query. After moving ddb into utils dir 'ddb' isn't automatically a valid component. Required-githooks: true Signed-off-by: Ryon Jensen <[email protected]> Skip-func-hw-test: true
d94592d
to
85e2c10
Compare
Required-githooks: true Signed-off-by: Ryon Jensen <[email protected]> Skip-func-hw-test: true
I'm not sure why the Jira Report is still failing. I added 'ddb' as a VALID_COMPONENT. |
…rityFixes.DAOS-15744 Required-githooks: true Test-tag: ddb_cmd
Test stage Functional on EL 8.8 completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-14275/4/execution/node/1167/log |
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 change seems fine for me. Not sure whether the -DER_BUSY error from DDB test cases are potentially related with the changes or not, although I cannot establish the relationship between them.
Test stage Functional on EL 8.8 completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-14275/5/execution/node/479/log |
…rityFixes.DAOS-15744 Test-tag: ddb_cmd
I'm not sure what the test failures from earlier runs were caused by, but the last couple runs have passed. I believe this is ready to land. |
is test-tag appropriate here? no other PR tests are affected or execute the ddb core code? |
ddb is a standalone executable. Nothing else uses it. |
fail_msg("Test not setup correctly"); | ||
return -DER_UNKNOWN; |
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 understand this is just test code, but DER_UNKNOWN is not friendly for debugging or triaging purposes. please consider changing that in a follow on
fail_msg("Test not setup correctly"); | ||
return -DER_UNKNOWN; |
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.
ditto
char *pool_uuid = "12345678-1234-1234-1234-123456789012"; | ||
int mkdir_result; | ||
|
||
if (strlen(tctx->dvt_pmem_file) == 0) { | ||
char dir[64] = {0}; | ||
|
||
sprintf(dir, "/mnt/daos/%s", pool_uuid); |
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 think we should also use snprintf here
2555532
2555534
2555543
2555544
2555546
2555540
2555528
2555522
2555521
2555518
Required-githooks: true
Signed-off-by: Ryon Jensen [email protected]
Skip-func-hw-test: true
Before requesting gatekeeper:
Features:
(orTest-tag*
) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.Gatekeeper: