Skip to content
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

[WFCORE-6732] WildFlyRunner doesn't call tearDown and completed ServerSetupTasks if a later one fails in setup #6017

Merged
merged 1 commit into from
Jun 5, 2024

Conversation

gaol
Copy link
Contributor

@gaol gaol commented May 29, 2024

Issue: https://issues.redhat.com/browse/WFCORE-6732

Not sure if a test case needs to be added and where to add if so, please let me know :)

@github-actions github-actions bot added the deps-ok Dependencies have been checked, and there are no significant changes label May 29, 2024
Comment on lines 195 to 199
if (setupException == null) {
super.run(notifier);
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Before this change, if an AssumptionViolatedException gets thrown, the super.run(notifier); was executed. Now, we are introducing a change here. I'm not familiar with JUInit runners, are there any side effects?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO, it won't introduce a change here. With the change, the super.run(notifier) will also be executed when AssumptionViolatedException was thrown from runSetupTasks(), the setupException is null in that case.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ups, right @gaol , apologies, I made a mistake with this

@yersan yersan added the ready-for-merge This PR is ready to be merged and fulfills all requirements label Jun 5, 2024
@yersan yersan merged commit ae21704 into wildfly:main Jun 5, 2024
11 of 12 checks passed
@yersan
Copy link
Collaborator

yersan commented Jun 5, 2024

Thanks @gaol

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deps-ok Dependencies have been checked, and there are no significant changes ready-for-merge This PR is ready to be merged and fulfills all requirements
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants