Skip to content

DAOS-19360 test: Handle abrupt EOF - #18819

Open
frostedcmos wants to merge 1 commit into
masterfrom
frostedcmos/DAOS-19360
Open

DAOS-19360 test: Handle abrupt EOF#18819
frostedcmos wants to merge 1 commit into
masterfrom
frostedcmos/DAOS-19360

Conversation

@frostedcmos

Copy link
Copy Markdown
Contributor
  • Handle abrupt EOF in logs; happens if server is SIGKILL-ed

Steps for the author:

  • Commit message follows the guidelines.
  • Appropriate Features or Test-tag pragmas were used.
  • Appropriate Functional Test Stages were run.
  • At least two positive code reviews including at least one code owner from each category referenced in the PR.
  • Testing is complete. If necessary, forced-landing label added and a reason added in a comment.

After all prior steps are complete:

  • Gatekeeper requested (daos-gatekeeper added as a reviewer).

- Handle abrupt EOF in logs; happens if server is SIGKILL-ed

Signed-off-by: Alexander A Oganezov <alexander.oganezov@hpe.com>
@frostedcmos
frostedcmos requested review from a team as code owners August 7, 2026 21:05
@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown

Ticket title is 'Functional Hardware Large/launch/functional_hardware_large - Error while running cart_logtest.py IndexError: list index out of range '
Status is 'Open'
Labels: 'ci_master_daily,triaged'
https://daosio.atlassian.net/browse/DAOS-19360

warnings_strict = False
warnings_mode = False
server_shutdown = False
abrupt_eof = getattr(self._li, 'truncated_eof', False)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Is the getattr necessary? Since we define self.truncated_eof = False in __init__ it seems it would always be defined?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants