Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: karma-runner/karma
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v3.1.3
Choose a base ref
...
head repository: karma-runner/karma
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v3.1.4
Choose a head ref
  • 5 commits
  • 13 files changed
  • 4 contributors

Commits on Dec 6, 2018

  1. fix(file-list): revert "do not preprocess up-to-date files" (#3226) (#…

    …3230)
    
    This reverts commit 5334d1a
    karma-webpack preprocessor updates bundle when needed, but karma's fileList consists of a single entry file which is usually unmodified. In this case, fileList.refresh() should always call preprocessor for the single entry file, avoiding preprocessing of unmodified files is done on karma-webpack side.
    segrey authored and johnjbarton committed Dec 6, 2018
    1 Configuration menu
    Copy the full SHA
    bb022a7 View commit details
    Browse the repository at this point in the history

Commits on Dec 8, 2018

  1. Configuration menu
    Copy the full SHA
    584dddc View commit details
    Browse the repository at this point in the history

Commits on Dec 17, 2018

  1. fix: restarted browsers not running tests (#3233)

    * fix: restarted browsers not running tests
    
    Currently whenever a browser disconnects completely (no socket.io connection loss), the launcher is instructed to "restart" the browser. Whenever the restarted browser now tries to "register" again, Karma considers the browser instance to be still executing and doesn't do anything about it (except setting the state to `EXECUTING` again).
    
    This means that the browser is in the state of executing, but
    practically it does nothing just waits. Resulting another disconnect
    (repeat here).
    
    * test: add unit test that covers disconnected restarted browsers
    
    * fixup! test: add unit test that covers disconnected restarted browsers
    
    Address feedback
    
    * fixup! test: add unit test that covers disconnected restarted browsers
    
    Improve comments & log messages
    devversion authored and johnjbarton committed Dec 17, 2018
    Configuration menu
    Copy the full SHA
    cc2eff2 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    10df4ad View commit details
    Browse the repository at this point in the history
  3. chore: release v3.1.4

    johnjbarton committed Dec 17, 2018
    Configuration menu
    Copy the full SHA
    b8b8618 View commit details
    Browse the repository at this point in the history
Loading