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

Tests fail with a number or errors and warnings #5

Open
nfriedly opened this issue Oct 15, 2014 · 1 comment
Open

Tests fail with a number or errors and warnings #5

nfriedly opened this issue Oct 15, 2014 · 1 comment

Comments

@nfriedly
Copy link

Hi, I started working on a MongoDB plugin based off of this one, and I kept getting strange test failures, so it occurred to me to run the tests on this plugin, and sure enough, they're failing too:

$ cake test
cake compile
cake install
npm install (for app)
npm install (for test)
npm install (for docpad tests)
coffee compile
npm test

> docpad-plugin-tumblr@2.0.6 test c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master
> node ./out/tumblr.test.js

tumblr-master
tumblr-master > create
warning: The plugin tumblr-master uses an invalid naming convention. We only allow alphanumeric characters (no symbols). Perhaps change it t
o tumblrmaster
For more information about what this means, visit:
    http://docpad.org/plugin-conventions
warning: The plugin tumblr-master is using a different name (tumblr) for its prototype name. This can cause issues.
For more information about what this means, visit:
    http://docpad.org/plugin-conventions
notice: If everyone who saw this message donated $1/week, maintaining DocPad would become sustainable: http://docpad.org/donate
error: An error occured:
Error: Didn't place the skeleton as the desired structure already exists
  at c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\node_modules\docpad\out\lib\docpad.js:4107:17
  at Object.cb [as oncomplete] (fs.js:168:19)
error: To report the above error, follow the guide at: http://docpad.org/bug-report
tumblr-master > create OK
tumblr-master > load plugin tumblr-master
tumblr-master > load plugin tumblr-master OK
tumblr-master > generate
tumblr-master > generate > action
error: An error occured:
Error: Tumblr plugin is not configured correctly
  at TumblrPlugin.fetchTumblrData (c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\out\tumblr.plugin.js:59:17)
  at TumblrPlugin.populateCollections (c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\out\tumblr.plugin.js:165:14)
  at ambi (c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\node_modules\docpad\node_modules\ambi\out\lib\ambi.js:55:18)
  at Task.<anonymous> (c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\node_modules\docpad\node_modules\event-emitter-grouped\out\l
ib\event-emitter-grouped.js:45:23)
  at ambi (c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\node_modules\docpad\node_modules\ambi\out\lib\ambi.js:55:18)
  at fire (c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\node_modules\docpad\node_modules\taskgroup\out\lib\taskgroup.js:384:27)
  at b (domain.js:183:18)
  at Domain.run (domain.js:123:23)
  at Task.fire (c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\node_modules\docpad\node_modules\taskgroup\out\lib\taskgroup.js:398
:25)
  at Object._onImmediate (c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\node_modules\docpad\node_modules\taskgroup\out\lib\taskgr
oup.js:414:26)
  at processImmediate [as _immediateCallback] (timers.js:345:15)
error: To report the above error, follow the guide at: http://docpad.org/bug-report
tumblr-master > generate > action ERR!
tumblr-master > generate ERR!
tumblr-master ERR!

FAILURE: 2/3 tests ran successfully; 1 failed, 0 incomplete, 1 errors

Error #1:
tumblr-master > generate > action
Error: Tumblr plugin is not configured correctly
  at TumblrPlugin.fetchTumblrData (c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\out\tumblr.plugin.js:59:17)
  at TumblrPlugin.populateCollections (c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\out\tumblr.plugin.js:165:14)
  at ambi (c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\node_modules\docpad\node_modules\ambi\out\lib\ambi.js:55:18)
  at Task.<anonymous> (c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\node_modules\docpad\node_modules\event-emitter-grouped\out\l
ib\event-emitter-grouped.js:45:23)
  at ambi (c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\node_modules\docpad\node_modules\ambi\out\lib\ambi.js:55:18)
  at fire (c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\node_modules\docpad\node_modules\taskgroup\out\lib\taskgroup.js:384:27)
  at b (domain.js:183:18)
  at Domain.run (domain.js:123:23)
  at Task.fire (c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\node_modules\docpad\node_modules\taskgroup\out\lib\taskgroup.js:398
:25)
  at Object._onImmediate (c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\node_modules\docpad\node_modules\taskgroup\out\lib\taskgr
oup.js:414:26)
  at processImmediate [as _immediateCallback] (timers.js:345:15)


npm ERR! Test failed.  See above for more details.
npm ERR! not ok code 0

c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\Cakefile:99
      throw err;
            ^
Error: Process exited with error status code
  at ChildProcess.<anonymous> (c:\Users\IBM_ADMIN\Downloads\docpad-plugin-tumblr-master\Cakefile:88:15)
  at ChildProcess.emit (events.js:98:17)
  at maybeClose (child_process.js:756:16)
  at Process.ChildProcess._handle.onexit (child_process.js:823:5)

In my case, I'm getting a somewhat different set of errors (http://stackoverflow.com/questions/26391988/docpad-plugin-odd-errors-when-testing-hangs-when-including-in-project) but it does still have the Error: Didn't place the skeleton as the desired structure already exists one - any idea what's going on here?

@nfriedly
Copy link
Author

I fixed my plugin - the main thing that was getting me was that TaskGroup doesn't ever fire the .once('complete', callback) event - at least not the current version. Changing it to .done(callback) was enough to make my project work.

However when change that in my fork of this and run the tests, it still fails with similar output to above. I'm using the git bash shell on windows 7, so maybe that makes the environment properties behave differently (?)

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

No branches or pull requests

1 participant