fix(ci): force examples sequential run for luacov #4043
Merged
+8
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For some times now, the coverage numbers are crazy. I found one reason with the way we run the examples tests in the CI: we have a
-j24to make them run faster. This is causing trouble with how theluacov.stats.outis written.This PR adds a new step for coverage where we run check-examples sequentially while preserving a faster step with the
-jflag, so other jobs provides faster feedbacks.