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

Rockylinux9.3 #51

Closed
wants to merge 5 commits into from
Closed

Rockylinux9.3 #51

wants to merge 5 commits into from

Conversation

yellow-shine
Copy link
Owner

No description provided.

Signed-off-by: Sammy Huang <[email protected]>
Signed-off-by: Sammy Huang <[email protected]>

delete

Signed-off-by: Sammy Huang <[email protected]>

add

Signed-off-by: Sammy Huang <[email protected]>

1

Signed-off-by: Sammy Huang <[email protected]>
Signed-off-by: Sammy Huang <[email protected]>
Copy link

mergify bot commented Feb 18, 2024

@samhuang-z Thanks for your contribution. Please submit with DCO, see the contributing guide https://github.com/milvus-io/milvus/blob/master/CONTRIBUTING.md#developer-certificate-of-origin-dco.

Copy link

mergify bot commented Feb 18, 2024

@samhuang-z

Invalid PR Title Format Detected

Your PR submission does not adhere to our required standards. To ensure clarity and consistency, please meet the following criteria:

  1. Title Format: The PR title must begin with one of these prefixes:
  • feat: for introducing a new feature.
  • fix: for bug fixes.
  • enhance: for improvements to existing functionality.
  • test: for add tests to existing functionality.
  • doc: for modifying documentation.
  • auto: for the pull request from bot.
  1. Description Requirement: The PR must include a non-empty description, detailing the changes and their impact.

Required Title Structure:

[Type]: [Description of the PR]

Where Type is one of feat, fix, enhance, test or doc.

Example:

enhance: improve search performance significantly 

Please review and update your PR to comply with these guidelines.

Copy link

mergify bot commented Feb 18, 2024

@samhuang-z ut workflow job failed, comment rerun ut can trigger the job again.

Signed-off-by: Sammy Huang <[email protected]>
Copy link

mergify bot commented Feb 18, 2024

@samhuang-z ut workflow job failed, comment rerun ut can trigger the job again.

Copy link

codecov bot commented Feb 18, 2024

Codecov Report

Attention: 140 lines in your changes are missing coverage. Please review.

Comparison is base (c91254f) 83.07% compared to head (498a5e7) 80.09%.
Report is 123 commits behind head on master.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #51      +/-   ##
==========================================
- Coverage   83.07%   80.09%   -2.98%     
==========================================
  Files         699      965     +266     
  Lines      112784   137419   +24635     
==========================================
+ Hits        93694   110072   +16378     
- Misses      15505    23629    +8124     
- Partials     3585     3718     +133     
Files Coverage Δ
internal/core/src/index/VectorMemIndex.cpp 41.54% <100.00%> (ø)
internal/datacoord/compaction_trigger.go 84.45% <ø> (-0.64%) ⬇️
internal/datacoord/garbage_collector.go 91.00% <100.00%> (+0.12%) ⬆️
internal/datacoord/meta.go 89.28% <100.00%> (+1.70%) ⬆️
internal/datacoord/segment_allocation_policy.go 91.17% <100.00%> (+0.55%) ⬆️
internal/datacoord/segment_manager.go 88.70% <100.00%> (+0.66%) ⬆️
internal/datanode/channel_checkpoint_updater.go 72.72% <100.00%> (ø)
internal/datanode/flow_graph_time_tick_node.go 72.72% <100.00%> (ø)
internal/datanode/importv2/util.go 63.33% <100.00%> (ø)
internal/datanode/io/binlog_io.go 92.68% <100.00%> (+3.79%) ⬆️
... and 32 more

... and 357 files with indirect coverage changes

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

Successfully merging this pull request may close these issues.

1 participant