-
Notifications
You must be signed in to change notification settings - Fork 197
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
subsequent tasks in multi task don't run their specs #299
Comments
Do you want to try to await the resolve call and see if that changes anything? |
This project uses a large multi task and it runs all of the specs. So i'm not sure what is the difference. |
I'm running into this issue as well after upgrading from version 1.2.0 to 2.0.3. Is this still being looked at? |
Not that I know of. |
@nealdeters I’d you signed the cla and reimplemented pr 300 it might fix your issue? |
@steveoh I ended up using that as the fix. Thanks for getting back to me. |
@nealdeters do you want to contribute the fix? |
Hi @jabbany @steveoh as per your suggestion in #311 I have tried to incoperate the changes mentioned in PR #300, But it is not working for me. I am using grunt-contrib-jasmine latest version in less.js and after running few test cases test cases are hanging, Please find the logs:
Could you please have a look and provide your feedback on the issue? |
I'm working on updating less.js to use 2.0.3 and have discovered some strange behavior. This happens in 2.0.2 and 2.0.3 but not 2.0.1
When calling a multi task, only the first task will actually run it's specs, and then it will either hang or continue to run the other tasks without actually running any specs.
I've written a small test case that shows the case when it doesn't run subsequent specs.
package.json
Gruntfile.js
test.js
test_2.js (with failing spec)
running
grunt --verbose
produces this outputas you can see the first task completes no problem but then the second task goes straight from
Jasmine Runner Starting...
to>> 0 failures
even though the spec should fail.As far as I can tell this is related to the issue I was having trying to update less.js to use the latest version,
and it might have something to do with tasks/jasmine.js:30 and how it is called on tasks/jasmine.js:372. I'm not very familiar with this project so that's as far as I've got.
The text was updated successfully, but these errors were encountered: