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

verbose mode doesn't work - casper is ran as a spawn #11

Closed
pgilad opened this issue Oct 2, 2013 · 1 comment
Closed

verbose mode doesn't work - casper is ran as a spawn #11

pgilad opened this issue Oct 2, 2013 · 1 comment

Comments

@pgilad
Copy link
Contributor

pgilad commented Oct 2, 2013

When running casper through grunt casper with option verbose (and direct) - I see the output being displayed only after casper has finished running.

This is different from the intended outcome, as running casperjs with the same options, I see the logs & progress as it goes, and I don't have to wait for the spec to finish working.

Perhaps this is due to the fact you are creating casper as a spawn?

CasperJs version: 1.1.0-DEV
"grunt-casper": "0.1.3"
Windows 7
Latest GruntJs

@iamchrismiller
Copy link
Owner

Yes, that is in fact the reason why. You have to run Casper through a spawned process because QtWebKit and V8 don't share the same js environment or event loop.

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