Open yuliiamir opened 5 months ago
The following method naming also caused the same Gradle issue with report generation in the scope of the retry mechanism.
@Unroll("Able to create a second flow if #data.description")
def "Able to create multiple flows on certain combinations of switch-port-vlans"() {
The appropriate changes have been added in the scope https://github.com/telstra/open-kilda/pull/5644
The issue occurs when the parameterized Spock method with a random unique name for each iteration fails. As a result, the Gradle retry plugin can not retrieve old failed test details by new rerun test details.
Issue:
As a solution, tests that have such kind of naming strategy should be modified.
Example:
Failed test: System is able to collect latency stats for subflows [subFlow: 11Apr091705_157_oatflour2420_haflow-a, direction: FORWARD, #0]
Test name after Gradle rerun failed test^: System is able to collect latency stats for subflows [subFlow: 11Apr091946_456_redlentils4861_haflow-b, direction: FORWARD, #1]