JDK-8289146 tries to address this test failure on systems without swap accounting turned on at the kernel level. The chosen solution was to fail the test and advise the user to run with swapaccount=1. This isn't a great solution as users might want to run on systems with swapaccount=0. The code handles this fine, but the test fails, which is unsatisfying.

Note that the test wants to verify that if --memory-swappiness=0 is passed on the container runtime, no swap memory should be reported by container detection code since no swap should be used. The premise is that swap accounting *is* turned on though. Otherwise the test cannot pass.

As running this test doesn't make sense on a system with swapaccount=0 the test should detect it and throw jtreg.SkippedException with an appropriate setup hint instead of failing.