-
Notifications
You must be signed in to change notification settings - Fork 43
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
(Ruby - Cucumber)Not all scenarios are shown in report when they are run in parallel #83
Comments
@aliaksandr-trush, @abotalov, any ides? |
Dudes DO you have any ideas? |
|
Also I have seen this warnings and errors in log
|
Will be it enough details? |
Aso I have seen that for example from 4 threads in report I have 3 threads, so some threads are not shown in RP or not launch |
@aliaksandr-trush can you assist with it? |
@DzmitryHumianiuk There has been some work done to work on the parallel executions, it is unfortunately in a branch. I can confirm that there are issues when running in parallel but we have worked to reduce those issues. |
#33 << work that has been done. I need to do some more fixes though. |
@mikesalvia i see it merged. |
It targeted a different branch. I'm not sure if that branch was properly tested. |
Is this still active!? |
@mikesalvia No one knows. There is no Ruby contributor. |
Oh yikes! |
Describe the bug
When I run scenarios for example in 5 threads (1350 scenarios) (via parallel_tests gem), I can see only 3 threads (940 scenarios for example) in Repost Portal launch. I cannot see all scenarios which should be run. I have thoughts that a not all scenarios are run with
-f ReportPortal::Cucumber::ParallelFormatter
.When I have run scenarios with default html report everything good. I have seen for request in build log such things with params
/item?filter.eq.parent=5bf30a0bb9d8210001c48485&filter.eq.name=Folder:%20scenarios
produced an exception:Expected behavior
I should see all 5 threads in launch and all run scenarios
Versions:
-Mac OS
[Current version: Analysis Service: 4.3.0; API Service: 4.3.0; Index Service: 4.2.0; Jira Service: 4.3.0; Rally Service: 4.3.0; Authorization Service: 4.2.0; Service UI: 4.3.0; ]
The text was updated successfully, but these errors were encountered: