-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
JDK16 fixes and workarounds that should make the EA job pass #17053
Conversation
Just pinging a few people to take notice that there are things to fix for JDK16:
I'm planning on creating issues for each "area" but I really don't mind if you create those issues yourself. 😉 |
This workflow status is outdated as a new workflow run has been triggered. 🚫 This workflow run has been cancelled. Failing Jobs - Building ac02b37
|
@famod
|
@Tibor17 thanks, good to know! |
This workflow status is outdated as a new workflow run has been triggered. 🚫 This workflow run has been cancelled. Failing Jobs - Building 5c3095a
|
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building 3f3075e
Full information is available in the Build summary check run. Test Failures⚙️ Gradle Tests - JDK 11 Windows #📦 integration-tests/gradle✖ |
I remember you mentioned that a new xstream version that fixes this problem is in the works, right? |
@geoand I hope things will be better with 1.5 but no clue when that will be released. |
@aloubyansky There is one last problem in the EA job (in my fork): Since I didn't commit my /cc @gsmet Edit: Regular CI is not affected since we currently only run those Maven ITs on JDK 11. |
No objections @famod Thanks! |
…ge/maven-invoker-way
…problem in bootstrapping
This workflow status is outdated as a new workflow run has been triggered. 🚫 This workflow run has been cancelled. Failing Jobs - Building 38d5beb
|
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.
LGTM, I'll let @gsmet in charge of pushing the big green merge button 😉
EA job passed completely in my fork: https://github.com/famod/quarkus/actions/runs/819992102 |
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.
Nice work, thanks a lot for this!
First step for #16195.
See also: https://quarkusio.zulipchat.com/#narrow/stream/187038-dev/topic/Quarkus.20tested.20on.20Java.2016/near/237676424
I tried to divide everything in commits than can be addressed individually later, e.g. when fault-tolerance is fixed that one commit could be reverted.
I think the most controversial commit is the first one with
--add-opens
.After a chat with @aloubyansky I decided to at least make sure it isn't propagated to tests via
MAVEN_OPTS
(which might spawn their ownmvn
subprocesses).I suggest to keep
excludedEnvironmentVariables
permanently because I think we generally don't want that propagation (until further notice).I'm currently testing a
--illegal-access=warn
alternative to that--add-opens
but I'm not convinced it's that much better.For that
tmpdir
commit see #16195 (comment) and #16195 (comment). It's a bit of a mess currently but I didn't see a better solution until something injboss-parent
and/or Surefire changes.