Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Merge reports for parallel builds
See original GitHub issueI’m using this action on a matrix based build https://github.com/websockets/ws/blob/use/github-actions/.github/workflows/ci.yml.
I’ve defined a test job which is run in parallel and in this job I run the action with the parallel option set to true.
https://github.com/websockets/ws/blob/use/github-actions/.github/workflows/ci.yml#L32
I’ve also defined a coverage job which is run after all test jobs complete. In this job I run the action with the parallel-finished option set to true.
https://github.com/websockets/ws/blob/use/github-actions/.github/workflows/ci.yml#L40
This works well but it seems results are not aggregated. Am I doing something wrong?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:16 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Interesting. Thanks for the clarification as I was trying to understand how could this affect my own projects and I wasn’t seeing a use case where coverage would be different. Thanks 😃
@lpinca good catch, we’ve deployed an update that should fix those Job numbers moving forward.
Thanks!