| java OpenJDK | |
|---|---|
| |
| Date | 2018-09-XX |
| Time | all day |
| Website | QA/Test Days |
| IRC | #fedora-devel (webirc) |
| Mailing list | test |
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
What to test?
Today's instalment of Fedora Test Day will focus on OpenJDK 11 and OpenJDK 10. Currently we have java-1.8.0-openjdk as main JDK in Fedora. It accompanied java-1.7.0-openjdk as JRE for a year, and replaced it in buildroot in F21. Similarly, as did java-1.7.0-openjdk to java-1.6.0-openjdk in F16 as parallel JRE and replaced it in F17 in build root and main JDK. However, today the situation is more complicated. Oracle changed release process, see OpenJDK 11 summary and OpenJDK 10 summary, so currently, in F27 and up, you have java-1.8.0-openjdk as main JDK, java-openjdk as rolling release of STS JDK 10, and java-11-openjdk as techpreview of future LTS JDK. Javaws is provided in another package - icedtea-web
- Most crucial is, that JDK10 and JDK11, unlike JDK8, are modular, so many java applications will case to work.
- This is not crucial part of the testing, but to have an matrix of most common failures would be interesting
Among other changes are
- parallel installability
- switching of JRE/JDK
- platform docs and sources
- config files in /etc
- system wide crypto policy
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion. In case of problem related to test day organization/wiki/whatever, please reach out to sumantrom.
- CET: jvanek, zzambers, mvala, pmikova
- EDT: still_looking_for_volunteers
Prerequisite for Test Day
- kind relationship to java
- basic knowledge of java and javac or rpms.
- basic knowledge of java's jigsaw (major change in jdk9) is advantage
- Root access on the system where testing is happening
Known issue
How to test?
TODO:
dnf install java dnf install javac dnf install java-devel dnf install java-openjdk dnf install java-11-openjdk dnf install java-1.8.0-openjdk alternatives --config javac/javac and other master JAVA_HOME usage content of /usr/lib/jvm (and all the vendor/version less links) configs in /etc system crypto infulence
Exploratory testing
If you run out of test cases, congratulations! But that's not the end! You can still help out by playing around with the various installs uninstalls parallel isntalls jre/jdk switching... in whatever ways you can think of: try out all the things you can find. Get creative! Any problems you find please file a bug, or report to the IRC channel.
Reporting bugs
If you have problems with any of the tests, report a bug to Bugzilla usually for the component java-openjdk or java-11-openjdk or java-1.8.0-openjdk. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.