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

Code coverage fails because it takes the wrong commit for master #669

Closed
ZER0 opened this issue Feb 24, 2022 · 0 comments · Fixed by #779
Closed

Code coverage fails because it takes the wrong commit for master #669

ZER0 opened this issue Feb 24, 2022 · 0 comments · Fixed by #779
Assignees
@HDauven @ureeves
Labels
fix:bug Something isn't working

Comments

@ZER0
Copy link
Contributor

ZER0 commented Feb 24, 2022

Describe the bug
Code coverage fails because it takes the wrong commit for master, see: #668

The current master at that point in time was: d8ef790 (just pushed)

But the code coverage reports: 8d01a94
(pushed 20 days ago)

This bug leads to code coverage failures even with small changes, making the code coverage totally unreliable and unpredictable.
To Reproduce
See the description.

Expected behaviour
Code Coverage should take the proper commit.

Logs/Screenshot
N/A

Platform
N/A

Additional context
N/A
@ZER0 ZER0 added the fix:bug Something isn't working label Feb 24, 2022
@HDauven HDauven self-assigned this Oct 17, 2023
@HDauven HDauven mentioned this issue Oct 19, 2023
Merged
@HDauven HDauven linked a pull request Oct 19, 2023 that will close this issue
Update CI jobs #779
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@HDauven HDauven

@ureeves ureeves

Labels
fix:bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update CI jobs dusk-network/plonk
3 participants
@ZER0 @HDauven @ureeves