Skip to content
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

Closed
ghost opened this issue Mar 31, 2018 · 8 comments
Closed

Problem running benchmarks #1756

ghost opened this issue Mar 31, 2018 · 8 comments
Labels
bug current functionality does not work as desired help wanted low priority question scope:tooling

Comments

@ghost
Copy link

ghost commented Mar 31, 2018

As Per The maintaining.md, I ran

$ node bench/run && node bench/compare

But, the result was

fs.js:928
  return binding.readdir(pathModule.toNamespacedPath(path), options.encoding);
                 ^

Error: ENOENT: no such file or directory, scandir 'E:\Workspace\ava\bench\.results'
    at Object.fs.readdirSync (fs.js:928:18)
    at Object.<anonymous> (E:\Workspace\ava\bench\compare.js:7:16)
    at Module._compile (module.js:649:30)
    at Object.Module._extensions..js (module.js:660:10)
    at Module.load (module.js:561:32)
    at tryModuleLoad (module.js:501:12)
    at Function.Module._load (module.js:493:3)
    at Function.Module.runMain (module.js:690:10)
    at startup (bootstrap_node.js:194:16)
    at bootstrap_node.js:666:3
@sindresorhus sindresorhus changed the title Problem Running Benchmarks Problem running benchmarks Mar 31, 2018
@novemberborn
Copy link
Member

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?

@novemberborn novemberborn added bug current functionality does not work as desired help wanted question low priority scope:tooling labels Apr 1, 2018
@sindresorhus
Copy link
Member

I think the benchmark could be useful if we have performance-related commits or PRs. I would prefer to just fix them.

@ghost
Copy link
Author

ghost commented Apr 2, 2018

👍 to @sindresorhus

novemberborn added a commit that referenced this issue Apr 2, 2018
Ignore `cli-spinners` and `inquirer`, since #1722 removes them.

Ignore `git-branch`, since the benchmark utils are currently broken
(#1756).

Ignore `globby` as it has significant breaking changes.
novemberborn added a commit that referenced this issue Apr 2, 2018
Ignore `cli-spinners` and `inquirer`, since #1722 removes them.

Ignore `git-branch`, since the benchmark utils are currently broken
(#1756).

Ignore `globby` as it has significant breaking changes.
@OTR500miles2go
Copy link

I'd love to work on this if it's still an open issue.

@novemberborn
Copy link
Member

@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.

@sindresorhus?

@sindresorhus
Copy link
Member

Yeah, let's just remove them.

@OTR500miles2go
Copy link

May I contribute by submitting a PR to:

  • remove /bench
  • update maintaining.md, remove the benchmark section
  • update .gitignore, remove the bench/.results entry

@novemberborn
Copy link
Member

Sounds great @OTR500miles2go!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug current functionality does not work as desired help wanted low priority question scope:tooling
Projects
None yet
Development

No branches or pull requests

3 participants