Commit d348df3
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
1 file changed
+1
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
64 | 64 | | |
65 | 65 | | |
66 | 66 | | |
| 67 | + | |
67 | 68 | | |
68 | 69 | | |
69 | 70 | | |
| |||
0 commit comments