try concurrency for module tests

Author: Narretz

karma-modules.conf.js

@@ -6,7 +6,10 @@ var sharedConfig = require('./karma-shared.conf');
 module.exports = function(config) {
   var angularModule = process.env.KARMA_MODULE;
 
-  sharedConfig(config, {testName: 'AngularJS: module ' + angularModule, logFile: 'karma-modules-' + angularModule + '.log'});
+  sharedConfig(config, {
+    testName: 'AngularJS: module ' + angularModule,
+    logFile: 'karma-modules-' + angularModule + '.log'
+  });
 
   config.set({
     files: angularFiles.mergeFilesFor('karmaModules-' + angularModule)

karma-shared.conf.js

@@ -177,6 +177,8 @@ module.exports = function(config, specificOptions) {
   if (process.env.TRAVIS) {
     var buildLabel = 'TRAVIS #' + process.env.TRAVIS_BUILD_NUMBER + ' (' + process.env.TRAVIS_BUILD_ID + ')';
 
+    config.concurrency = 4;
+
     // Karma (with socket.io 1.x) buffers by 50 and 50 tests can take a long time on IEs;-)
     config.browserNoActivityTimeout = 120000;
 
@@ -195,12 +197,12 @@ module.exports = function(config, specificOptions) {
       filename: process.env.LOGS_DIR + '/' + (specificOptions.logFile || 'karma.log')
     });
 
-    if (process.env.BROWSER_PROVIDER === 'saucelabs' || !process.env.BROWSER_PROVIDER) {
-      // Allocating a browser can take pretty long (eg. if we are out of capacity and need to wait
-      // for another build to finish) and so the `captureTimeout` typically kills
-      // an in-queue-pending request, which makes no sense.
-      config.captureTimeout = 0;
-    }
+    // if (process.env.BROWSER_PROVIDER === 'saucelabs' || !process.env.BROWSER_PROVIDER) {
+    //   // Allocating a browser can take pretty long (eg. if we are out of capacity and need to wait
+    //   // for another build to finish) and so the `captureTimeout` typically kills
+    //   // an in-queue-pending request, which makes no sense.
+    //   config.captureTimeout = 0;
+    // }
   }