Ran
|
Jobs
4
|
Files
24
|
Run time
53s
|
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.
1 of 1 new or added line in 1 file covered. (100.0%)
310 of 350 relevant lines covered (88.57%)
63.83 hits per line
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
1 | 465.1 | 22 |
88.71 |
Travis Job 465.1 | |
2 | 465.2 | 22 |
88.95 |
Travis Job 465.2 | |
3 | 465.3 | 22 |
88.95 |
Travis Job 465.3 | |
4 | 465.4 | 22 |
88.92 |
Travis Job 465.4 |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|