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.

Sign up for GitHub

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

Jump to bottom

add tests to Allocator #373

Merged
merged 1 commit into from
Feb 6, 2024
Merged

add tests to Allocator #373

merged 1 commit into from
Feb 6, 2024

Conversation

arvidn
Copy link
Contributor

@arvidn arvidn commented Feb 5, 2024 •
edited

bring test coverage of Allocator.rs from 94.09% to 98.53%

https://coveralls.io/jobs/135722648

@coveralls-official Coveralls Official
Copy link

coveralls-official bot commented Feb 5, 2024 •
edited

Pull Request Test Coverage Report for Build 7791213784

  • 0 of 193 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.5%) to 94.148%
Totals Coverage Status
Change from base Build 7773181525: 0.5%
Covered Lines: 5390
Relevant Lines: 5725
💛 - Coveralls

@arvidn arvidn marked this pull request as ready for review February 5, 2024 22:35
@arvidn arvidn requested a review from Rigidity February 5, 2024 22:35
Rigidity
Rigidity approved these changes Feb 5, 2024
View reviewed changes
Copy link
Contributor

@Rigidity Rigidity left a comment

Choose a reason for hiding this comment

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

lgtm

@arvidn arvidn merged commit 646beb7 into main Feb 6, 2024
27 checks passed
@arvidn arvidn deleted the allocator-tests branch February 6, 2024 00:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Rigidity Rigidity Rigidity approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@arvidn @Rigidity