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 think I found the issue, one of the tests is using jasmine.clock().mocktime(time) and that seems to be screwing up how Karma reports the duration for the test. Since the mocked time is far enough in the past I'm guessing that the signed integer is getting flipped and going way negative.
The text was updated successfully, but these errors were encountered:
Originally reported to the Karma project.
Expected behaviour
Running karma tests takes ~12 seconds, expect test duration (runtime) to be ~12 seconds.
Actual behaviour
PhantomJS 2.1.1 (Windows 7 0.0.0): Executed 316 of 316 SUCCESS (1.959 secs / -41118 mins 50.274 secs)
TOTAL: 316 SUCCESS
Environment Details
Angular Yeoman Project.
Windows 7
karma --version
): 1.3.0karma.config.js
fileSteps to reproduce the behaviour
grunt test
I think I found the issue, one of the tests is using
jasmine.clock().mocktime(time)
and that seems to be screwing up how Karma reports the duration for the test. Since the mocked time is far enough in the past I'm guessing that the signed integer is getting flipped and going way negative.The text was updated successfully, but these errors were encountered: