-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
unixPB: Install gcc 10.3 into /usr/local/gcc10 #2420
Conversation
e54bbec
to
86175f5
Compare
Signed-off-by: Stewart X Addison <[email protected]>
macos check failure was a connection timeout downloading |
whoops, I didn't consider the GitHub check when doing #2405 . Thanks for bringing it up :-) |
ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/gcc_10/tasks/main.yml
Show resolved
Hide resolved
ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/gcc_10/tasks/main.yml
Show resolved
Hide resolved
Changes look good in VPC, although there's a problem showing up when it tries to run the tests - however it does not look related to this PR. https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/1366/OS=CentOS6,label=vagrant/console
|
Signed-off-by: Stewart X Addison <[email protected]>
ansible_lint check is now failing regardless of this PR, so should not hold things up ... |
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 - Looking at VPC-1366, there was a successful JDK17 build on CentOS6/x84, using GCC-10. The testing failed, and we're looking more into that, however I don't think that is related to this PR. Same case with the Linter, that appears to be failing due to something other than the syntax of this PR.
I think all the github check failures are now determined to be unrelated to this PR. I've got a final VPC run at https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/1370 and if that's ok (other than the test execution failure which also appears unrelated to this PR - https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/1367 is a run from the master branches to check if it happens there too) then I'll merge. |
@Willsparker Can you re-review please? I've made a change to I've edited the VPC job to explicitly clone from my branch to test this. |
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
Chnage to |
Converting this back to draft as the MBCS test is failing to pass when the build is performed with GCC10
|
Problem with the MBCS test on JDK17 will be resolved by eclipse-openj9/openj9#14212. [VPC 1381] worked on JDK8 with GCC 10.3 so I'm comfortable that this is now safe so I will merge :-) |
Fixes #2386
Signed-off-by: Stewart X Addison [email protected]
Checklist
Change to testVPC.sh was due to a bug when building later JDKs which made the process pick up the
static-libs
directory instead of the JDK, which causd a test failure (described in the comments below)