-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Comparing changes
Open a pull request
base repository: karma-runner/karma
base: v4.1.0
head repository: karma-runner/karma
compare: v4.2.0
- 13 commits
- 56 files changed
- 6 contributors
Commits on Apr 23, 2019
-
fix(server): Add error handler for webserver socket. (#3300)
Some times connection arrive, are given 404 responses, then disconnect, resulting in ECONNRESET errors on the socket. After we began monitoring UncaughtExceptions, these errors show up. Suppress them with a handler that ignores errors.
Configuration menu - View commit details
-
Copy full SHA for fe9a1dd - Browse repository at this point
Copy the full SHA fe9a1ddView commit details
Commits on May 15, 2019
-
chore: update braces and chokidar to latest versions (#3307)
This results in a significant dependencies reduction. New version of chokidar also promises significant memory and performance improvements.
Configuration menu - View commit details
-
Copy full SHA for 7828bea - Browse repository at this point
Copy the full SHA 7828beaView commit details
Commits on May 17, 2019
-
* chore: remove unused devDependencies * chore: update some devDependencies
Configuration menu - View commit details
-
Copy full SHA for 7f40349 - Browse repository at this point
Copy the full SHA 7f40349View commit details
Commits on May 23, 2019
-
chore(test): fix flaky test cases (#3314)
* fix(test): fixed flaky reconnecting test cc2eff2 introduced different behavior depending on whether socket reconnected or browser reconnected after reload. This lead to the reconnecting test being flaky as, depending on the timing, it will trigger second test run and result in unexpected output. * fix(test): remove broken monitor action for Cucumber The issue is that it resulted in the following sequence of actions: - run karma start - run karma run - and then instantly kill karma start command This resulted in flaky tests because the kill could race, resulting in incomplete output. In fact test was unnecessary complicated as it was enough to use runOut, which asserts output of the karma run command. * fix(test): guard from repeated executions of the karma run 'data' event handler may be called multiple times, which will result in multiple calls to karma run. To take it even further, its execution is delayed by setTimeout, which means that subsequent executions will run while next test scenario is in progress and may mess it up. To prevent this make sure that karma run is executed only once independently of how many time 'data' event is fired.
Configuration menu - View commit details
-
Copy full SHA for 1205bce - Browse repository at this point
Copy the full SHA 1205bceView commit details
Commits on May 25, 2019
-
chore: revert back to Mocha 4 (#3313)
Mocha 5+ dropped support for IE 8 and IE 9. This leads to failing BrowserStack tests, so reverting back to version 4 until Karma decides to drop support for the mentioned browsers.
Configuration menu - View commit details
-
Copy full SHA for 5e11340 - Browse repository at this point
Copy the full SHA 5e11340View commit details
Commits on Jun 3, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 3aea7ec - Browse repository at this point
Copy the full SHA 3aea7ecView commit details
Commits on Jun 4, 2019
-
Configuration menu - View commit details
-
Copy full SHA for f0c4677 - Browse repository at this point
Copy the full SHA f0c4677View commit details
Commits on Jun 17, 2019
-
fix(reporter): format stack with 1-based column (#3325)
Columns in original stack are 1-based, but SourceMapConsumer.prototype.originalPositionFor(generatedPosition) accepts 0-based column and returns 0-based column too. This change converts columns from 1-based to 0-based forth and back. Closes #3324
Configuration menu - View commit details
-
Copy full SHA for 182c04d - Browse repository at this point
Copy the full SHA 182c04dView commit details
Commits on Jul 1, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 1087926 - Browse repository at this point
Copy the full SHA 1087926View commit details
Commits on Jul 12, 2019
-
fix(logging): Util inspect for logging the config. (#3332)
While flatten is accruate and works with circular data, it's too hard to read.
Configuration menu - View commit details
-
Copy full SHA for 70b72a9 - Browse repository at this point
Copy the full SHA 70b72a9View commit details -
Configuration menu - View commit details
-
Copy full SHA for a1049c6 - Browse repository at this point
Copy the full SHA a1049c6View commit details -
Configuration menu - View commit details
-
Copy full SHA for db1ea57 - Browse repository at this point
Copy the full SHA db1ea57View commit details -
Configuration menu - View commit details
-
Copy full SHA for 42933c9 - Browse repository at this point
Copy the full SHA 42933c9View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v4.1.0...v4.2.0