Ran
|
Files
22
|
Run time
2s
|
Badge
Embed ▾
README BADGES
|
travis-ci
Parallel support for separate CircleCI Workflow jobs `CIRCLE_WORKFLOW_WORKSPACE_ID` is the same when "Rerun failed job" is done while `CIRCLE_WORKFLOW_ID` changes, so use `CIRCLE_WORKFLOW_WORKSPACE_ID` for `service_number`, so that the results from the original and rerun are combined. Use `CIRCLE_BUILD_NUM` for `service_number` either in or out of Workflows. This appears to match the usage of `service_number` and `service_job_id` in https://github.com/lemurheavy/coveralls-ruby/commit/cf20b3a32, which added parallel support for the older, parallel-in-1-job system to coveralls-ruby - service_job_id varies over the parallel things while service_number must be the same across all parallel siblings.
329 of 370 relevant lines covered (88.92%)
17.17 hits per line
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|