WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Conversation

@dominictarr
Copy link
Collaborator

found missing } which was preventing web-runner from compiling.

logging in stdio breaks it...

beginning to rewrite runFile to use some other means of communication.

moved message functions into async_testing/lib/messages.js
found a couple of problems with child,

tests that logged stuff was breaking reporting,
and you could make false positives by outputting a finish message (indicating 0 tests, which is success(!))

started working on another child process implementation, using http.

but realised that the messages must be queued, so that they arrive in order.
@deepthawtz
Copy link

/usr/local/lib/node/.npm/async_testing/9999.0.0-LINK-25de0aad/package/lib/web-runner.js:343
});

@dbrock
Copy link

dbrock commented Jan 3, 2011

You should really fix this immediately. It prevents the whole package from even loading.

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

Successfully merging this pull request may close these issues.

5 participants