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

ci: add steps to report valgrind memory results #269

Merged
merged 1 commit into from
May 29, 2024

Conversation

msclock
Copy link
Collaborator

@msclock msclock commented May 29, 2024

No description provided.

Signed-off-by: msclock <msclock@qq.com>
Copy link

codecov bot commented May 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (674b9fa) to head (da562ce).

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #269   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            5         5           
  Lines           21        21           
=========================================
  Hits            21        21           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@msclock msclock requested a review from huxuan May 29, 2024 08:04
@msclock msclock enabled auto-merge (squash) May 29, 2024 08:05
@msclock msclock merged commit 822b394 into serious-scaffold:master May 29, 2024
34 checks passed
@msclock msclock deleted the report_valgrind branch May 29, 2024 09:59
@serious-scaffold
Copy link
Contributor

🎉 This PR is included in version 1.4.48 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants