-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Problem running benchmarks #1756
Comments
As you found in #1755 the benchmarks have been broken for over a year… I never actually run them. Perhaps we should get rid of them. @avajs/core? |
I think the benchmark could be useful if we have performance-related commits or PRs. I would prefer to just fix them. |
👍 to @sindresorhus |
I'd love to work on this if it's still an open issue. |
@OTR500miles2go thanks for your interest! I don't mind it being fixed but it feels like wasted effort. It's 14 months since this issue was raised and I've still never tried to run benchmarks. |
Yeah, let's just remove them. |
May I contribute by submitting a PR to:
|
Sounds great @OTR500miles2go! |
As Per The
maintaining.md
, I ran$ node bench/run && node bench/compare
But, the result was
The text was updated successfully, but these errors were encountered: