NoSuchElementException in getCurrentStep() method during parallel run

I’m submitting a …

• [* ] bug report
• feature request
• support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

During parallel run about 50-70 threads using testNg mechanism i faced that sometimes method which annotated with @Step threw NoSuchElementException

java.util.NoSuchElementException at java.util.LinkedList.getFirst(LinkedList.java:244) at io.qameta.allure.internal.AllureStorage.getCurrentStep(AllureStorage.java:37) at io.qameta.allure.AllureLifecycle.startStep(AllureLifecycle.java:203) at io.qameta.allure.aspects.StepsAspects.step(StepsAspects.java:49)

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

Allure threw NoSuchElementException in public Optional<String> getCurrentStep() { final LinkedList<String> uids = currentStepContext.get(); return uids.isEmpty() ? Optional.empty() : Optional.of(uids.getFirst());

so i think this method should be synchronized

What is the expected behavior?

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Allure version	2.4.1
Test framework	testng@6.9.10
Allure adaptor	allure-testng@2.6.0
Generate report using	allure-gradle@2.5

Other information

[bwolfe]

This ticket should be in the allure-java repo

[baev]

The issue should be fixed in latest allure-java release.