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

Failures running Javac for DDR_Test #4397

Closed
andrewcraik opened this issue Jan 23, 2019 · 9 comments
Closed

Failures running Javac for DDR_Test #4397

andrewcraik opened this issue Jan 23, 2019 · 9 comments

Comments

@andrewcraik
Copy link
Contributor

andrewcraik commented Jan 23, 2019

PR builds are failing regularly trying to run the DDR_Tests. Failures report a compile step failed related to javac with cryptic messages similar to:

10:48:33 
10:48:33 Total time: 1 second
10:48:33 makefile:82: recipe for target 'compile' failed
10:48:33 make: *** [compile] Error 1
[Pipeline] }

see https://ci.eclipse.org/openj9/job/PullRequest-Sanity-JDK11-aix_ppc-64_cmprssptrs-OpenJ9/85/console

@andrewcraik
Copy link
Contributor Author

@DanHeidinga @pshipton FYI. @keithc-ca could this be related to any of the recent DDR changes? Not trying to place blame just trying to figure out if this is a problem with javac or a problem with DDR - any thoughts?

@andrewcraik
Copy link
Contributor Author

FYI @0xdaryl and @liqunl due to interest on the OpenJ9 triage slack channel

@DanHeidinga
Copy link
Member

DanHeidinga commented Jan 23, 2019

I think I've seen it on non-DDR builds as well - looking for a link now.

Similar failure for IllegalAccessError_for_protected_method in https://ci.eclipse.org/openj9/job/PullRequest-Sanity-JDK8-osx_x86-64_cmprssptrs-OpenJ9/65/console

@gacholio
Copy link
Contributor

Could the problem here be that the javac is the one just built from the PR. Any flakiness in the code could case the compiler to fail before getting to actual testing (which is a serious error that we continue to propagate).

@keithc-ca
Copy link
Contributor

Yes, I think the test code is being compiled with the brand new JDK. I agree it's serious if javac in that JDK doesn't work.

@pshipton
Copy link
Member

I think we found the culprit
#4017

@DanHeidinga
Copy link
Member

@pshipton Is this fixed now that #4017 has been merged? If so we should close it out.

@AdamBrousseau
Copy link
Contributor

No, 4017 is what caused this issue. I am still determining why though. I would like to figure it out so we can get in a fix rather than simply reverting the change.

@DanHeidinga
Copy link
Member

@AdamBrousseau What's the downside of reverting now and re-introducing the change later? Currently PR builds are broken which affects all PRs.

AdamBrousseau added a commit to AdamBrousseau/openj9 that referenced this issue Jan 24, 2019
This reverts commit 0ae098f.
Issue eclipse-openj9#4397
Signed-off-by: Adam Brousseau <adam.brousseau88@gmail.com>
AdamBrousseau added a commit to AdamBrousseau/openj9 that referenced this issue Jan 24, 2019
- Since JAVA_BIN etc are set when the test file is loaded,
  we need to load on the node where the tests will run.
  This is due to the absolute PATH used. Since the WORKSPACE
  differs from the setup machine and the agents, setting
  JAVA_BIN on the worker would refer to a PATH that didn't
  exist on the agent.

Fixes eclipse-openj9#4397
[skip ci]

Signed-off-by: Adam Brousseau <adam.brousseau88@gmail.com>
Yuehan-Lin pushed a commit to Yuehan-Lin/openj9 that referenced this issue Feb 5, 2019
- Since JAVA_BIN etc are set when the test file is loaded,
  we need to load on the node where the tests will run.
  This is due to the absolute PATH used. Since the WORKSPACE
  differs from the setup machine and the agents, setting
  JAVA_BIN on the worker would refer to a PATH that didn't
  exist on the agent.

Fixes eclipse-openj9#4397
[skip ci]

Signed-off-by: Adam Brousseau <adam.brousseau88@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants