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

Revert "Revert "Mark VM as exitting earlier"" #9864

Merged
merged 1 commit into from
Jun 12, 2020

Conversation

gacholio
Copy link
Contributor

Reverts #9829

@gacholio gacholio merged commit 2b740f6 into master Jun 12, 2020
@gacholio gacholio deleted the revert-9829-revert-9630-exit branch June 12, 2020 16:26
@pshipton
Copy link
Member

pshipton commented Jun 12, 2020

@gacholio what's going on, this change introduces hang on exit problems for all platforms.

@gacholio
Copy link
Contributor Author

It only affects a single test (on every platform, not just windows), and the fix is coming in a PR in a few minutes. There was no need to re-review the existing code.

@pshipton
Copy link
Member

pshipton commented Jun 12, 2020

ok, but there is a timing hole here. If the new PR doesn't get merged today then the problem gets re-exposed in the builds tonight and on the weekend. The better approach is to include the "revert revert" commit in the new PR, separately from the latest fix commit, so they are merged together. Keeping it separated in two commits allows the reviewer to only look at the latest fix.

@gacholio
Copy link
Contributor Author

I was unable to figure out how to do that. This change was in the builds for a week before the problem was detected, so there's no issue with having it in for a short while unfixed.

@pshipton
Copy link
Member

In Eclipse, make local branch, open the history, find the revert commit and select revert on it to create a new commit in your local branch. Then make the changes on top in a new commit as usual.

@gacholio
Copy link
Contributor Author

Thanks, I'll keep it in mind for the next time.

@pshipton
Copy link
Member

I believe the problem causes some timeouts in the builds running at AdoptOpenJDK (not sure why not at OpenJ9). They weren't noticed until triaging for the 0.21 release Milestone 1, the revert didn't make M1. My point is that now Adopt nightly builds may be failing again until the fix is reviewed and merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants