-
Notifications
You must be signed in to change notification settings - Fork 11
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
test: Add coverage for runner health monitor #39
Conversation
Codecov ReportAttention: Patch coverage is
📢 Thoughts on this report? Let us know! |
There might be a timing issue here, I'll take a closer look tomorrow. |
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.
Suggested how to make this hopefully a bit more testable. LMK WDYT
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.
Much cleaner now 👍
panic(fmt.Errorf("failed to terminate runner process: %v", err)) | ||
} | ||
logs.Debug("Stopped monitoring runner health") | ||
logs.Warn("Found runner unresponsive too many times, terminating runner...") |
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.
Since this no longer does the termination, we could move this log to where it's actually terminated
Makefile
Outdated
test-uncached: | ||
go test -count=1 ./... |
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.
What does this do? Could we add a 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.
Added while testing but not really useful, removed.
Edit: To elaborate, Go caches successful test results by default and I was checking if there were any timing issues by running the same tests multiple times. No need now that this was all refactored.
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.
🚀
https://linear.app/n8n/issue/PAY-2247/write-tests-for-launcher