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

Test Metrics Count Incorrect in ReportPortal #178

Open
Priyanshu19992002 opened this issue Apr 5, 2024 · 2 comments
Open

Test Metrics Count Incorrect in ReportPortal #178

Priyanshu19992002 opened this issue Apr 5, 2024 · 2 comments

Comments

@Priyanshu19992002
Copy link

Hi Team,

We have a serenity bdd cucumber framework in which we are using ReportPortal v23.1 with below dependency version:
Serenity - v3.3.10
Serenity-ReportPortal-Integration - v1.5.7

We are facing problem with respect to test counts in ReportPortal. We have executed the tests in parallel. The test metrics in ReportPortal is not matching with the actual test case executed. The error logs which we are seeing is as below:

07:01:54.055 [rp-io-39] ERROR c.e.r.utils.SubscriptionUtils - Start test item completed with error
2024-04-05T07:01:54.0902133Z com.epam.reportportal.exception.ReportPortalException: Report Portal returned error
2024-04-05T07:01:54.0903045Z Status code: 406
2024-04-05T07:01:54.0903627Z Status message: Not Acceptable
2024-04-05T07:01:54.0905013Z Error Message: Start time of child ['Fri Apr 05 06:52:56 UTC 2024'] item should be same or later than start time ['2024-04-05T06:52:58.183'] of the parent item/launch '9828'
2024-04-05T07:01:54.0906165Z Error Type: CHILD_START_TIME_EARLIER_THAN_PARENT
2024-04-05T07:01:54.0906596Z
2024-04-05T07:01:54.0907847Z at com.epam.reportportal.service.ReportPortalErrorHandler.handleError(ReportPortalErrorHandler.java:85)
2024-04-05T07:01:54.0909470Z at com.epam.reportportal.service.ReportPortalErrorHandler.handle(ReportPortalErrorHandler.java:61)
2024-04-05T07:01:54.0911132Z at com.epam.reportportal.restendpoint.http.HttpClientRestEndpoint$1.subscribe(HttpClientRestEndpoint.java:526)
2024-04-05T07:01:54.0912856Z at io.reactivex.internal.operators.maybe.MaybeCreate.subscribeActual(MaybeCreate.java:45)
2024-04-05T07:01:54.0914102Z at io.reactivex.Maybe.subscribe(Maybe.java:4290)
2024-04-05T07:01:54.0915264Z at io.reactivex.internal.operators.maybe.MaybeSubscribeOn$SubscribeTask.run(MaybeSubscribeOn.java:54)
2024-04-05T07:01:54.0916941Z at io.reactivex.internal.schedulers.ScheduledDirectTask.call(ScheduledDirectTask.java:38)
2024-04-05T07:01:54.0918395Z at io.reactivex.internal.schedulers.ScheduledDirectTask.call(ScheduledDirectTask.java:26)
2024-04-05T07:01:54.0919259Z at java.util.concurrent.FutureTask.run(FutureTask.java:266)
2024-04-05T07:01:54.0919922Z at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
2024-04-05T07:01:54.0920644Z at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
2024-04-05T07:01:54.0921187Z at java.lang.Thread.run(Thread.java:750)

What can be the possible reason behind this?

@grey-rain
Copy link
Collaborator

hi @Priyanshu19992002 !
Could you please let me know how are your tests paralleled? There are multiple ways to do it in Cucumber. It would be great if you could provide test sample which helps to replicate the issue.
BTW, is there a chance to try the same with the latest integration version 1.6.0?

@Priyanshu19992002
Copy link
Author

Hi @grey-rain ,

  1. We are using Serenity v3.3.10 in which we are running our test parallely at feature level.
  2. We have serenity bdd framework in place where we test multiple applications (each application test are running in parallel at feature level). We are observing the above mentioned issue with respect to one particular application in which a single test takes longer time to execute in comparison to other application. Could this be the reason for this particular issue pls clarify and let us know for further questions.

Note- We haven't tried with v1.6.0 since it is not compatible with serenity v3.3.10.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants