-
Notifications
You must be signed in to change notification settings - Fork 23
smoke: fix shutdown test for service mode #475
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
base: main
Are you sure you want to change the base?
Conversation
📝 WalkthroughWalkthroughAdds a new 📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
🧰 Additional context used📓 Path-based instructions (1)**/*.sh⚙️ CodeRabbit configuration file
Files:
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
🔇 Additional comments (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In @smoke/_init.sh:
- Around line 229-230: The journalctl check is unreliable because it reads the
last 2 system-wide entries; change the check that currently uses "journalctl -n
2 | grep -q 'Deactivated successfully'" to query the grout service unit (use the
service/unit name) and increase the number of lines searched (e.g., -n 50) so
the grep reliably finds "Deactivated successfully"; keep the existing fail
invocation (fail "shutdown was not successful") but update the journalctl
invocation reference in the script to include --unit=<grout-unit-name> (or -u
<grout-unit-name>) and a larger -n value.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
smoke/_init.shsmoke/shutdown_test.sh
🧰 Additional context used
📓 Path-based instructions (1)
**/*.sh
⚙️ CodeRabbit configuration file
**/*.sh: - Don't bother about unquoted shell variables.
Files:
smoke/_init.shsmoke/shutdown_test.sh
🧬 Code graph analysis (1)
smoke/shutdown_test.sh (1)
smoke/_init.sh (1)
shutdown_grout(223-234)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
- GitHub Check: build-and-tests (gcc-13, none, debugoptimized, ubuntu-24.04, -Dfrr=enabled, false)
- GitHub Check: build-and-tests (clang-15, none, debugoptimized, ubuntu-22.04, false)
- GitHub Check: build-and-tests (gcc-14, address, debug, ubuntu-24.04, -Dfrr=enabled, true)
- GitHub Check: build-and-tests (clang-18, none, debugoptimized, ubuntu-24.04, false)
- GitHub Check: build-and-tests (clang-16, none, debugoptimized, ubuntu-24.04, false)
- GitHub Check: rpm
- GitHub Check: deb
🔇 Additional comments (2)
smoke/shutdown_test.sh (1)
34-34: LGTM!Clean delegation to the centralized
shutdown_groutfunction.smoke/_init.sh (1)
219-221: LGTM!Correct approach to retrieve the main PID of a systemd-managed grout instance.
When Grout was working as a systemd service (rather than starting again for each test), shutdown_test did not work as expected.
5c44cc9 to
16f48ee
Compare
When Grout was working as a systemd service (rather than starting again for each test), shutdown_test did not work as expected.
Summary by CodeRabbit
New Features
Refactor
✏️ Tip: You can customize this high-level summary in your review settings.