-
Notifications
You must be signed in to change notification settings - Fork 900
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
Restart launcher after bgw_scheduler_restart #7594
base: main
Are you sure you want to change the base?
Conversation
If the scheduler is not restarted, it can affect other tests, so restarting it at the end of the test.
1c15c15
to
75ef8ff
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7594 +/- ##
==========================================
+ Coverage 80.06% 82.30% +2.24%
==========================================
Files 190 238 +48
Lines 37181 44139 +6958
Branches 9450 11101 +1651
==========================================
+ Hits 29770 36330 +6560
- Misses 2997 3425 +428
+ Partials 4414 4384 -30 ☔ View full report in Codecov by Sentry. |
|
||
-- We need to restart the launcher as well to read the reset | ||
-- configuration or it will affect other tests. | ||
CALL ts_terminate_launcher(); |
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.
It says it will restart the launcher, but then "terminate" is called? Is this correct?
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.
Yes, the launcher restarts automatically after being terminated. It is also verified later in the test, just to make sure that the launcher is actually running when it should.
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.
Ok, I would recommand clarifying this in the comment for future understanding.
If the scheduler is not restarted, it can affect other tests, so restarting it at the end of the test. Also moving some validation queries to later in the test to make sure that all background workers have restarted properly and read the configuration.
Disable-check: force-changelog-file