-
Notifications
You must be signed in to change notification settings - Fork 203
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
Prevent schedule from being reread unnecessarily #3183
Conversation
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.
change looks good but as this was and is a very tricky code area I would favor tests a lot! Feel free to mock as much as needed, especially any potential "sleep" calls.
Codecov Report
@@ Coverage Diff @@
## master #3183 +/- ##
=======================================
Coverage 91.98% 91.98%
=======================================
Files 211 211
Lines 12931 12933 +2
=======================================
+ Hits 11894 11896 +2
Misses 1037 1037
Continue to review full report at Codecov.
|
906dcb3
to
c2363a6
Compare
I added a test |
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.
Perfect
This can happen if a test is finished and the new one hasn't started. (Reproduce by adding a `sleep 10` in basetest.pm after `$self->done()`. The backend will report an empty `$running_test`, and in this case `$current_test_module` should keep its last value. It will also reduce payload of the status posts, because it previously posted the status of *all* tests when `$current_test_module` was empty. This also fixes the issue that results of short tests < 10s are only reported at the end of the job. Related Issues: * https://progress.opensuse.org/issues/58826 * https://progress.opensuse.org/issues/58700 * https://progress.opensuse.org/issues/67972
c2363a6
to
64caa7a
Compare
This can happen if a test is finished and the new one hasn't started.
(Reproduce by adding a
sleep 10
in basetest.pm after$self->done()
.The backend will report an empty
$running_test
, and in this case$current_test_module
should keep its last value.It will also reduce payload of the status posts, because it previously posted
the status of all tests when
$current_test_module
was empty.This also fixes the issue that results of short tests < 10s are only
reported at the end of the job.
Related Issues: