Skip to content

Remove benchmark submodules #217

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

Conversation

zaneduffield
Copy link
Collaborator

Registering the benchmark corpuses as submodules is convenient, but has drawbacks as well.

  1. depending on how people clone the repo, they may drag in a bunch of irrelevant stuff
  2. it kind of looks like we are 'using' the code from these repos, but we aren't
  3. cargo install --git will clone all submodules, slowing down an install using this method

This change makes the benchmark code clone the repo manually to a gitignored folder.

See

Registering the benchmark corpuses as submodules is convenient, but has
drawbacks as well.
1. depending on how people clone the repo, they may drag in a bunch of
   irrelevant stuff
2. it kind of looks like we are 'using' the code from these repos, but
   we aren't
3. `cargo install --git` will clone all submodules, slowing down an
   install using this method

This change makes the benchmark code clone the repo manually to a
gitignored folder.

See
- rust-lang/cargo#4247
@zaneduffield zaneduffield requested a review from jgardn3r March 20, 2025 06:22
Copy link

codecov bot commented Mar 20, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

@zaneduffield zaneduffield merged commit d47aaa6 into integrated-application-development:master Mar 21, 2025
7 checks passed
@zaneduffield zaneduffield deleted the remove-submodules branch March 21, 2025 00:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants