You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've had this happen twice after a clean checkout -- run grunt test and see this:
messaging for mrT1
✓ allows mrT1 to add a note (124ms)
✓ and add a comment on the note (42ms)
✓ and then get the whole thread (55ms)
1) allows mrT1 to get all messages for his team for the last two weeks
✓ allows mrT1 to get just the parent messages for his team (49ms)
...
20 passing (2s)
1 failing
1) platform client messaging for mrT1 allows mrT1 to get all messages for his team for the last two weeks:
Uncaught AssertionError: expected 1 to be at least 2
When you run the test a second time, it works. Is the test reliant on having data around from previous tests? This isn't critical, but should be addressed someday.
The text was updated successfully, but these errors were encountered:
It shouldn't but I will have a quick look.
On May 1, 2014 9:02 AM, "Kent Quirk" [email protected] wrote:
I've had this happen twice -- run grunt test and see this:
messaging for mrT1
✓ allows mrT1 to add a note (124ms)
✓ and add a comment on the note (42ms)
✓ and then get the whole thread (55ms)
1) allows mrT1 to get all messages for his team for the last two weeks
✓ allows mrT1 to get just the parent messages for his team (49ms)
...
20 passing (2s)
1 failing
platform client messaging for mrT1 allows mrT1 to get all messages for his team for the last two weeks:
Uncaught AssertionError: expected 1 to be at least 2
When you run the test a second time, it works. Is the test reliant on
having data around from previous tests? This isn't critical, but should be
addressed someday.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/14
.
I've had this happen twice after a clean checkout -- run grunt test and see this:
When you run the test a second time, it works. Is the test reliant on having data around from previous tests? This isn't critical, but should be addressed someday.
The text was updated successfully, but these errors were encountered: