Ran
|
Jobs
6
|
Files
35
|
Run time
2min
|
Badge
Embed ▾
README BADGES
|
push
travis-ci
<a href="https://github.com/napalm-automation/napalm/commit/<a class=hub.com/napalm-automation/napalm/commit/c54cbd13f501642c5575da68f6e3bf1b07564d00">c54cbd13f<a href="https://github.com/napalm-automation/napalm/commit/c54cbd13f501642c5575da68f6e3bf1b07564d00">">Add GitHub issue template, as we used to have before When we used to maintain separare NAPALM drivers, we had an issue template looking like this: https://github.com/napalm-automation/napalm-junos/commit/</a><a class="double-link" href="https://github.com/napalm-automation/napalm/commit/<a class="double-link" href="https://github.com/napalm-automation/napalm/commit/110fec4bc9c50da43701b5019ecd859cc3c35f54">110fec4bc</a>">110fec4bc</a><a href="https://github.com/napalm-automation/napalm/commit/c54cbd13f501642c5575da68f6e3bf1b07564d00">#diff-faa36bc26a21ed93c8de974753b71507. I was looking today through the issues we currently have open, and I found some of them a bit chaotic, and hard to understand the context / environment the user runs. Additionally, some, e.g., #960, is really hard to follow, and I've included a note to invite the user to check the HitGub markdown manual.
4892 of 6099 relevant lines covered (80.21%)
2.4 hits per line
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
1 | 2223.1 | 35 |
80.03 |
Travis Job 2223.1 | |
2 | 2223.2 | 35 |
80.13 |
Travis Job 2223.2 | |
3 | 2223.3 | 35 |
80.13 |
Travis Job 2223.3 | |
4 | 2223.4 (TOXENV=pylama) | 0 | Travis Job 2223.4 | ||
5 | 2223.5 (TOXENV=black) | 0 | Travis Job 2223.5 | ||
6 | 2223.6 (TOXENV=sphinx) | 0 | Travis Job 2223.6 |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|