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

Some tests are failing #1

Open
ghost opened this issue Apr 18, 2010 · 3 comments
Open

Some tests are failing #1

ghost opened this issue Apr 18, 2010 · 3 comments

Comments

@ghost
Copy link

ghost commented Apr 18, 2010

I use 64-bit Arch Linux and Chromium 5.0.342.9 (43360).

Modules/1.0 – all failed
Modules/1.1.1 – all failed
Modules/1.1.1 Wrapped – 9 passed, 3 failed
Async/A – all failed
determineShallowDependencies() – all failed

The error that I see most often is “Died on test #1: NETWORK_ERR: XMLHttpRequest Exception 101.”, but there’s also stuff like “FAIL module.uri is absolute and ends with program.js”.

@jbrantly
Copy link
Owner

Thanks! I'll take a look into it when I can.

@jbrantly
Copy link
Owner

Sorry for the delay. I had someone else try the tests (I didn't have Chromium handy) and they passed. The error sounds like a cross-domain issue perhaps, or something similar. If you visit the page at http://jbrantly.github.com/yabble/test/modules1.0/index.html do the tests still fail?

@akidee
Copy link

akidee commented May 10, 2011

I have the same problem - test cases fail or are not listed at all. To test offline, I have written a small node.js server:

var connect = require('connect')

dir = process.argv[2]

connect(
    connect.static(dir)
).listen(3000)

I tested on Mac OS 10.6 with Google Chrome 12 and Firefox 4.0.

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

2 participants