Skip to content

Random error with async reporting #175

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.

Sign up for GitHub

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

Jump to bottom
Closed
babantax opened this issue Oct 18, 2023 · 2 comments
Closed

Random error with async reporting #175

babantax opened this issue Oct 18, 2023 · 2 comments
Assignees
@grey-rain
Labels
investigation required waiting feedback

Comments

@babantax
Copy link
Contributor

Hello!

Just testing release 1.6.0 and If I use async reporting rp.reporting.async = true, half of the launches more or less are lost.

With rp.reporting.async = false is working fine. Not sure if this bug is related to this repository or is on the client-java 5.1.22 dependency, see more info here.

Thank a lot in advance
@grey-rain grey-rain self-assigned this Oct 21, 2023
@grey-rain
Copy link
Collaborator

grey-rain commented Oct 22, 2023 •
edited
Loading

@babantax hello! I am not sure where this issue should reside... never happened to me. lets try investigating it together! :)
are results missed only in ReportPortal, e.g do you still see native Serenity report for those executions?

P.S. I found this issue related to async reporting #118 . It seems like (prety long time ago) it behaved differently for async reporting from what you describe.

@grey-rain
Copy link
Collaborator

abandoned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@grey-rain grey-rain

Labels
investigation required waiting feedback
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@grey-rain @babantax