RFR: 8340092: [Linux] containers/systemd/SystemdMemoryAwarenessTest.java failing on some systems

Matthias Baesken mbaesken at openjdk.org
Mon Sep 16 07:12:07 UTC 2024


On Fri, 13 Sep 2024 09:10:19 GMT, Severin Gehwolf <sgehwolf at openjdk.org> wrote:

> Please review this trivial test fix. The test fails if the `<slice>.d` directory already exists (for some reason). It needs to exist for the test to work. But if it exists we ignore the failure, thus using `Files.createDirectories()`.
> 
> As a benefit I've also added `exclusiveAccess.dirs=.` to the `systemd` test directory to match container tests in `docker` folder and added `TRUNCATE_EXISTING` for files in the `<slice>.d` directory. Both of which should ensure the test runs more reliably.
> 
> Testing:
> - [ ] GHA
> - [x] Manual testing by creating the directory first, running the test. Failed. The same handshake passes after the patch.
> 
> Thanks!

Unfortunately I still see test failures 
containers/systemd/SystemdMemoryAwarenessTest.java

java.lang.AssertionError: Failed to reload systemd daemon
	at jdk.test.lib.containers.systemd.SystemdTestUtils.systemdDaemonReload(SystemdTestUtils.java:190)
	at jdk.test.lib.containers.systemd.SystemdTestUtils.buildSystemdSlices(SystemdTestUtils.java:169)
	at jdk.test.lib.containers.systemd.SystemdTestUtils.buildAndRunSystemdJava(SystemdTestUtils.java:91)
	at SystemdMemoryAwarenessTest.testHelloSystemd(SystemdMemoryAwarenessTest.java:69)
	at SystemdMemoryAwarenessTest.main(SystemdMemoryAwarenessTest.java:48)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	at java.base/java.lang.reflect.Method.invoke(Method.java:573)
	at com.sun.javatest.regtest.agent.MainWrapper$MainTask.run(MainWrapper.java:138)
	at java.base/java.lang.Thread.run(Thread.java:1576)

-------------

PR Comment: https://git.openjdk.org/jdk/pull/20989#issuecomment-2352159646


More information about the hotspot-runtime-dev mailing list