Skip to content
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-15151 cart: Cleanup runaway sessions #14386

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

frostedcmos
Copy link
Contributor

  • Initial version of a '-c' option (cleanup sessions) for self_test. Allows user to terminate all self_test sessions on the specified targets. Intended to be used as a follow-up to an abrupt exit of the previous self_test session.

  • clang format of self_test.c file

Required-githooks: true

Before requesting gatekeeper:

  • Two review approvals and any prior change requests have been resolved.
  • Testing is complete and all tests passed or there is a reason documented in the PR why it should be force landed and forced-landing tag is set.
  • Features: (or Test-tag*) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.
  • Commit messages follows the guidelines outlined here.
  • Any tests skipped by the ticket being addressed have been run and passed in the PR.

Gatekeeper:

  • You are the appropriate gatekeeper to be landing the patch.
  • The PR has 2 reviews by people familiar with the code, including appropriate owners.
  • Githooks were used. If not, request that user install them and check copyright dates.
  • Checkpatch issues are resolved. Pay particular attention to ones that will show up on future PRs.
  • All builds have passed. Check non-required builds for any new compiler warnings.
  • Sufficient testing is done. Check feature pragmas and test tags and that tests skipped for the ticket are run and now pass with the changes.
  • If applicable, the PR has addressed any potential version compatibility issues.
  • Check the target branch. If it is master branch, should the PR go to a feature branch? If it is a release branch, does it have merge approval in the JIRA ticket.
  • Extra checks if forced landing is requested
    • Review comments are sufficiently resolved, particularly by prior reviewers that requested changes.
    • No new NLT or valgrind warnings. Check the classic view.
    • Quick-build or Quick-functional is not used.
  • Fix the commit message upon landing. Check the standard here. Edit it to create a single commit. If necessary, ask submitter for a new summary.

- Initial version of a '-c' option (cleanup sessions) for self_test.
  Allows user to terminate all self_test sessions on the specified targets.
  Intended to be used as a follow-up to an abrupt exit of the previous self_test session.

- clang format of self_test.c file

Required-githooks: true

Signed-off-by: Alexander A Oganezov <alexander.a.oganezov@intel.com>
Copy link

Ticket title is 'DAOS 2.4 - src/cart/crt_self_test_service.c:657 crt_self_test_msg_handler() No self-test buffers available for session '
Status is 'In Progress'
Labels: 'ALCF,scrubbed,triaged'
https://daosio.atlassian.net/browse/DAOS-15151

Comment on lines +977 to +978
if (cleanup_sessions)
close_all_sessions(crt_ctx, srv_grp, endpts, num_endpts);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

session close code

Comment on lines +767 to +770
static void
close_all_sessions(crt_context_t cr_ctx, crt_group_t *srv_grp, struct st_endpoint *st_eps,
int num_eps)
{
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

new close all sessions client function

Comment on lines +1718 to +1720
case 'c':
cleanup_sessions = true;
break;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

new option

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant