On Tue, 30 Jan 2024 13:57:43 GMT, Severin Gehwolf <sgehw...@openjdk.org> wrote:
>> 8307977: jcmd and jstack broken for target processes running with elevated >> capabilities > > `test/hotspot/jtreg/serviceability` tests would also be worth running. > Hi @jerboaa, thanks a lot for the hints! The container tests were new to me > at least. > > Just out of curiosity, are the container tests run as part of the tier1 tests > (`make test-tier1`)? I'm not sure if I'm looking at the right place, but I > get the feeling this is defined in `test/hotspot/jtreg/TEST.groups`, and the > answer is maybe "no" in that case. > > > Please run container tests, which do some jcmd testing across containers > > (host system runs jcmd and containers have the JVMs): > > `test/hotspot/jtreg/containers` See > > [testing.md](https://github.com/openjdk/jdk/blob/master/doc/testing.md#docker-tests) > > as to how to run them. I'll give this PR a spin as well. > > If I understand it correctly, this is the way to run them. Please correct me > if I'm wrong. > > ``` > $ make test TEST="jtreg:test/hotspot/jtreg/containers" > > ... > > ============================== > Test summary > ============================== > TEST TOTAL PASS FAIL ERROR > > jtreg:test/hotspot/jtreg/containers 14 14 0 0 > > ============================== > TEST SUCCESS > ``` Thanks! Please make sure that the tests actually ran. If, for example, `docker` is not installed, they get skipped. ------------- PR Comment: https://git.openjdk.org/jdk/pull/17628#issuecomment-1918774353
