-
Notifications
You must be signed in to change notification settings - Fork 66
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
timeout error when running benchmarks #71
Comments
Thanks a ton!!!!!! ❤️ This is great, really keep it up even with little things. Otherwise I'd never know. These issues are super valuable as a maintainer, which is why I always wonder why not more people open a bunch of bugs in OSS projects because there's definitely a tone of them. This is a new usage of Will set it to infinity as well. :) Also while not grave, certainly annoying. I might cut a new release sooner than I originally planned to :D |
Fixed on master, although I'm not sure you wanna use master yet as it breaks the other formatters (HTML etc.) right now as one main key was renamed - shouldn't be too long though ;P |
Awesome - happy to help! Yeah, I was benchmarking some pretty fast stuff. Here was the second successful run for your reference:
Thanks again for the awesome library! I look forward to helping more in a week or so once I get my open source time back 😄 |
Cool stuff! But damn that standard deviation... Wish I had implemented #50 again so the console formatter could show min/max and sample size. Or the nth percentile thing. So much to do :D Your talk is next week, right? Good luck + much success! If you do more complex stuff in the benchmarking functions, #70 might be interesting to you. If you try it out, the difference would be interesting for me to see :) |
Guten Tag!
It's probably not a big deal, but I was running some benchmarks just now, and on one run I got the following timeout error from
Task.await
.I ran the same task again right after and it worked just fine, so it's a transient issue. I figured I'd file the error just so you were aware, but clearly it's not really that much of an issue since it fixes itself. However, if there's anything else I can do to help shed some light on this, then let me know and I'll send along whatever I can!
The text was updated successfully, but these errors were encountered: