-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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: fix test failures in ActionEventInterceptorTest #8938
test: fix test failures in ActionEventInterceptorTest #8938
Conversation
``` Error: Failures: Error: ActionEventInterceptorTest.testInterceptComplete:247 Error: ActionEventInterceptorTest.testInterceptException:261 Error: ActionEventInterceptorTest.testInterceptStartAsync:234 expected:<Starting VM[. Id: 0 Name: null]> but was:<Starting VM[]> ```
Not sure if it fixes the issue, let's wait for the results of github actions |
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.
clgtm and fixes the issue locally for me.
great, thanks @DaanHoogland I kicked the build 3 times, all succeeded. https://github.com/apache/cloudstack/actions/runs/8734995428/job/23976479820?pr=8938 |
marked as "ready for review" as it fixes the failure with build CI |
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.
clgtm
* test: fix test failures in ActionEventInterceptorTest ``` Error: Failures: Error: ActionEventInterceptorTest.testInterceptComplete:247 Error: ActionEventInterceptorTest.testInterceptException:261 Error: ActionEventInterceptorTest.testInterceptStartAsync:234 expected:<Starting VM[. Id: 0 Name: null]> but was:<Starting VM[]> ``` * Update 8938: move CallContext.unregister as well
This fixes test failures in some PRs against main/4.20 branch
Description
This PR...
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?