-
Notifications
You must be signed in to change notification settings - Fork 107
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
Additional Unit test Fix for 12107 #12111
Additional Unit test Fix for 12107 #12111
Conversation
@amaltaro this is all fixed here. I am merging this PR so that others do not wait for their broken unit tests. Please leave any comments in a post merge the review if you have any. |
@todor-ivanov did you merge it by mistake? I don't understand why you would not wait for Jenkins CI to do its job and come back with the result(!) |
hi @amaltaro no I did not merge it by mistake ... .it was a simple fix and the tests were successful, and I did not want to stop other peoples' work with a failing unit test. |
Because I have no idea why would jenkins claim it as failed... since this was exactly the test that this PR fixes and I have tested even before I created the PR. Here is what I get in my local run for this unit test:
|
and you can also see this very same test have changed from failure to success in the PR which @anpicci is working: Here is the report from Andrea's PR jenkins actions, which I triggered upon merging this test:
I do not think we have anything to do here. I only wonder if we can force Jenkins to run the tests again on an already merged PR .... |
@todor-ivanov now it has been merged already and we know everything is working as expected, as you retrieved this information from Andrea. For future occasions though, please give Jenkins the 15-20min to run its job and do not merge anything before Jenkins tests come back and usual tests are successful. We know that it is not 100% of the time that Jenkins and localhost unit tests match, so it's always wise to wait for Jenkins. |
Fixes #12037
Status
ready
Description
With PR #12108 we forgot to fix one Unit test and remove tow commented lines. The current PR addresses this.
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
#12108
External dependencies / deployment changes
No