|
Ran
|
Jobs
1
|
Files
10
|
Run time
2s
|
Badge
README BADGES
|
push
travis-ci
<a href="https://github.com/rhaendel/goos/commit/<a class=hub.com/rhaendel/goos/commit/581a01c57274ed8902fb454311188afbfde16cce">581a01c57<a href="https://github.com/rhaendel/goos/commit/581a01c57274ed8902fb454311188afbfde16cce">">Try to address a Windowlicker timing problem Windowlicker has a timing problem in version r268. It is discussed on https://groups.google.com/forum/#!topic/growing-object-oriented-software/aEFI72rjn7w Nat Pryce advises to use Google&#39;s WindowTester instead of Windowlicker. Other users were successful in using a DEV version of Windowlicker. So I am going this way. (cherry picked from commit </a><a class="double-link" href="https://github.com/rhaendel/goos/commit/<a class="double-link" href="https://github.com/rhaendel/goos/commit/badc8eb35ee423af8aafc465da23b10bfc798237">badc8eb35</a>">badc8eb35</a><a href="https://github.com/rhaendel/goos/commit/581a01c57274ed8902fb454311188afbfde16cce">) Unfortunately the repository "https://ibuzz-csd.googlecode.com/hg/maven-repository" is not available anymore as it was at timme committing badc8eb35ee423af8aa. So i directly took the jars from https://github.com/edzhelyov/goos/tree/master/lib and committed them to the lib directory.
197 of 213 relevant lines covered (92.49%)
0.92 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 79.1 (TERM=dumb) | 0 |
92.49 |
Travis Job 79.1 |