can't run the tests

[andrewrk]

$ npm test

> aws-sdk@2.0.4 test /home/andy/dev/aws-sdk-js
> npm -s run-script lint && npm -s run-script unit && npm -s run-script buildertest && npm -s run-script browsertest && ([ -f configuration ] && npm -s run-script integration || true)


/home/andy/dev/aws-sdk-js/node_modules/jasmine-node/lib/jasmine-node/reporter.js:336
  jasmineNode.TeamcityReporter.prototype = new jasmine.TeamcityReporter;
                                           ^
TypeError: undefined is not a function
    at /home/andy/dev/aws-sdk-js/node_modules/jasmine-node/lib/jasmine-node/reporter.js:336:44
    at Object.<anonymous> (/home/andy/dev/aws-sdk-js/node_modules/jasmine-node/lib/jasmine-node/reporter.js:342:3)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/home/andy/dev/aws-sdk-js/node_modules/jasmine-node/lib/jasmine-node/index.js:34:21)
    at Module._compile (module.js:456:26)
npm ERR! Test failed.  See above for more details.
npm ERR! not ok code 0

[lsegal]

It looks like there's a regression in the latest jasmine-node. I noticed
build failures on Travis for this too.

On July 3, 2014 6:11:13 PM Andrew Kelley notifications@github.com wrote:

$ npm test

> aws-sdk@2.0.4 test /home/andy/dev/aws-sdk-js
> npm -s run-script lint && npm -s run-script unit && npm -s run-script 
buildertest && npm -s run-script browsertest && ([ -f configuration ] && 
npm -s run-script integration || true)


/home/andy/dev/aws-sdk-js/node_modules/jasmine-node/lib/jasmine-node/reporter.js:336
  jasmineNode.TeamcityReporter.prototype = new jasmine.TeamcityReporter;
                                           ^
TypeError: undefined is not a function
    at 
    /home/andy/dev/aws-sdk-js/node_modules/jasmine-node/lib/jasmine-node/reporter.js:336:44
    at Object.<anonymous> 
    (/home/andy/dev/aws-sdk-js/node_modules/jasmine-node/lib/jasmine-node/reporter.js:342:3)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> 
    (/home/andy/dev/aws-sdk-js/node_modules/jasmine-node/lib/jasmine-node/index.js:34:21)
    at Module._compile (module.js:456:26)
npm ERR! Test failed.  See above for more details.
npm ERR! not ok code 0

---

Reply to this email directly or view it on GitHub:
#313

[andrewrk]

I recommend locking the major and minor versions of dependencies, including devDependencies.

[lsegal]

We typically do lock devDepencies to major versions-- jasmine-node was not. That said, locking to any version of jasmine-node in this case would not have resolved this failure as the regression occurred in a dependent package of jasmine-node. The only way we could have avoided this would be by generating a shrinkwrap, which unfortunately is not feasible. The workaround for now would be to run:

npm install jasmine-reporters@1.x

[lsegal]

Fixed by a temporary adjustment to the package.json in db52a5b. I've actually been working on a long-running branch to move over to mocha, so I will work on that as a permanent fix.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.