-
-
Notifications
You must be signed in to change notification settings - Fork 314
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
Functional tests do not compile on z/OS #660
Comments
FYI @sophia-guo @vsebe |
Functional tests are using We need to update this and use |
FYI @llxia - this is the issue i was speaking about earlier. |
For system tests we have a parameter defined in top.xml that sets source encoding to
The
We need to have something similar for functional tests too, for them to compile and run on z/OS. May be we could have TestConfig set a global parameter that could be used by all tests? |
I am curious to know why we set |
|
Without changing anything, below is what I observed:
|
Ebcdic conversation is done by Git itself when it checks out code on z/OS. For this, each of the 3 systemtest repos has defined its own .gitattriutes file (e.g. https://github.com/AdoptOpenJDK/openjdk-systemtest/blob/master/.gitattributes) where we define which file should be left alone and which file should be converted. This file is used in the git command, see: https://github.com/AdoptOpenJDK/openjdk-tests/blob/ac0012d53f1223456c4b8dfc9a5a99675aa279ba/systemtest/build.xml#L46 - this ensures that text files are converted, by git, into ebcdic. In the case of functional tests, I believe we are getting lucky in the case where the tests are running. |
Even in system test, not all files are converted to ebcdic:
This may explain in system test console output, we see following:
|
Yes, I have seen these special characters in the job output as well, I am not sure if it's because some files are not converted in ebcdic (because if not, we would see tests not compiling / running). For example, the following seems to be a z/OS Ant bug:
Note also that, text files do not need to be in 'ebcdic' format for the new z/OS to process them either. You can transfer ascii files on a z/OS machine, and open them. It's the JVM that requires texts files to be in ebcdic format while on z/OS. |
The files are correctly tagged after git clone. Looks the files are not tagged after the |
Thanks for @vsebe help! @Mesbah-Alam, @renfeiw and I had the discussion. We actually have mutiple issues on zos. We will work on the following:
|
Just for the record, However, in a couple of our tests, we do ant |
The Tap file issue should be fixed: #722 |
Part of the problem is being fixed upstream, are there any other actions that need to be completed before we close this? |
Above two issues are fixed. Also as Shelley mentioned, compilation issue is being fixed upstream. I will close this issue. Once we get new SDK with the fix from upstream, we can re-test and open issue as needed. |
When functional teat compilation is attempted on z/OS, we get the following type of errors:
I suspect this is due to the fact that we are not supplying the correct encoding value in the build.xml files of the functional tests.
We need to define what file encoding to be used for Java source files for tests as we do in case of system tests.
Build link: https://hyc-runtimes-jenkins.swg-devops.com/view/Test_functional/job/Test-sanity.functional-JDK11-zos_390-64_cmprssptrs/9/console
The text was updated successfully, but these errors were encountered: