-
Notifications
You must be signed in to change notification settings - Fork 188
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
Duplicate history trends #110
Comments
@apulverizer yes, it's duplicated the #1 execution but there is no results. It didn't affect your metrics. you see twice but both have no results. |
Thanks for looking into it @fescobar However, I don't think it only happens on the first execution. It seems to be on every execution.
You can see there are 2 entries for both |
@apulverizer you are already using When you clean your results, the files automatically are detected, then execute generate-report. For that reason you have to apply correctly
delete all your local folders, after that
|
@fescobar yeah that's what I did.
In the servers logs I only see the intentionally triggered reports. I still see the duplicate results though. |
@apulverizer can you attach logs?
|
@apulverizer you are right, I will fix soon. |
@apulverizer can you check
I will be waiting for your feedback. Thank you again. |
The change looks good. Thanks for resolving this @fescobar |
@apulverizer I'm removing |
Verified with version |
I am facing this again in Single project mode. |
It seems like the history trend is invalid.
Here is a simple repro case using the sample data:
allure-api-usage
directory callpython send_results.py
generate-report
on thedefault
projectAfter a single test run I'm seeing a trend chart like:
Notice there are two entries for
#1
this seems invalid.Running
allure server allure-results-example/
locally renders it like:which is what I expect to see.
It seems like the history is getting duplicated somehow.
Logs:
This is my compose file:
The text was updated successfully, but these errors were encountered: