There is weird issue observed with following 4 compiler/jvmci tests in case they are run in Graal JIT mode
(flags "-XX:+UnlockExperimentalVMOptions -XX:+EnableJVMCI -XX:+TieredCompilation -XX:+UseJVMCICompiler -Djvmci.Compiler=graal")
and jtreg is launched with -agentvm:

 compiler/jvmci/meta/StableFieldTest.java
 compiler/jvmci/jdk.vm.ci.hotspot.test/src/jdk/vm/ci/hotspot/test/HotSpotConstantReflectionProviderTest.java
 compiler/jvmci/jdk.vm.ci.hotspot.test/src/jdk/vm/ci/hotspot/test/MemoryAccessProviderTest.java
 compiler/jvmci/events/JvmciShutdownEventTest.java

The error occurs during "@run driver jdk.test.lib.FileInstaller ..." and is "result: Error. Can't init module exports: module not found: jdk.internal.vm.ci"
 

If '-agentvm' is not specified then no error happens.
Changing "@run driver" to "@run main" also results in no error.
This looks kind of strange and looks like something is going wrong with jtreg.

Steps to reproduce:
> jtreg -agentvm -vt -jdk:../build/linux-x64-debug.jdk/jdk-11/fastdebug
        -vmoptions:"-XX:+UnlockExperimentalVMOptions -XX:+EnableJVMCI -XX:+TieredCompilation -XX:+UseJVMCICompiler -Djvmci.Compiler=graal"
        -dir:test/hotspot/jtreg compiler/jvmci/events/JvmciShutdownEventTest.java