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
Contradiction between tests results and browserscope #127
Comments
Why do you close an issue without giving any reason? |
|
You didn't read my first report, did you ? |
Ah sorry, I'm trying to close old stale issues we have no interest in addressing. We chose the lower limit because its better to side on the lowest possible value as the true value can be anywhere in between. This way we don't artificially inflate browserscope results with outliers. |
I don't think 2 month is old but at least you give a frank reason. |
Browserscope has no concept of margin of error, it only sees a reported number, so we handle that for it. Margin of error and other stats are calculated in this snippet of code. |
Ok you're not answering the first part of my question. The snippet of code looks like bullshit. |
Yap ;) |
Hi,
Thanks for creating jsperf :)
It is somewhat surprising to create a revision, run tests once and see differences between the values in the last column and the values in browserscope.
While the answer is here :
http://jsperf.com/faq#browserscope
it should definitely be mentionned (at least a link to http://jsperf.com/faq#browserscope with a warning) between the test runner section and the browserscope section because :
It could be interesting to have an advanced FAQ which gives possible explanations why some tests have bigger error margin than others.
Best regards,
Laurent Lyaudet
The text was updated successfully, but these errors were encountered: