> `TestLoadLibraryDeadlock.java` test runs `LoadLibraryDeadlock` and wait for 5 > seconds and then grab the output. Then run `jcmd` to dump the thread stacks > in case there is a deadlock. The test ignores and swallows any exception > which makes it hard to diagnose test issues. > > This PR simplifies the test to use `jdk.test.lib.process.ProcessTools` to > launch `LoadLibraryDeadlock` test so that the output and error will be > captured in the same way as other tools are run by this test. Also update > the test to propagate exceptions where appropriate. This hopes to collect > more information to diagnose the issue if this test fails next time.
Mandy Chung has updated the pull request incrementally with one additional commit since the last revision: review feedback: use ProcessTools.createTestJavaProcessBuilder ------------- Changes: - all: https://git.openjdk.org/jdk/pull/16459/files - new: https://git.openjdk.org/jdk/pull/16459/files/a4c8ebae..962690fa Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=16459&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=16459&range=00-01 Stats: 49 lines in 2 files changed: 15 ins; 20 del; 14 mod Patch: https://git.openjdk.org/jdk/pull/16459.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/16459/head:pull/16459 PR: https://git.openjdk.org/jdk/pull/16459
