-
Notifications
You must be signed in to change notification settings - Fork 8
Searching for Configuration Problems
In some cases, the analysis and measurement of your project might not work as expected. Please check this page first; if you can not find a solution for your problem here, please file an issue in peass-ci-plugin.
Check the following problems:
For every executed method, an entry is written to the Kieker writer queue and this entry is serialized afterwards. The writing might not finish on time due to too many method calls / too slow I/O.
If this error occurs, you will find something like
10:44:01.116 [Test worker] DEBUG de.dagere.kopeme.kieker.KoPeMeKiekerSupport:104 - Queue size: 9999999 10:44:02.333 [Test worker] DEBUG de.dagere.kopeme.kieker.KoPeMeKiekerSupport:104 - Queue size: 9999145 10:44:03.386 [Test worker] DEBUG de.dagere.kopeme.kieker.KoPeMeKiekerSupport:104 - Queue size: 10000000 10:44:04.500 [Test worker] DEBUG de.dagere.kopeme.kieker.KoPeMeKiekerSupport:104 - Queue size: 9999999 10:44:05.865 [Test worker] DEBUG de.dagere.kopeme.kieker.KoPeMeKiekerSupport:104 - Queue size: 9999384 10:44:07.167 [Test worker] DEBUG de.dagere.kopeme.kieker.KoPeMeKiekerSupport:112 - Final queue size: 9997446
in your tests log. If the Final queue size is above 0, please consider increasing kiekerWaitTime or reducing the size of your test case. Additionally, if your queue size hits the maximum queue size, consider increasing kiekerQueueSize.
In order for measurement to be executable correctly, Peass needs a repeatable workload. By default, Peass executes @BeforeClass / @BeforeAll once, then executes @Before, your test case, @After (repeated), and then once @AfterClass / @AfterAll. If you want to execute @BeforeClass / @BeforeAll / @AfterClass / @AfterAll also repeated, set executeBeforeClassInMeasurement to true.