-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
harness: consume output of balancer when running tests #1221
harness: consume output of balancer when running tests #1221
Conversation
WalkthroughThe recent update to the Changes
Assessment against linked issues
Poem
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? TipsChatThere are 3 ways to chat with CodeRabbit:
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 as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
Do you mean something like this? I'm aware it doesn't log it back out to the parent process quite yet. Also, I know it makes some of the tests to fail for now. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1221 +/- ##
================================================
+ Coverage 61.4906% 61.7090% +0.2184%
================================================
Files 115 115
Lines 9338 9467 +129
Branches 1145 1152 +7
================================================
+ Hits 5742 5842 +100
- Misses 3596 3625 +29 ☔ View full report in Codecov by Sentry. |
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.
crates/harness/src/test_runner.rs
Outdated
|
||
let _stdout = child.stdout.take().expect("Failed to capture stdout."); | ||
let _stderror = child.stderr.take().expect("Failed to capture stderror."); |
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 stdout and stderr of the child process are being captured but not used. This could lead to confusion or bugs if the intention was to handle these streams later. It's important to either implement the handling of these streams or remove the capture if it's unnecessary.
The captured stdout and stderr are not being re-emitted. This needs to be addressed to meet the PR objectives. The code should be modified to conditionally re-emit these logs based on the --nocapture
flag.
The test test_balancer_restart
does not seem to verify the new behavior related to stdout and stderr capturing. Additional tests should be added to ensure that the capturing and conditional re-emission of logs are working as intended.
@Victor-M-Giraldo If it prevents stdout and stderr from being logged to the console, yeah. This isn't really enough for me to give meaningful feedback. |
Do you think you might have some time tomorrow anywhere between 9-12 to join a call and help me out with this? I know the task should be pretty easy, but i'm having some trouble with it. |
Yeah I got time at like 10am |
That works. Thank you. |
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.
Review Status
Actionable comments generated: 0
Configuration used: CodeRabbit UI
Files selected for processing (1)
- crates/harness/src/test_runner.rs (3 hunks)
Files skipped from review as they are similar to previous changes (1)
- crates/harness/src/test_runner.rs
closes #1188