Conversation
The CI job on coverage should only run unit tests, not invariant tests, and it does not need many fuzz runs of these tests just to ensure the code is coverged.
|
Coverage after merging coverage-tweaks into main will be
Coverage Report
|
|||||||||||||||||||
wildmolasses
approved these changes
Mar 4, 2025
|
lgtm. the change affects the coverage job only, not the test job, and i cant think of a good reason why we need more iterations on coverage, as i imagine our tests are specific enough to cover all statements/branches (and the weighted foundry dictionary ought to supplement well) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.