|
Ran
|
Jobs
3
|
Files
124
|
Run time
7min
|
Badge
README BADGES
|
push
travis-ci
<a href="https://github.com/wikimedia/parsoid/commit/7dee7f51f">Fix console.assert when running under node >= 0.10 For browser compatibility (I guess) in Node v10, console.assert() was changed to log messages to stderr *WITHOUT THROWING AN EXCEPTION*. That interacts poorly with our service framework, which relies on exception handling to return error pages, and with various places in our code which assume that console.assert() can't fall through. In theory we should probably switch to a "better" assertion library. But since we don't use console.assert very much anyway, and we're switching to PHP (with its own assertion library), for the moment just hack console.assert() to ensure it throws an exception the way it always used to. Change-Id: I</a><a class="double-link" href="https://github.com/wikimedia/parsoid/commit/223370d23">223370d23</a>
9557 of 12045 branches covered (79.34%)
14772 of 17537 relevant lines covered (84.23%)
94168.24 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 2537.1 | 0 |
84.23 |
Travis Job 2537.1 | |
| 2 | 2537.2 | 0 |
84.23 |
Travis Job 2537.2 | |
| 3 | 2537.3 | 0 |
84.23 |
Travis Job 2537.3 |