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

In Visual Studio 2013 - Failed to start runner #504

Closed
david-m-forster opened this Issue Mar 10, 2016 · 12 comments

Comments

Projects
None yet
2 participants
@david-m-forster

david-m-forster commented Mar 10, 2016

Issue description or question

just reinstalled wallabyjs on a new visual studio 2013 update 5 installation and when I start wallaby.js i get the error in the bottom status bar:

Failed to start runner, see the output window or log file for more details :(

Wallaby used to work on my old VS installation (had to reinstall VS as my C drive got corrupted)

Turned on debug in wallaby.js but no error messages logged anywhere so very hard to provide any detailed info on this error. VS output console output "Referenced file '~/Scripts/_references.js' not found" once or twice but it is not written every time. Mostly, the VS output window is empty.

looked in "C:\Users\myusername\AppData\Local\Temp" but no .wallaby folder. Also no activitylog.xml file under MS location.

Wallaby.js configuration file

var wallabify = require('wallabify');
var wallabyPostprocessor = wallabify({});

module.exports = function () {
    return {
        /*
         * Notes:
         * - All browserifyed source files and tests should set 'load:false' 
         * - Defauilt of 'load:true' means file included via normal script tag
         * - files property should contain ALL files needed in test EXCEPT unit test entry pages
         * - tests property should contain ONLY test entry pages
         * - set debug to true to get detailed wallaby output 
         */
      files: [
          { pattern: 'test/lib/expect.js', load: true },
          { pattern: 'test/lib/sinon-1.17.0.js', load: true },
          { pattern: 'test/lib/jquery-1.10.2.min.js', load: true },
          { pattern: 'src/**/*.js', load: false },
          { pattern: 'lib/**/*.js', load: false },
          { pattern: 'test/src/**/*Tests.js', ignore: true }, // these files are excluded from "files"
          { pattern: 'test/src/**/*.js', load: false }
      ],

      tests: [
          // Each test entry page is loaded into browser (i.e phantom)
          { pattern: 'test/src/**/*Tests.js', load: false }
      ],

      testFramework: 'mocha',

      postprocessor: wallabyPostprocessor,

      debug: true,

      bootstrap: function () {
          // required to trigger tests loading
          window.__moduleBundler.loadTests();
      }
  };
};

Code editor or IDE name and version

Visual Studio 2013

OS name and version

Windows 8.1

@ArtemGovorov

This comment has been minimized.

Show comment
Hide comment
@ArtemGovorov

ArtemGovorov Mar 10, 2016

Member

VS output console output "Referenced file '~/Scripts/_references.js' not found" once or twice but it is not written every time. Mostly, the VS output window is empty.

Try selecting "Wallaby.js - Console" in the "Show output from:" combobox in the output window. Is there anything logged there?

Member

ArtemGovorov commented Mar 10, 2016

VS output console output "Referenced file '~/Scripts/_references.js' not found" once or twice but it is not written every time. Mostly, the VS output window is empty.

Try selecting "Wallaby.js - Console" in the "Show output from:" combobox in the output window. Is there anything logged there?

@david-m-forster

This comment has been minimized.

Show comment
Hide comment
@david-m-forster

david-m-forster Mar 10, 2016

Yeah that is the weird thing. I can't see any wallabyjs output in the output console.

image

image

Another colleague also tried installing wallaby (also VS 2013) and is getting the same error)

I installed it last time a couple of months back. I will try installing the last version of wallaby and see if that works.

david-m-forster commented Mar 10, 2016

Yeah that is the weird thing. I can't see any wallabyjs output in the output console.

image

image

Another colleague also tried installing wallaby (also VS 2013) and is getting the same error)

I installed it last time a couple of months back. I will try installing the last version of wallaby and see if that works.

@david-m-forster

This comment has been minimized.

Show comment
Hide comment
@david-m-forster

david-m-forster Mar 10, 2016

just an update

  • tried all the versions from wallaby-vs-2013-v1.0.16.vsix to wallaby-vs-2013-v1.0.21.vsix . all are exhibiting the same broken behaviour
  • downloaded the VS Wallaby-Sample from the wallaby.js repo, tried starting the plugin (v1.0.21) but get the same error
  • started VS with devenv /log and checked the generated activitylog.xml file but found nothing indicating a problem with the wallaby plugin

david-m-forster commented Mar 10, 2016

just an update

  • tried all the versions from wallaby-vs-2013-v1.0.16.vsix to wallaby-vs-2013-v1.0.21.vsix . all are exhibiting the same broken behaviour
  • downloaded the VS Wallaby-Sample from the wallaby.js repo, tried starting the plugin (v1.0.21) but get the same error
  • started VS with devenv /log and checked the generated activitylog.xml file but found nothing indicating a problem with the wallaby plugin
@ArtemGovorov

This comment has been minimized.

Show comment
Hide comment
@ArtemGovorov

ArtemGovorov Mar 10, 2016

Member

Could you please paste a screenshot of your C:\Users\myusername\.wallaby folder (core and dependencies subfolders)?

Member

ArtemGovorov commented Mar 10, 2016

Could you please paste a screenshot of your C:\Users\myusername\.wallaby folder (core and dependencies subfolders)?

@david-m-forster

This comment has been minimized.

Show comment
Hide comment
@david-m-forster

david-m-forster Mar 10, 2016

Sure. Note that there are no files under any of the folders - not sure why

image

david-m-forster commented Mar 10, 2016

Sure. Note that there are no files under any of the folders - not sure why

image

@ArtemGovorov

This comment has been minimized.

Show comment
Hide comment
@ArtemGovorov

ArtemGovorov Mar 10, 2016

Member

Thanks,
could you please delete the C:\Users\myusername\.wallaby folder completely, restart your VS and try starting wallaby?

Member

ArtemGovorov commented Mar 10, 2016

Thanks,
could you please delete the C:\Users\myusername\.wallaby folder completely, restart your VS and try starting wallaby?

@david-m-forster

This comment has been minimized.

Show comment
Hide comment
@david-m-forster

david-m-forster Mar 10, 2016

completed! deleted folder, started VS, opened wallaby-sample, chose start wallaby

result: .wallaby folder recreated but all subfolders still completely empty - and same error as before

david-m-forster commented Mar 10, 2016

completed! deleted folder, started VS, opened wallaby-sample, chose start wallaby

result: .wallaby folder recreated but all subfolders still completely empty - and same error as before

@ArtemGovorov

This comment has been minimized.

Show comment
Hide comment
@ArtemGovorov

ArtemGovorov Mar 10, 2016

Member

It's strange. Looks like wallaby extension can't download its dependencies.
Are you behind some proxy?
When you start wallaby after deleting the .wallaby folder, was it displaying Downloading core/PhantomJs/etc messages in the VS status bar?
Still no C:\Users\myusername\AppData\Local\Temp\.wallaby folder?
Do you have admin privileges on the machine/running VS as admin?

Member

ArtemGovorov commented Mar 10, 2016

It's strange. Looks like wallaby extension can't download its dependencies.
Are you behind some proxy?
When you start wallaby after deleting the .wallaby folder, was it displaying Downloading core/PhantomJs/etc messages in the VS status bar?
Still no C:\Users\myusername\AppData\Local\Temp\.wallaby folder?
Do you have admin privileges on the machine/running VS as admin?

@david-m-forster

This comment has been minimized.

Show comment
Hide comment
@david-m-forster

david-m-forster Mar 11, 2016

yep, always run as admin but the proxy may indeed be the problem. for some reason, last time I installed wallaby here (a couple of months ago) it wasn't a problem. looking at fiddler looks like it is failing on some requests so I need to get the machine on an open network (this is turning out to be a problem so will have to get back to you)

out of curiosity, is downloading dependencies a new thing? also, what is it downloading and is there a way I can manually grab the files it needs?

thanks

david-m-forster commented Mar 11, 2016

yep, always run as admin but the proxy may indeed be the problem. for some reason, last time I installed wallaby here (a couple of months ago) it wasn't a problem. looking at fiddler looks like it is failing on some requests so I need to get the machine on an open network (this is turning out to be a problem so will have to get back to you)

out of curiosity, is downloading dependencies a new thing? also, what is it downloading and is there a way I can manually grab the files it needs?

thanks

@ArtemGovorov

This comment has been minimized.

Show comment
Hide comment
@ArtemGovorov

ArtemGovorov Mar 11, 2016

Member

Downloading dependencies was in wallaby extension from day one. The very first time it's downloading PhantomJs, node.js, and wallaby.js core. The latter is also periodically automatically updated when we release its new versions.

You may download and install the dependencies manually, but to have the automatic core updates I'd still recommend to sort the proxy issue out. To manually install you will need to:

  • Download wallaby.js core from http://update.wallabyjs.com/wallaby-v1.0.334.zip.
  • Download PhantomJs from https://s3.amazonaws.com/wallaby-downloads/phantom/phantomjs-2.1.1-windows.zip.
  • Download node.js from https://s3.amazonaws.com/wallaby-downloads/node/v4.2.2/win-x64/node.exe if you're on 64 bit Win or from https://s3.amazonaws.com/wallaby-downloads/node/v4.2.2/win-x86/node.exe if you're on 32 bit one.
  • Open C:\Users\myusername\.wallaby and create core subfolder, nodejs\4.2.2 subfolder and phantomjs\2.1.1 subfolder.
  • In each of the created subfolders, create an empty file with installer.committed name.
  • Extract wallaby.js core downloaded archive somewhere and copy its contents to the core subfolder (so there's a server.js and a few other files and folders in the core subfolder).
  • Extract PhantomJs downloaded archive somewhere and copy its contents to the phantomjs\2.1.1 subfolder (so there's a phantomjs.exe and a few other files and examples folder in the phantomjs\2.1.1 subfolder).
  • Copy downloaded node.exe to the nodejs\4.2.2 subfolder.
Member

ArtemGovorov commented Mar 11, 2016

Downloading dependencies was in wallaby extension from day one. The very first time it's downloading PhantomJs, node.js, and wallaby.js core. The latter is also periodically automatically updated when we release its new versions.

You may download and install the dependencies manually, but to have the automatic core updates I'd still recommend to sort the proxy issue out. To manually install you will need to:

  • Download wallaby.js core from http://update.wallabyjs.com/wallaby-v1.0.334.zip.
  • Download PhantomJs from https://s3.amazonaws.com/wallaby-downloads/phantom/phantomjs-2.1.1-windows.zip.
  • Download node.js from https://s3.amazonaws.com/wallaby-downloads/node/v4.2.2/win-x64/node.exe if you're on 64 bit Win or from https://s3.amazonaws.com/wallaby-downloads/node/v4.2.2/win-x86/node.exe if you're on 32 bit one.
  • Open C:\Users\myusername\.wallaby and create core subfolder, nodejs\4.2.2 subfolder and phantomjs\2.1.1 subfolder.
  • In each of the created subfolders, create an empty file with installer.committed name.
  • Extract wallaby.js core downloaded archive somewhere and copy its contents to the core subfolder (so there's a server.js and a few other files and folders in the core subfolder).
  • Extract PhantomJs downloaded archive somewhere and copy its contents to the phantomjs\2.1.1 subfolder (so there's a phantomjs.exe and a few other files and examples folder in the phantomjs\2.1.1 subfolder).
  • Copy downloaded node.exe to the nodejs\4.2.2 subfolder.
@david-m-forster

This comment has been minimized.

Show comment
Hide comment
@david-m-forster

david-m-forster Mar 11, 2016

great thanks! excellent detail. Since I work at a financial institution I imagine they have locked down the firewall recently. Now that I have an idea what the problem likely is I will install wallaby at home and then copy the .wallaby folder and bring it into work.

david-m-forster commented Mar 11, 2016

great thanks! excellent detail. Since I work at a financial institution I imagine they have locked down the firewall recently. Now that I have an idea what the problem likely is I will install wallaby at home and then copy the .wallaby folder and bring it into work.

@ArtemGovorov

This comment has been minimized.

Show comment
Hide comment
@ArtemGovorov

ArtemGovorov Mar 11, 2016

Member

No worries, thanks the update.

install wallaby at home and then copy the .wallaby folder and bring it into work

That should work for you, just make sure your home Windows has the same bitness as your work one, otherwise you may need to replace the node.js version in the folder.

Member

ArtemGovorov commented Mar 11, 2016

No worries, thanks the update.

install wallaby at home and then copy the .wallaby folder and bring it into work

That should work for you, just make sure your home Windows has the same bitness as your work one, otherwise you may need to replace the node.js version in the folder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment