Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Could not update step: step with uuid 4e11d596-3482-4a5a-ae04-c70ed3cc753a not found io.qameta.allure.AllureLifecycle #1798

Open
roaamagdy opened this issue Nov 6, 2024 · 3 comments
Assignees
Labels
bug Something isn't working question Further information is requested

Comments

@roaamagdy
Copy link

roaamagdy commented Nov 6, 2024

When running junit test , this error is thrown each time the test method is executed with different uuid.

Could not update step: step with uuid 4e11d596-3482-4a5a-ae04-c70ed3cc753a not found io.qameta.allure.AllureLifecycle

@roaamagdy roaamagdy added bug Something isn't working triage needs to be looked at labels Nov 6, 2024
@MohabMohie
Copy link
Contributor

Dear @roaamagdy,
I'm unable to reproduce this with the latest engine version using the latest junit.

2025-02-18_23-20-02-649_AllureReport.zip

Would you kindly share more insights? I checked my console, allure, and the engine log files but couldn't capture it myself.

@MohabMohie MohabMohie added question Further information is requested and removed triage needs to be looked at labels Feb 18, 2025
@roaamagdy
Copy link
Author

Reproducible with latest shaft engine . I am using Junit and it is the concole logs and in pipline logs.

Image

@MohabMohie
Copy link
Contributor

Hi @roaamagdy
Can you kindly provide an allure report for further investigation?
I'm testing junit too and unable to reproduce the issue locally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants