Skip to content

[dummy test] ci: test Codecov integration with dummy coverage#1493

Closed
jamesgao-jpg wants to merge 7 commits intomainfrom
ci/codecov-dummy-test
Closed

[dummy test] ci: test Codecov integration with dummy coverage#1493
jamesgao-jpg wants to merge 7 commits intomainfrom
ci/codecov-dummy-test

Conversation

@jamesgao-jpg
Copy link
Collaborator

Summary

  • Skip real build/test in the ut workflow and create a minimal dummy coverage.info in LCOV format
  • Tests whether Codecov upload and PR bot comments work correctly before investing in full CI runs

This is a throwaway PR to validate the Codecov setup from PR #1492.

Test plan

  • Verify Codecov bot posts a coverage comment on this PR
  • Confirm coverage data appears on codecov.io for the knowhere repo
  • Close this PR once validated

foxspy and others added 7 commits March 10, 2026 07:44
- Add test_helpers.h: IndexTestHelper template class for reducing repetitive Build/Search code
- Add test_config_generators.h: Centralized ConfigGenerator class for all index configurations
- Add test_flat.cc: Dedicated Flat index tests (build, search, bitset, range search, serialization)
- Add test_distance_unit.cc: Unit tests for distance computation (L2, IP, L1, Linf)
- Add test_distance_datatypes.cc: Multi-datatype distance tests (fp16, bf16, int8)
- Add test_utility_components.cc: BlockingQueue and BitsetView unit tests

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Signed-off-by: xianliang.li <xianliang.li@zilliz.com>
- Merge test_distance_unit.cc into test_distances.cc
- Merge test_distance_datatypes.cc into test_simd.cc
- Add sparse_utils unit tests (SparseRow, MaxMinHeap, GrowableVectorView, DocIdFilterByVector)
- Add HNSW edge case tests (empty graph, heavy filtering, iterator)
- Enable coverage reporting in CI workflow (with_coverage=True)
- Add codecov.yml configuration (70% global, 80% patch targets)
- Add scripts/run_incremental_coverage.sh for local coverage analysis

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Signed-off-by: xianliang.li <xianliang.li@zilliz.com>
Coverage report generation is handled inline in ut.yaml workflow.
The run_codecov.sh script redundantly re-runs tests and is not
referenced by any CI pipeline.

Signed-off-by: jamesgao-jpg <james.gao@zilliz.com>
Signed-off-by: jamesgao-jpg <james.gao@zilliz.com>
Signed-off-by: jamesgao-jpg <james.gao@zilliz.com>
…ces.cc

Signed-off-by: jamesgao-jpg <james.gao@zilliz.com>
Skip real build/test and create a minimal LCOV file to validate
that Codecov upload and PR comments work correctly.

Signed-off-by: jamesgao-jpg <james.gao@zilliz.com>
@sre-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details 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

@jamesgao-jpg jamesgao-jpg changed the title ci: test Codecov integration with dummy coverage [dummy test] ci: test Codecov integration with dummy coverage Mar 10, 2026
@mergify mergify bot added the dco-passed label Mar 10, 2026
@mergify
Copy link

mergify bot commented Mar 10, 2026

@jamesgao-jpg 🔍 Important: PR Classification Needed!

For efficient project management and a seamless review process, it's essential to classify your PR correctly. Here's how:

  1. If you're fixing a bug, label it as kind/bug.
  2. For small tweaks (less than 20 lines without altering any functionality), please use kind/improvement.
  3. Significant changes that don't modify existing functionalities should be tagged as kind/enhancement.
  4. Adjusting APIs or changing functionality? Go with kind/feature.

For any PR outside the kind/improvement category, ensure you link to the associated issue using the format: “issue: #”.

Thanks for your efforts and contribution to the community!.

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.

3 participants