Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8277160 [macos] tools/jpackage/share/MultiLauncherTwoPhaseTest.java failed with "PackagerException: jlink failed"
  3. JDK-8277507

Add jlink.debug system property while launching jpackage tests to help diagonize recent intermittent failures

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: P4 P4
    • 18
    • 18
    • tools
    • None
    • b26

      There have been 3 reported test failures of jpackage tests:
      https://bugs.openjdk.java.net/browse/JDK-8274622
      https://bugs.openjdk.java.net/browse/JDK-8277160
      https://bugs.openjdk.java.net/browse/JDK-8277058

      All of them appear to have the same underlying root cause where the jlink command (which is launched from within the jpackage tests) fails with:

      "Error: java.lang.IllegalArgumentException".
      These have all failed on macos aarch64 based on the logs attached to those issues.

      However, that isn't enough to narrow down what's causing these failures. The jdk.tools.jlink.internal.JlinkTask internally uses a "jlink.debug" system property to decide whether to print the exception stacktrace of these failures. By default it is "false" and it doesn't print these exception stacktraces.

      It would be good to set this system property to "true" while launching these jpackage tests to help get more detailed failure cause.



            jpai Jaikiran Pai
            jpai Jaikiran Pai
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: