Right now, each time we invoke llvm-kompile-testing, we are invoking maven. A consequence of this is that if maven has a transient failure during that invocation due to its communication with the internet, the test fails.
We don't really need to be invoking maven each time. We ought to be able to use the maven appassembler plugin to create a script that we can invoke from the llvm-kompile-testing script which will invoke the jvm directly. If we do this, then the intermittent failures will be limited only to if the maven internet fails during the build process itself, which is much more rare.
Doing this ought to reduce the frequency of flaky tests on CI, which have been happening somewhat frequently recently.
Right now, each time we invoke llvm-kompile-testing, we are invoking maven. A consequence of this is that if maven has a transient failure during that invocation due to its communication with the internet, the test fails.
We don't really need to be invoking maven each time. We ought to be able to use the maven appassembler plugin to create a script that we can invoke from the llvm-kompile-testing script which will invoke the jvm directly. If we do this, then the intermittent failures will be limited only to if the maven internet fails during the build process itself, which is much more rare.
Doing this ought to reduce the frequency of flaky tests on CI, which have been happening somewhat frequently recently.