koordinator
koordinator copied to clipboard
WIP: init prediction manager framework
Ⅰ. Describe what this PR does
Ⅱ. Does this pull request fix one issue?
Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist
- [ ] I have written necessary docs and comments
- [ ] I have added necessary unit tests and integration tests
- [ ] All checks passed in
make test
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 67.53%. Comparing base (
cd58ac6
) to head (9c119fc
). Report is 21 commits behind head on main.
:exclamation: Current head 9c119fc differs from pull request most recent head 1b30e5a. Consider uploading reports for the commit 1b30e5a to get more accurate results
Additional details and impacted files
@@ Coverage Diff @@
## main #1889 +/- ##
==========================================
- Coverage 67.56% 67.53% -0.03%
==========================================
Files 420 420
Lines 47059 47059
==========================================
- Hits 31795 31782 -13
- Misses 12955 12964 +9
- Partials 2309 2313 +4
Flag | Coverage Δ | |
---|---|---|
unittests | 67.53% <ø> (-0.03%) |
:arrow_down: |
Flags with carried forward coverage won't be shown. Click here to find out more.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please ask for approval from zwzhang0107 and additionally assign eahydra, fillzpp after the PR has been reviewed.
You can assign the PR to them by writing /assign @eahydra @fillzpp
in a comment when ready.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment
This issue has been automatically marked as stale because it has not had recent activity. This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/stale
is applied - After 30d of inactivity since
lifecycle/stale
was applied, the issue is closed You can: - Mark this issue or PR as fresh with
/remove-lifecycle stale
- Close this issue or PR with
/close
Thank you for your contributions.
This issue has been automatically closed because it has not had recent activity. This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/stale
is applied - After 30d of inactivity since
lifecycle/stale
was applied, the issue is closed You can: - Reopen this PR with
/reopen
Thank you for your contributions.