RFR: 8340092: [Linux] containers/systemd/SystemdMemoryAwarenessTest.java failing on some systems
Severin Gehwolf
sgehwolf at openjdk.org
Mon Sep 16 11:40:04 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!
Thanks. It could be that the `user@<uid>.service` isn't running on those systems. Would you be able to check? What does this command report (run as the user the test suite runs, please)?
$ systemctl status user@$(id -u).service
If that's it, I'll add another check for this.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/20989#issuecomment-2352674624
More information about the hotspot-runtime-dev
mailing list