dagere / issuetest Goto Github PK

This issue has been imported from an old repository. It was originally created by @DaGeRe at 2020-11-24T13:21:14Z with number #1

Als Entwickler möchte ich Zugriff auf ein minimales Jenkins-Plugin erhalten, dass es ermöglicht:

• Die Regressionstestselektion und Messung auszuführen
• Performanceänderungen beim jeweiligen Job anzuzeigen

Das sollte die letzten beiden Git-Versionen des aktuellen Branches analysieren.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-04-15T13:03:49Z with number #12

Since the performance testing takes quite long it might not be useful to trigger it for every build, instead for example something like once per night.
If triggered in that way it would be neccessary to run peass not against a statically defined version diff but instead against the last version that was tested by peass before.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-10-20T08:52:56Z with number #48

When executing RCA with

measure versionDiff: 1, VMs: 20, 
              createDefaultConstructor: false, executeRCA: true, iterations: 40, 
              executeParallel: false, warmup: 10,
              includes: 'immo.geomap.backend.objektservice.impl.objekte.TestObjektServiceImpl#*',
              measurementMode: 'LEVELWISE', repetitions: 10, testGoal: '', timeout: 100,
              useAggregation: true, useSourceInstrumentation: true, displayRTSLogs: true, nightlyBuild: false,
              redirectToNull: false, showStart: true, excludeLog4j: true, generateCoverageSelection: true

In Console view when running:

Cannot reduce iterations (5) or repetitions (2) anymore
Was unable to analyze: testSearchPaging
java.lang.RuntimeException: Execution took too long, Iterations: 2 Warmup: 0 Repetitions: 2
   at de.dagere.peass.measurement.rca.CauseTester.measureVersion(CauseTester.java:66)
   at de.dagere.peass.measurement.rca.searcher.LevelCauseSearcher.measureLevel(LevelCauseSearcher.java:99)
   at de.dagere.peass.measurement.rca.searcher.LevelCauseSearcher.isLevelDifferent(LevelCauseSearcher.java:83)
   at de.dagere.peass.measurement.rca.searcher.LevelCauseSearcher.isLevelDifferent(LevelCauseSearcher.java:93)
   at de.dagere.peass.measurement.rca.searcher.LevelCauseSearcher.searchCause(LevelCauseSearcher.java:70)
   at de.dagere.peass.measurement.rca.searcher.CauseSearcher.search(CauseSearcher.java:67)
   at de.dagere.peass.ci.helper.RCAExecutor.executeRCA(RCAExecutor.java:139)
   at de.dagere.peass.ci.helper.RCAExecutor.analyseChange(RCAExecutor.java:119)
   at de.dagere.peass.ci.helper.RCAExecutor.executeRCAs(RCAExecutor.java:72)
   at de.dagere.peass.ci.remote.RemoteRCA.executeRCA(RemoteRCA.java:88)
   at de.dagere.peass.ci.remote.RemoteRCA.invoke(RemoteRCA.java:58)
   at de.dagere.peass.ci.remote.RemoteRCA.invoke(RemoteRCA.java:28)
   at hudson.FilePath.act(FilePath.java:1173)
   at hudson.FilePath.act(FilePath.java:1156)
   at de.dagere.peass.ci.LocalPeassProcessManager.rca(LocalPeassProcessManager.java:98)
   at de.dagere.peass.ci.MeasureVersionBuilder.measure(MeasureVersionBuilder.java:171)
   at de.dagere.peass.ci.MeasureVersionBuilder.runAllSteps(MeasureVersionBuilder.java:155)
   at de.dagere.peass.ci.MeasureVersionBuilder.perform(MeasureVersionBuilder.java:119)
   at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:99)
   at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69)
   at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
   at java.lang.Thread.run(Thread.java:748)

This issue has been imported from an old repository. It was originally created by @alex-iotiq at 2021-03-26T15:34:12Z with number #11

Es fehlt die Möglichkeit einen testGoal im Plugin anzugeben, genauso wie in peass DaGeRe/peass#22.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-03-11T14:20:15Z with number #10

In our project the unit tests cannot be run repetitiously without resetting the state through @AfterClass and @BeforeClass.
peass does not run these functions between repetitions.
I understand that this is sometimes counterproductive to measurement speed.
Is it possible to get this feature as an option?

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-07-22T13:04:43Z with number #24

Currently the information on the measured times are presented as a single graph in the jenkins action 'Performance Measurement'. Whereas the results of the Root Cause Analsysis are shown in greater detail for each node.
Bring the represented information in 'Performance Measurement' up to par with those in RCA.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-09-09T14:56:17Z with number #31

the link redirects to the jenkins job.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-09-14T08:27:44Z with number #35

It seems that sometimes (usually through timeouts?) the configuration changes internally, for example reduces the iteration count.
This needs to be transparent for the user.

This issue has been imported from an old repository. It was originally created by @DaGeRe at 2021-05-11T09:48:41Z with number #14

There should be a separate pipeline step measureJMH, which starts the measurement of JMH tests.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-03-10T23:42:23Z with number #9

In case that cleanup of unit tests is not proper neither iterations and repetitions can be used (need be set to 0) and instead many VMs need be used.
Also (if the unit tests can be run several times in a vm) there doesn't seem to be any good metric for how many repetitions vs. iterations should be used.
It seems that both can be hidden to the advanced configuration. Instead there would be a switch 'All unit tests can be run multiple times in one VM' and a total number of times to run the test. (Or alternatively another config option, see #8 Simpler Configuration issue)
As far as i can see peass-ci should be able to determine a good configuration from these two inputs that are much user friendlier.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-03-03T09:44:49Z with number #7

With Includes set the regression test selection fails because it can't find the java files, seems to be because of multi module structure.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-09-29T10:34:03Z with number #43

In my instance the @before and @ClassRule / @rule make up the majority of runtime of the test AND they seem to be the main sources of the spread.
It would be useful to have an option to only measure the method without these, obviously this would mean no repetitions.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-02-26T16:37:13Z with number #6

Feature seems to not work at the moment.

This issue has been imported from an old repository. It was originally created by @mai13drd at 2021-06-29T13:31:03Z with number #20

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-07-21T10:54:50Z with number #23

Currently, when a test fails in whatever fashion (i.e. timeout), the exception in the peass process happens at a later time and for different reasons, thus the Exceptions shown in the jenkins Console are products of the peass process that the user cannot interpret easily.
Additionally the erroneous Tests and their respective logs should be shown or referenced for the jenkins user.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-10-18T09:10:18Z with number #46

No visualization of measurement results:

java.lang.NumberFormatException: For input string: '_8' at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:580) at java.lang.Integer.parseInt(Integer.java:615) at de.dagere.peass.visualization.KoPeMeTreeConverter.readFile(KoPeMeTreeConverter.java:88) at de.dagere.peass.visualization.KoPeMeTreeConverter.<init>(KoPeMeTreeConverter.java:60) at de.dagere.peass.ci.helper.DefaultMeasurementVisualizer.visualizeMeasurements(DefaultMeasurementVisualizer.java:65) at de.dagere.peass.ci.LocalPeassProcessManager.createPureMeasurementVisualization(LocalPeassProcessManager.java:155) at de.dagere.peass.ci.LocalPeassProcessManager.visualizeMeasurementResults(LocalPeassProcessManager.java:130) at de.dagere.peass.ci.MeasureVersionBuilder.measure(MeasureVersionBuilder.java:168) at de.dagere.peass.ci.MeasureVersionBuilder.runAllSteps(MeasureVersionBuilder.java:155) at de.dagere.peass.ci.MeasureVersionBuilder.perform(MeasureVersionBuilder.java:119) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:99) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)

This issue has been imported from an old repository. It was originally created by @DaGeRe at 2021-09-13T09:38:12Z with number #34

