JDK-8292054 : Test runtime/posixSig/TestPosixSig.java fails with 'Test failed, bad output.'
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 20
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2022-08-08
  • Updated: 2023-11-23
  • Resolved: 2022-08-17
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 20
20 b12Fixed
Related Reports
Relates :  
JDK-8279878 - java/awt/font/JNICheck/JNICheck.sh test fails on Ubuntu 21.10
Relates :  
JDK-8291569 - Consider removing JNI checks for signals SIGPIPE and SIGXFSZ
Relates :  
JDK-8292559 - Add test for -XX:+CheckJNICalls showing changed signal handlers
Relates :  
JDK-8285792 - Posix signal handler modification checking issues.
Relates :  
JDK-8319633 - runtime/posixSig/TestPosixSig.java intermittent timeouts on UNIX
Description
Test runtime/posixSig/TestPosixSig.java fails with
[2022-08-06T08:47:22.861110619Z] Gathering output for process 2830437
output: Warning: SIGFPE handler modified!
Signal Handlers:
   SIGSEGV: javaSignalHandler in libjvm.so, mask=11100100010111111101111111111110, flags=SA_RESTART|SA_SIGINFO
    SIGBUS: javaSignalHandler in libjvm.so, mask=11100100010111111101111111111110, flags=SA_RESTART|SA_SIGINFO
    SIGFPE: sig_handler in libTestPsig.so, mask=00000000000000000000000000000000, flags=none
  *** Handler was modified!
  *** Expected: javaSignalHandler in libjvm.so, mask=11100100110111111111111111111110, flags=SA_RESTART|SA_SIGINFO
   SIGPIPE: javaSignalHandler in libjvm.so, mask=11100100010111111101111111111110, flags=SA_RESTART|SA_SIGINFO
   SIGXFSZ: javaSignalHandler in libjvm.so, mask=11100100010111111101111111111110, flags=SA_RESTART|SA_SIGINFO
    SIGILL: sig_handler in libTestPsig.so, mask=00000000000000000000000000000000, flags=none
  *** Handler was modified!
  *** Expected: javaSignalHandler in libjvm.so, mask=11100100110111111111111111111110, flags=SA_RESTART|SA_SIGINFO
   SIGUSR2: SR_handler in libjvm.so, mask=00100000000000000000000000000000, flags=SA_RESTART|SA_SIGINFO
    SIGHUP: UserHandler in libjvm.so, mask=11100100010111111101111111111110, flags=SA_RESTART|SA_SIGINFO
    SIGINT: UserHandler in libjvm.so, mask=11100100010111111101111111111110, flags=SA_RESTART|SA_SIGINFO
   SIGTERM: UserHandler in libjvm.so, mask=11100100010111111101111111111110, flags=SA_RESTART|SA_SIGINFO
   SIGQUIT: UserHandler in libjvm.so, mask=11100100010111111101111111111110, flags=SA_RESTART|SA_SIGINFO
   SIGTRAP: SIG_DFL, mask=00000000000000000000000000000000, flags=none
Consider using jsig library.
Warning: SIGILL handler modified!
Signal Handlers:
   SIGSEGV: javaSignalHandler in libjvm.so, mask=11100100010111111101111111111110, flags=SA_RESTART|SA_SIGINFO
    SIGBUS: javaSignalHandler in libjvm.so, mask=11100100010111111101111111111110, flags=SA_RESTART|SA_SIGINFO
    SIGFPE: sig_handler in libTestPsig.so, mask=00000000000000000000000000000000, flags=none
  *** Handler was modified!
  *** Expected: javaSignalHandler in libjvm.so, mask=11100100110111111111111111111110, flags=SA_RESTART|SA_SIGINFO
   SIGPIPE: javaSignalHandler in libjvm.so, mask=11100100010111111101111111111110, flags=SA_RESTART|SA_SIGINFO
   SIGXFSZ: javaSignalHandler in libjvm.so, mask=11100100010111111101111111111110, flags=SA_RESTART|SA_SIGINFO
    SIGILL: sig_handler in libTestPsig.so, mask=00000000000000000000000000000000, flags=none
  *** Handler was modified!
  *** Expected: javaSignalHandler in libjvm.so, mask=11100100110111111111111111111110, flags=SA_RESTART|SA_SIGINFO
   SIGUSR2: SR_handler in libjvm.so, mask=00100000000000000000000000000000, flags=SA_RESTART|SA_SIGINFO
    SIGHUP: UserHandler in libjvm.so, mask=11100100010111111101111111111110, flags=SA_RESTART|SA_SIGINFO
    SIGINT: UserHandler in libjvm.so, mask=11100100010111111101111111111110, flags=SA_RESTART|SA_SIGINFO
   SIGTERM: UserHandler in libjvm.so, mask=11100100010111111101111111111110, flags=SA_RESTART|SA_SIGINFO
   SIGQUIT: UserHandler in libjvm.so, mask=11100100010111111101111111111110, flags=SA_RESTART|SA_SIGINFO
   SIGTRAP: SIG_DFL, mask=00000000000000000000000000000000, flags=none
Consider using jsig library.

----------System.err:(10/524)----------
java.lang.RuntimeException: Test failed, bad output.
	at TestPosixSig.main(TestPosixSig.java:65)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at java.base/java.lang.reflect.Method.invoke(Method.java:578)
	at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:312)
	at java.base/java.lang.Thread.run(Thread.java:1589)
Comments
Changeset: 0d96546a Author: Harold Seigel <hseigel@openjdk.org> Date: 2022-08-17 19:56:14 +0000 URL: https://git.openjdk.org/jdk/commit/0d96546ab93600f17877e5db2770e4125916bcda
17-08-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/9882 Date: 2022-08-15 18:29:55 +0000
15-08-2022
Hmm I see this failing on OL8.6 as well in a personal mach5 job.
09-08-2022
This may be an Ubuntu/Gtk issue. Gtk modifies SIGFPE handler and so causes the warnings from the VM. Those warnings then cause the test to break. See JDK-8279878. Not clear where Gtk comes into your test runs though ??? Workaround is to disable warnings when running the test. This will also go away when we fix JDK-8291569.
09-08-2022