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

Report generation broken if multiple browsers run in parallel #14

Open
dpoetzsch opened this issue Mar 23, 2020 · 2 comments
Open

Report generation broken if multiple browsers run in parallel #14

dpoetzsch opened this issue Mar 23, 2020 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@dpoetzsch
Copy link
Contributor

Describe the bug
If multiple browsers run in parallel the generated report is often broken. I guess this is because multiple processes are accessing the report.json file in parallel, leading to all kinds of race conditions.

To Reproduce
Steps to reproduce the behavior:

  1. Run multple browsers in parallel
  2. The generated report often only contains results from one browser.

Expected behavior

I'd expect all matching results to be present in the report.json. Alternatively, it would be totally ok, if each browser generates its own report.json.

Desktop (please complete the following information):

  • OS: Fedora Linux 31
  • Browser Chrome + Firefox (both headless)
  • Version 1.0.0

Additional context
Add any other context about the problem here.

@dpoetzsch dpoetzsch added the bug Something isn't working label Mar 23, 2020
@ennjin
Copy link
Owner

ennjin commented Mar 23, 2020

Hi, I checked parallel performance and got the correct result. You can checkout for master branch, build the project and run e2e job.

@dpoetzsch
Copy link
Contributor Author

dpoetzsch commented Mar 23, 2020

Interesting. I actually cannot reproduce the behavior with the tests in this repository as well.

However, I can reproduce it reliably with my test suite. Sadly this is a private repo, so I cannot provide access to it, but I can show you what I mean in a screencast: https://streamable.com/x0gih.

Something I did notice though, is that your report contains a browser property, while mine doesn't. I will continue investigating...

EDIT: Just checked, the browser property is probably not it. Maybe it is a cucumber thing?

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

No branches or pull requests

2 participants