search

busterjs / buster

Abandoned - A powerful suite of automated test tools for JavaScript.
http://docs.busterjs.org
Other
448 stars 37 forks source link

ramp: Cannot add non-existent resource /____ramp_internals-...uuid here....js to load path #375

Closed augustl closed 10 years ago

augustl commented 10 years ago

In some cases, you'll get the following error when running "buster test":

-c/--config: Cannot add non-existent resource /____ramp_internals-edf83560-b0db-4ec4-8c16-e3108750e9f4.js to load path

The UUID is different for each run.

Have not yet been able to reproduce this issue.

guidokessels commented 10 years ago

I have this error consistently for every testrun after updating Buster to 0.7.3.

Downgrading back to 0.6.11 (which I was using before) removes the error for me.

Let me know if I can help with any info you need to reproduce this.

augustl commented 10 years ago

I haven't been able to reproduce this at all, so anything you can tell me about your setup would be nice!

I also have a suspicion of what the problem might be, so if you don't mind getting set up with a buster dev environment to test it from git master, that would have been great, in case I'm not able to reproduce it on my setup.

rundis commented 10 years ago

Same problem here. Works fine on my mac, but not on centos at work. I will try and see if I can reproduce on a virtual/vagrant box. Hopefully during the weekend.

augustl commented 10 years ago

This may or may not have been fixed in master. Haven't reproduced it yet, but I've removed a possible race condition.

Try to run from master, or wait for a new release which will probably come soon (just want to run it through Chris first).

augustl commented 10 years ago

Relevant commits:

https://github.com/busterjs/ramp-resources/commit/80ba723badb848c3a1c4b8e8d5ff5ef8ac047563 https://github.com/busterjs/ramp/compare/bcd32bf557...a54b177305

rundis commented 10 years ago

Managed to reproduce error. Check out : https://github.com/rundis/buster-ramp-error

augustl commented 10 years ago

@rundis: Thanks a lot for reproducing the error! A VM provisioned with ansible has got to be the ultimate way to reproduce errors.

The error has now been fixed in ramp 1.0.3. Use npm to reinstall buster completely to ge the latest version of all dependencies.

The root of the error is async behaviour caused by return when(theResourceSet) in ramp-resources. Wrapping in when will force it do be async, but for some reason it was only actually async in some cases, such as in your vagrant setup, but not on my arch linux setup, and apparently not on any other of the "core" buster peeps setups either.

This was fixed in the commits I mentioned before, now verified by @rundis' VM.

rundis commented 10 years ago

tx. Works like a charm !