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

Add test for no failed Systemd units #3583

Merged
merged 1 commit into from
Sep 11, 2024
Merged

Conversation

sairon
Copy link
Member

@sairon sairon commented Sep 11, 2024

Test that systemctl reports no failed units at the end of the basic test.

Summary by CodeRabbit

  • Tests
    • Introduced a new test to verify that there are no failed system units, enhancing the robustness of the testing framework.

Test that systemctl reports no failed units at the end of the basic test.
@sairon sairon added the build Build and CI related issues label Sep 11, 2024
@sairon sairon requested a review from agners September 11, 2024 15:40
Copy link

coderabbitai bot commented Sep 11, 2024

Walkthrough

Walkthrough

The changes introduce a new test function, test_systemctl_check_no_failed, to the testing suite. This function is designed to verify that there are no failed units reported by the system by checking the output of the systemctl command. The test ensures that the output indicates "0 loaded units listed," enhancing the overall test coverage related to system unit failures.

Changes

Files Change Summary
tests/smoke_test/test_basic.py Added test_systemctl_check_no_failed(shell) to check for failed system units.

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 93ac046 and 4683e48.

Files selected for processing (1)
  • tests/smoke_test/test_basic.py (1 hunks)
Additional comments not posted (1)
tests/smoke_test/test_basic.py (1)

75-78: LGTM!

The new test function test_systemctl_check_no_failed is a valuable addition to the test suite. It correctly checks for failed systemd units by running the appropriate command and asserting the expected output.

The function is well-implemented and enhances the robustness of the testing framework by identifying potential issues related to systemd unit failures.

The code changes are approved.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@Impact123
Copy link

Checking the exit code of systemctl --failed --quiet or the line count of systemctl --failed --legend=false might be more reliable in the long-term in case the text is ever changed in the future.


@pytest.mark.dependency(depends=["test_init"])
def test_systemctl_check_no_failed(shell):
output = shell.run_check("systemctl --no-pager -l list-units --state=failed")
Copy link
Member

Choose a reason for hiding this comment

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

Threre is --output=json, but not sure if it makes for a better test 🤔 Either way works for me.

@sairon sairon merged commit 5d164b1 into dev Sep 11, 2024
2 checks passed
@sairon sairon deleted the add-test-for-no-failed-units branch September 11, 2024 21:30
@sairon sairon mentioned this pull request Sep 26, 2024
@sairon sairon mentioned this pull request Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Build and CI related issues cla-signed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants