-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Normalize Mocha tests to have realistic timings #3539
Conversation
Haven't reviewed the rest, but definitely revert 6b93c95. Changes to test specifications do not require any changes to "package.json". |
6b93c95
to
829e8b3
Compare
@plroebuck done. |
Could you explain the process you used to come up with your slow threshold values? |
I ran tests for 3,4 times and added (~3 * average value of duration it took) If a test takes 100ms
e.g All of Also, if it's a semver-patch, then we need to update package.json with version bump. |
Were the tests run on AppVeyor?
|
@plroebuck no. I ran them locally. Got it 👍 |
Yeah, local timings won't be as much help. Need to run against the 80386 machines Appveyor seems to be powered by... :) You could use timings from our existing commits. Try to get some spread between when you collect results -- certain times of day are much worse than others. |
BTW, you are using the actual formula, right? |
this also resolves #2483... lots of dupes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks! just noticed one issue with the code.
I haven't had a chance to cross-reference the values and the real-world perf though
test/integration/suite.spec.js
Outdated
@@ -4,49 +4,53 @@ var assert = require('assert'); | |||
var run = require('./helpers').runMocha; | |||
var args = []; | |||
|
|||
describe('suite w/no callback', function() { | |||
describe('suit', function() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo
#2483 already closed. |
@plroebuck ok. I'll cross check with previous builds and will update values where needed. @boneskull good catch. Will push updates by this weekend. 👍 |
@WaleedAshraf any movement on this? |
Hi @craigtaub, Sorry for leaving it here for long. |
a6ebb9f
to
829e8b3
Compare
@here, I think it's not needed now. |
Have you checked on AppVeyor? To quote issue.
|
@craigtaub I did, but it's not that clear because logs are not colored and it's difficult to identify slow (red) tests. |
Ah yes, they don't support colours so that won't be possible. Think you can tell its slow if over default slow value (for integrations believe 3750ms). |
Hi, I checked the lastest build on AppVeyor and there is only one test which hits the limit of 3750ms
But this is way too over the limit. Rest of tests are under the limit. |
I agreed to close this issue. Any thoughts? |
Description of the Change
Add
.slow()
to tests which are normally taking longer time.Benefits
More clear view of actual slow tests.
Possible Drawbacks
Should keep an eye on these test for later -- if they are getting even slower, then something's 🐟 !
Applicable issues
Fixes #2597
semver-patch
See also #2837