milvus icon indicating copy to clipboard operation
milvus copied to clipboard

fix: set conan profile to default

Open XTxxxx opened this issue 6 months ago • 8 comments

Fix https://github.com/milvus-io/milvus/issues/41844

XTxxxx avatar May 14 '25 13:05 XTxxxx

Welcome @XTxxxx! It looks like this is your first PR to milvus-io/milvus 🎉

sre-ci-robot avatar May 14 '25 13:05 sre-ci-robot

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: XTxxxx To complete the pull request process, please assign czs007 after the PR has been reviewed. You can assign the PR to them by writing /assign @czs007 in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

sre-ci-robot avatar May 14 '25 13:05 sre-ci-robot

@XTxxxx 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.

mergify[bot] avatar May 14 '25 13:05 mergify[bot]

@XTxxxx

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.

mergify[bot] avatar May 14 '25 13:05 mergify[bot]

@XTxxxx E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

mergify[bot] avatar May 14 '25 15:05 mergify[bot]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 73.70%. Comparing base (2d0ae3a) to head (f260d3a). Report is 237 commits behind head on master.

:x: Your project status has failed because the head coverage (73.70%) is below the target coverage (77.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           master   #41845       +/-   ##
===========================================
- Coverage   81.64%   73.70%    -7.95%     
===========================================
  Files        1204      335      -869     
  Lines      186101    30637   -155464     
===========================================
- Hits       151949    22582   -129367     
+ Misses      27865     8055    -19810     
+ Partials     6287        0     -6287     
Components Coverage Δ
Client ∅ <ø> (∅)
Core 73.70% <ø> (∅)
Go ∅ <ø> (∅)

see 1539 files with indirect coverage changes

:rocket: New features to boost your workflow:
  • :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

codecov[bot] avatar May 14 '25 15:05 codecov[bot]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

stale[bot] avatar Jun 18 '25 19:06 stale[bot]

@XTxxxx cpu-e2e job failed, comment /run-cpu-e2e can trigger the job again.

mergify[bot] avatar Jun 18 '25 19:06 mergify[bot]