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

Fix the benchmarks datasets URL format #225

Merged
merged 3 commits into from
Jun 28, 2022
Merged

Fix the benchmarks datasets URL format #225

merged 3 commits into from
Jun 28, 2022

Conversation

Kerollmops
Copy link
Member

@Kerollmops Kerollmops commented Jun 28, 2022

We were using an URL of the form git://github.com/orga/repo.git which is wrong and GitHub broke it recently. I just changed it to make it valid by using the https://github.com/orga/repo.git format.

This PR also changes the version of retain_mut to =0.1.7 to avoid CI-breaking warnings. If you want to understand the reason why I am doing that you can read more in #224.

Copy link
Contributor

@irevoire irevoire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@Kerollmops
Copy link
Member Author

Thank you very much for the review!
bors merge

@bors
Copy link
Contributor

bors bot commented Jun 28, 2022

Build succeeded:

@bors bors bot merged commit b7c0d2d into master Jun 28, 2022
@bors bors bot deleted the fix-benchmarks branch June 28, 2022 11:44
not-jan pushed a commit to not-jan/roaring-rs that referenced this pull request Aug 31, 2022
225: Fix the benchmarks datasets URL format r=Kerollmops a=Kerollmops

We were using an URL of the form _git://github.com/orga/repo.git_ which is wrong and GitHub broke it recently. I just changed it to make it valid by using the https://github.com/orga/repo.git format.

This PR also changes the version of `retain_mut` to _=0.1.7_ to avoid CI-breaking warnings. If you want to understand the reason why I am doing that you can read more in RoaringBitmap#224.

Co-authored-by: Kerollmops <[email protected]>
bors bot added a commit that referenced this pull request Sep 1, 2022
222: Introduce `insert_range` for RoaringTreemap r=Kerollmops a=not-jan

Implemented a somewhat naive version of `insert_range` for RoaringTreemap

~~I wanted to add a separate benchmark to compare the performance of `insert_range` with collecting from an iterator but was unable to do so because `cargo bench` would fail with a connection error every time I ran it.~~
**Edit:** This is fixed now with #225

Co-authored-by: saik0 <[email protected]>
Co-authored-by: not-jan <[email protected]>
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