Peass currently uses jQuery for interaction in the frontend. For several reasons (https://javascript.plainenglish.io/why-you-should-use-react-instead-of-jquery-d68b5b129bbb), react should be used instead.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-09-24T08:38:43Z with number #41

Currently it is not clear what's going on after a force push.
Since peass can't build the 'last' (deleted) version it just doesn't do anything but doesn't show an error message either.
It should be made clear to the user that something is up. Clearing the peass-cache and rebuilding seems to fix the issue.

This issue has been imported from an old repository. It was originally created by @DaGeRe at 2021-09-07T16:35:15Z with number #28

Measurement always happens for the specified repetitions count. Therefore, the measured value should always be visualized (instead of value/repetitions). This should be clarified by a question mark with information that show up on hover.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-07-16T09:07:03Z with number #22

Seems to happen at regression test selection stage.

Example Exception:
java.lang.RuntimeException: java.io.FileNotFoundException: /var/jenkins_home/workspace/GeoMap-Parallel-Test/../GeoMap-Parallel-Test_fullPeass/properties_GeoMap-Parallel-Test/methods/011d58f92f2628b4a5e4dee78482fd61d035addd/geomap-backend-objektservice§immo.geomap.backend.objektservice.impl.objekte.TestObjektServiceImpl/createObjekt_java.lang.String_java.lang.String_java.lang.Double_java.lang.Double_java.lang.Boolean_immo.geomap.datamodel.importer.EntryState_immo.geomap.datamodel.objekt.ImmoEinordnungEnums.EKaufMiete_immo.geomap.datamodel.objekt.ImmoEinordnungEnums.EObjektArt_immo.geomap.datamodel.objekt.ImmoEinordnungEnums.EObjektTyp_java.lang.Boolean_int_java.lang.Double_boolean_int_java.lang.Boolean_java.lang.Double_java.time.LocalDateTime_immo.geomap.datamodel.importer.geo.GeoPoint_diff.txt (File name too long)
at de.dagere.peass.analysis.properties.PropertyReader.readAllTestsProperties(PropertyReader.java:49)
at de.dagere.peass.ci.ContinuousExecutor.readMethodSources(ContinuousExecutor.java:128)
at de.dagere.peass.ci.ContinuousExecutor.executeRegressionTestSelection(ContinuousExecutor.java:114)
at de.dagere.peass.ci.ContinuousExecutor.executeRTS(ContinuousExecutor.java:92)
at de.dagere.peass.ci.remote.RemoteRTS.invoke(RemoteRTS.java:54)
at de.dagere.peass.ci.remote.RemoteRTS.invoke(RemoteRTS.java:20)
at hudson.FilePath.act(FilePath.java:1164)
at hudson.FilePath.act(FilePath.java:1147)
at de.dagere.peass.ci.LocalPeassProcessManager.rts(LocalPeassProcessManager.java:57)
at de.dagere.peass.ci.MeasureVersionBuilder.perform(MeasureVersionBuilder.java:105)
at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:99)
at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69)
at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.FileNotFoundException: /var/jenkins_home/workspace/GeoMap-Parallel-Test/../GeoMap-Parallel-Test_fullPeass/properties_GeoMap-Parallel-Test/methods/011d58f92f2628b4a5e4dee78482fd61d035addd/geomap-backend-objektservice§immo.geomap.backend.objektservice.impl.objekte.TestObjektServiceImpl/createObjekt_java.lang.String_java.lang.String_java.lang.Double_java.lang.Double_java.lang.Boolean_immo.geomap.datamodel.importer.EntryState_immo.geomap.datamodel.objekt.ImmoEinordnungEnums.EKaufMiete_immo.geomap.datamodel.objekt.ImmoEinordnungEnums.EObjektArt_immo.geomap.datamodel.objekt.ImmoEinordnungEnums.EObjektTyp_java.lang.Boolean_int_java.lang.Double_boolean_int_java.lang.Boolean_java.lang.Double_java.time.LocalDateTime_immo.geomap.datamodel.importer.geo.GeoPoint_diff.txt (File name too long)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(FileOutputStream.java:270)
at java.io.FileOutputStream.(FileOutputStream.java:213)
at org.apache.commons.io.FileUtils.openOutputStream(FileUtils.java:2440)
at org.apache.commons.io.FileUtils.writeStringToFile(FileUtils.java:3356)
at org.apache.commons.io.FileUtils.writeStringToFile(FileUtils.java:3340)
at de.dagere.peass.analysis.properties.MethodChangeReader.readMethodChangeData(MethodChangeReader.java:47)
at de.dagere.peass.analysis.properties.PropertyReadHelper.readMethodSources(PropertyReadHelper.java:188)
at de.dagere.peass.analysis.properties.PropertyReadHelper.analyzeTraceFiles(PropertyReadHelper.java:174)
at de.dagere.peass.analysis.properties.PropertyReadHelper.getSourceInfos(PropertyReadHelper.java:129)
at de.dagere.peass.analysis.properties.PropertyReadHelper.read(PropertyReadHelper.java:99)
at de.dagere.peass.analysis.properties.PropertyReader.readMethod(PropertyReader.java:79)
at de.dagere.peass.analysis.properties.PropertyReader.readVersion(PropertyReader.java:64)
at de.dagere.peass.analysis.properties.PropertyReader.readAllTestsProperties(PropertyReader.java:43)

This issue has been imported from an old repository. It was originally created by @DaGeRe at 2020-11-24T13:21:38Z with number #2

Es sollten VMs, Iterationen, GC, etc. sollte über Jenkins-Oberfläche konfiguriert werden.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-09-13T09:37:56Z with number #33

The delete cache ability is there mainly to allow new measurements with a changed peass-version or configuration. The old measurement is often still valid, but the details (through the Inspect Measurements link) are not available after deleting the cache.
Would it be possible to hold these results available?

This issue has been imported from an old repository. It was originally created by @DaGeRe at 2021-09-13T08:18:35Z with number #32

Currently, if the cache is deleted, all cached Peass data is deleted.

There should also be an option to only delete the measurement data, since sometimes remeasurement without reexecution of regression test selection is intended.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-02-26T13:20:16Z with number #5

The Includes option allows to specify only a subset of tests to be measured by peass. At the moment the regression test selection phase seems to still instrument all tests regardless of Includes.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-09-29T10:35:54Z with number #44

Measuring many tests can be very time intense, to be able to set better informed includes it would be great to have a way to run all current tests as performance tests and make available the information of

1. runtime
2. spread

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-04-22T09:52:44Z with number #13

It rarely happens that a commit doesn't compile.
Measuring the commit after that one should still work by comparing not to the last (potentially non-compiling) commit, but against the last compiling build.

This issue has been imported from an old repository. It was originally created by @DaGeRe at 2021-06-27T11:15:47Z with number #18

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-06-17T08:46:15Z with number #17

Currently whitespaces in jenkins items (pipelines) causes all tests to be selected.

This issue has been imported from an old repository. It was originally created by @mawHBT at 2021-09-15T12:15:05Z with number #36

If SimpleLoggerContext is used, creating LoggerContext in JenkinsLogRedirector causes:

java.lang.ClassCastException: class org.apache.logging.log4j.simple.SimpleLoggerContext cannot be cast to class org.apache.logging.log4j.core.LoggerContext (org.apache.logging.log4j.simple.SimpleLoggerContext and org.apache.logging.log4j.core.LoggerContext are in unnamed module of loader jenkins.util.AntClassLoader @212619ff)
   at de.dagere.peass.ci.JenkinsLogRedirector.<init>(JenkinsLogRedirector.java:14)
   at de.dagere.peass.ci.MeasureVersionBuilder.perform(MeasureVersionBuilder.java:112)
   at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:100)
   at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:70)

This issue has been imported from an old repository. It was originally created by @DaGeRe at 2021-10-19T10:38:43Z with number #47

With the configuration measurementMode: 'LEVELWISE', useSampling: false, useSourceInstrumentation: false, RCA failes sometimes with the following message:

02:12:32.397 [org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#1]] WARN de.dagere.peass.measurement.rca.data.CallTreeNode:129 - Warning! Reading aggregated data which contain less executions than the warmup 100
Was unable to analyze: testSearchPaging
java.lang.NullPointerException
at de.dagere.peass.statistics.StatisticUtil.getMean(StatisticUtil.java:30)
at de.dagere.peass.measurement.rca.data.CallTreeNode.removeWarmup(CallTreeNode.java:134)
at de.dagere.peass.measurement.rca.data.CallTreeNode.addAggregatedMeasurement(CallTreeNode.java:102)
at de.dagere.peass.measurement.rca.KiekerResultReader.readNode(KiekerResultReader.java:101)
at de.dagere.peass.measurement.rca.KiekerResultReader.readAggregatedData(KiekerResultReader.java:80)
at de.dagere.peass.measurement.rca.KiekerResultReader.readResults(KiekerResultReader.java:67)
at de.dagere.peass.measurement.rca.CauseTester.handleKiekerResults(CauseTester.java:164)
at de.dagere.peass.dependencyprocessors.OnceRunner.runOnce(OnceRunner.java:60)
at de.dagere.peass.dependencyprocessors.DependencyTester.runOnce(DependencyTester.java:233)
at de.dagere.peass.dependencyprocessors.DependencyTester.runSequential(DependencyTester.java:225)
at de.dagere.peass.dependencyprocessors.DependencyTester.runOneComparison(DependencyTester.java:189)
at de.dagere.peass.dependencyprocessors.AdaptiveTester.evaluateWithAdaption(AdaptiveTester.java:47)
at de.dagere.peass.measurement.rca.CauseTester.evaluate(CauseTester.java:91)
at de.dagere.peass.measurement.rca.CauseTester.measureVersion(CauseTester.java:59)
at de.dagere.peass.measurement.rca.searcher.LevelCauseSearcher.measureLevel(LevelCauseSearcher.java:99)
at de.dagere.peass.measurement.rca.searcher.LevelCauseSearcher.isLevelDifferent(LevelCauseSearcher.java:83)
at de.dagere.peass.measurement.rca.searcher.LevelCauseSearcher.isLevelDifferent(LevelCauseSearcher.java:93)
at de.dagere.peass.measurement.rca.searcher.LevelCauseSearcher.searchCause(LevelCauseSearcher.java:70)
at de.dagere.peass.measurement.rca.searcher.CauseSearcher.search(CauseSearcher.java:67)
at de.dagere.peass.ci.helper.RCAExecutor.executeRCA(RCAExecutor.java:139)
at de.dagere.peass.ci.helper.RCAExecutor.analyseChange(RCAExecutor.java:119)
at de.dagere.peass.ci.helper.RCAExecutor.executeRCAs(RCAExecutor.java:72)
at de.dagere.peass.ci.remote.RemoteRCA.executeRCA(RemoteRCA.java:88)
at de.dagere.peass.ci.remote.RemoteRCA.invoke(RemoteRCA.java:58)
at de.dagere.peass.ci.remote.RemoteRCA.invoke(RemoteRCA.java:28)

This should be fixed.

This issue has been imported from an old repository. It was originally created by @mai13drd at 2021-06-29T13:20:08Z with number #19

This issue has been imported from an old repository. It was originally created by @alex-iotiq at 2021-10-25T11:05:24Z with number #49

If testing with Peass with the original build.gradle is not working, a modification of build.gradle to run successful tests with Peass can cause problems for the main project.
An alternative build.gradle that you can provide for Peass can solve this problem where you have the original file for the main project and another one specifically for testing with Peass.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-10-25T14:55:41Z with number #50

Using the OnlyMeasureWorkload option should be mutually exclusive with using several repetitions, since @before (compared to @BeforeClass) would usually be needed to run before every test method run.

Currently this runs through without a notice, but it should likely be a ConfigurationException or similar.

This issue has been imported from an old repository. It was originally created by @DaGeRe at 2021-10-18T08:42:12Z with number #45

Since the update to Java 16, powermock does not work anymore: https://github.com/DaGeRe/peass/actions/runs/1351543388 This should be fixed

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-09-27T13:31:58Z with number #42

Not sure what the reason might be:
Performance Measurement Logs Overview
Peass Measurement Execution Log
Test Case: geomap-backend-objektservice§immo.geomap.backend.objektservice.impl.objekte.TestObjektServiceImpl#testSearchPaging
VMs: 0
And no logs supplied, even though there are measurements.

This issue has been imported from an old repository. It was originally created by @mai13drd at 2021-08-25T10:02:41Z with number #27

If JMH-benchmarks are used for measurements, the field Source instrumentation inside the job configuration must be set, since JMH in combination with AspectJ-instrumentation does not work yet.
This should be fixed or at least reported to the user.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-07-22T13:43:59Z with number #25

Timeout for tests are a supported feature to cut short unexpectedly long running tests.
Currently they seem to simply lead to an error in the peass process, badly visible for the user. Instead it should inform of the issue clearly and continue running any other tests.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-09-08T07:39:46Z with number #29

The Exception is:

java.lang.NullPointerException
   at de.dagere.peass.ci.rts.RTSVisualizationCreator.readStaticSelection(RTSVisualizationCreator.java:109)
   at de.dagere.peass.ci.rts.RTSVisualizationCreator.visualize(RTSVisualizationCreator.java:46)
   at de.dagere.peass.ci.LocalPeassProcessManager.visualizeRTSResults(LocalPeassProcessManager.java:78)
   at de.dagere.peass.ci.MeasureVersionBuilder.perform(MeasureVersionBuilder.java:114)
   at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:99)
   at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69)
   at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
   at java.lang.Thread.run(Thread.java:748)

Seems to happen when no changes detected.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-09-20T08:21:29Z with number #39

One headline there is 'Messungen', should probably be english ;)

This issue has been imported from an old repository. It was originally created by @mai13drd at 2021-07-01T07:55:26Z with number #21

This issue has been imported from an old repository. It was originally created by @mai13drd at 2021-05-26T12:37:02Z with number #15

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-09-16T09:01:52Z with number #38

The text there is helpful, only please add the notation for maven submodules: submodule$path.to.Test#*

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-09-16T09:00:17Z with number #37

The logs aren't shown when the build fails early, i.e. when the includes are badly formatted.

This issue has been imported from an old repository. It was originally created by @MarkEWaite at 2021-02-06T15:08:05Z with number #4

Use Jenkins plugin bom to manage versionsThe Jenkins plugin bill of materials can reduce the version managementchallenges for Jenkins components.- Manage dependencies with plugin bom- Use latest parent pom 4.16

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-06-10T12:53:19Z with number #16

Maybe this is mostly an issue for the current early stage:
Available data, i.e. the includes, or already instrumented tests don't change if you do a rebuild. To circumvent that you'd have to make a new jenkins item or delete the results of specific peass stages by hand. It would be useful to have possibilities of deleting some or all results through some jenkins menu item.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-03-10T23:33:24Z with number #8

It is fairly hard to choose a proper configuration that will
a) not take too long to finish
b) show small enough performance differences

Is it possible to let the tool figure out the appropriate configuration by giving it a target time and significance?
As a start the tool might make bad assumptions but would offer this configuration optionally in the interface.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-09-09T14:51:40Z with number #30

The target audience would likely not know what the significance indicator T means, or have to look up the exact meaning. It would be useful to have a easy to understand indication, something along the lines of
not significant
low significance
high significance

This issue has been imported from an old repository. It was originally created by @mai13drd at 2021-08-18T08:31:31Z with number #26

Added a boolean measureJMH to MeasureVersionBuilder. Can be set in pipeline configuration to allow usage of JMH-Tests for measurements.

This issue has been imported from an old repository. It was originally created by @DaGeRe at 2020-11-24T15:09:01Z with number #3

Der Quelltext-Diff in der RCA-Visualisierung sollte Syntax-Highlighting ermöglichen und veränderte Zeilen markieren.

This issue has been imported from an old repository. It was originally created by @Schattensilber at 2021-09-20T08:24:49Z with number #40

The deviation values are currently hard to understand.
It seems to me it would be useful to present them in the same unit as the measurement time and difference to be better comparable to those numbers.