Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Fail on load-errors. #1931

Merged

Conversation

budde377
Copy link
Member

Stop karma if a launcher, reporter, plugin, or preprocessor fails to
load, after attempting to load each of them, and reporting errors for
each load error.

Also someone should prob. tell @nikku that the karma-browserify
plugin is going to stop working due the changed signature of
createPreprocessor.

Closes #855

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.

@budde377
Copy link
Member Author

@srawlins, can you sign the CLA?

@nikku
Copy link

nikku commented Feb 25, 2016

@nikku does not like that change for the reason you mentioned (createPreprocessor syntax changed).

Isn't there another way to implement that in a backward compatible manner?

@budde377
Copy link
Member Author

@nikku Sorry for the indirection.
I might have an idea.

@budde377 budde377 force-pushed the issue-855-fail-on-load-errors branch 2 times, most recently from 21a3e46 to cd24d95 Compare February 25, 2016 20:45
@dignifiedquire
Copy link
Member

@budde377 is this ready for review?

@budde377
Copy link
Member Author

@dignifiedquire, yes. I don't know what to do about the missing CLA from @srawlins.

@googlebot
Copy link

CLAs look good, thanks!

@@ -11,7 +11,7 @@ var processDecorator = require('./launchers/process').decoratorFactory

// TODO(vojta): remove once nobody uses it
var baseBrowserDecoratorFactory = function (baseLauncherDecorator, captureTimeoutLauncherDecorator,
retryLauncherDecorator, processLauncherDecorator) {
retryLauncherDecorator, processLauncherDecorator) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's not do this please, instead use this indentation:

var name = function (
  arg1,
  arg2,
  arg3
) {
  // body
}

@dignifiedquire dignifiedquire self-assigned this Mar 1, 2016
…ors.

Stop karma if a launcher, reporter, plugin, or preprocessor fails to
load, after attempting to load each of them, and reporting errors for
each load error.

Closes karma-runner#855
@budde377 budde377 force-pushed the issue-855-fail-on-load-errors branch from 9c705a7 to fca930e Compare March 1, 2016 15:31
@dignifiedquire
Copy link
Member

Closes #855

@dignifiedquire dignifiedquire added this to the v1.0 milestone Mar 3, 2016
@dignifiedquire
Copy link
Member

Thanks a lot @budde377 and @srawlins for making this happen!

dignifiedquire added a commit that referenced this pull request Mar 4, 2016
@dignifiedquire dignifiedquire merged commit e83bfd7 into karma-runner:master Mar 4, 2016
@budde377
Copy link
Member Author

budde377 commented Mar 4, 2016

@dignifiedquire I just want to notice, that I didn't do the whole extract server from injector thing, so we might see some launchers breaking if they rely on the signature of the launcer.

@dignifiedquire
Copy link
Member

@budde377 yeah I realised that, but I wanted to get it in, will fix reporters when they tell us, this is not really documented stable api anyway

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants