Skip to content

Commit d348df3

Browse files
authored
Use coverage flags to distinguish between runs (#261)
Currently, we run separate coverage jobs for the different software versions. We run unit and integration tests for - The lowest supported CB3 version with a UR5 (Currently 3.14.3) - The lowest suppoted PolyScope 5 version with a UR5e (Currently 5.9.4) - The latest PolyScope 5 version with a UR20 All of these gather coverage data, but take different branches in the code due to version-dependent execution. As we generate and upload coverage data for all of them, coverage data varies slightly. This approach uses individual flags for each matrix entry. I am not 100% sure whether this does what we want, but I want to give it a try.
1 parent c956c83 commit d348df3

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

.github/workflows/ci.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,7 @@ jobs:
6464
with:
6565
fail_ci_if_error: true
6666
token: ${{ secrets.CODECOV_TOKEN }}
67+
flags: ${{ matrix.env.ROBOT_MODEL }}-${{ matrix.env.URSIM_VERSION }}
6768
- name: Generate URSim log files
6869
if: always()
6970
run: |

0 commit comments

Comments
 (0)