Qiskit
/
qiskit
/
30291239050
88%
main: 88%
main: 88%
|
Ran
|
Jobs
1
|
Files
950
|
Run time
3min
|
Badge
Embed ▾
README BADGES
|
coverage: 87.636% (+0.006%) from 87.63%
push
github
web-flowFix failure reporting on Windows CI runners (#16608) (#16668) * Fix failure reporting on Windows CI runners The Windows unit test runs were somewhat misconfigured. The were previously failing to propagate failures in the set-up jobs up to the exit status of the shell, which manifested as errors around locating an `stestr` executable while trying to run the test suite when the actual error was in a `pip install` command in a prior step. This was masked because `cmd.exe` doesn't have an easy equivalent to `set -e` (or at least, not one I know / found out about), and the last command in the installation step was a `pip check`. Separately, the environment configuration for the test-runner step had got lost, and was being applied only to the `stestr history` pruning. The easiest fix for this is just to centralise everything on `bash` and use its `set -e`. Inserting an extra `--group optionals` by variable expansion allows us to install all the packages in a single step, obviating the need for a `pip check` anyway. * Match environment variables with Unix-likes (cherry picked from commit 09981b135) Co-authored-by: Jake Lishman <jake.lishman@ibm.com>
112846 of 128767 relevant lines covered (87.64%)
996743.06 hits per line
Coverage Regressions
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 6 |
97.15 |
0.47% | crates/qasm2/src/parse.rs |
| 4 |
91.52 |
0.26% | crates/qasm2/src/lex.rs |
| 1 |
93.88 |
-0.24% | crates/qasm2/src/expr.rs |
Jobs
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 30291239050.1 | 950 |
87.64 |
GitHub Action Run |
