improve vmlens handling and execution

[aepfli]

Vmlens is a powerful tool but our current developer experience is diminished, as it is executed all the times and increases the basic verify step heavily.

But especially our basic verify step should be fast and provide fast feedback. I suggest to move the vmlens to an own maven profile which is not executed per default. Additionally I suggest to also execute the vmlens profile as a separate GitHub action, to distinguish between the topics, and to give faster feedback on pull requests if it is a general testing compilation issue or if it is a concurrency issue.

Wdyt @chrfwow ?

[chrfwow]

The way vmlens is set up currently, it will run the whole test suite (invoke the test target) after verify has run, but with the agent attached. If we want to have it as a separate profile, we can certainly do that, and it would speed things up because we will not run the tests twice. But it will still take some time as all tests have to be executed for vmlens, even though we might only want to run the vmlens tests, which is not possible currently.
Ideally, we would configure our verify step in a way to only run the vmlens test target, and not the default test target. The vmlens tests themselfes to not take much longer than our other tests. The increase in time for the verify steps to complete comes from the current setup of the pipeline. We first run verify as we did before, and then we run the tests again with the vmlens agent attached. This should be fixed.

Edit: the vmlens tests do take quite a while, and I think we should only run them if applicable

[RajvardhanT7747]

can i get more clarification about this issue ? @aepfli

[chrfwow]

@RajvardhanT7747 we recently introduced vmlens into the sdk.
The Vmlens maven plugin provides an extra test target, which attaches the vmlens agent, runs the tests, and does some evaluations on the results.
Currently, our vmlens setup first runs the verify target, and afterwards the vmlens test target. This means that the tests are effectively run twice, once by verify, and a second time through vmlens.

Ideally, the first run during verify would already run the vmlens test target, or we run the vmlens tests through an extra pipeline step, that we will only run when applicable

[chrfwow]

In a recent run, the vmlens were hanging for ~30mins at one test (this has not happened in the CI pipeline before). I think we need to look into possible causes

[ThomasKrieger]

I changed the config and the name of the test so that VMLens now only execute the VmLensTest, or new VmLensCT.
This also solves the problem with the hanging threads wich was related to executing ArchUnit Tests together with VMLens.

see #1628

The VMLens tests takes now around 4s. Just let me know if you also want a specific profile for this.