Should the group jdk_wayland that would consist of jdk_awt_wayland + some other tests be created as well?
The reasons may be:
probably we might have non awt tests that need to be executed in regular runs against Wayland builds
even when jdk_wayland would be the same as jdk_awt_wayland it would help in generating run configurations without any workarounds. E.g. in order to generate configurations for wayland-fastdebug we have got errors about duplicated configurations related to jdk_awt_wayland that requires adding some crutches...
Should the group
jdk_wayland
that would consist ofjdk_awt_wayland
+ some other tests be created as well? The reasons may be:awt
tests that need to be executed in regular runs against Wayland buildsjdk_wayland
would be the same asjdk_awt_wayland
it would help in generating run configurations without any workarounds. E.g. in order to generate configurations forwayland-fastdebug
we have got errors about duplicated configurations related tojdk_awt_wayland
that requires adding some crutches...