## What\n- Make master Mergify build-ut-cov gate success depend only on
ci-v2/build-ut-cov.\n- Make master Mergify build-ut-cov gate failure
remove ci-passed when ci-v2/build-ut-cov fails, without requiring legacy
split CI failures.\n\n## Why\nWhen legacy split CI jobs are downlined on
master, those checks can be missing instead of failed. The previous
remove rule required both build-ut-cov failure and legacy failure, so
ci-passed could remain after build-ut-cov failed.\n\n## Validation\n-
python3 -c "import yaml;
yaml.safe_load(open('/Users/zilliz/workspace/milvus/zhikunyao_milvus_ci/.github/mergify.yml'));
print('yaml ok')"\n- git diff --check
Signed-off-by: Zhikun Yao <zhikun.yao@zilliz.com>
This PR disables automatic pull_request triggers for Mac Code Checker
and separates non-PR concurrency by branch or SHA so master commits are
not displaced while pending. Test: git diff --check.
---------
Signed-off-by: Zhikun Yao <zhikun.yao@zilliz.com>
This PR removes Code Checker MacOS from the Mergify ci-passed gate.
The macOS checker will no longer be required for ci-passed, and macOS
checker failures will no longer remove ci-passed. It can still run
separately or on demand.
Signed-off-by: Zhikun Yao <zhikun.yao@zilliz.com>
## Summary
Add `scripts/milvus-debug.sh` to automate GDB coredump analysis using
the `-debug` image that accompanies each Milvus release starting from
v2.6.14.
## Background
Starting with v2.6.14, each Milvus release publishes two image variants:
| Tag | Content | Size | Use |
|-----|---------|------|-----|
| `milvusdb/milvus:<tag>` | **stripped** (production) | ~1/3 |
Production deployment |
| `milvusdb/milvus:<tag>-debug` | unstripped (full symbols) | full | GDB
coredump analysis |
The stripped production image is **byte-identical** to the debug image
in its code sections (`strip --strip-debug` removes only `.debug_*`
sections and symbol tables). So GDB can use the debug image's symbols to
resolve addresses in a coredump produced by the stripped image.
## What the script does
1. Pulls the debug image
2. Mounts the coredump file read-only into a container
3. Installs `gdb` on demand (not present in the runtime image by
default)
4. Launches GDB with `solib-search-path=/milvus/lib` so symbols from all
shared libraries (`libknowhere.so`, `libtantivy-binding.so`, etc.)
resolve correctly
5. Auto-prints the initial backtrace
## Typical usage after a production crash
```bash
# 1. Copy the coredump out of the crashed pod
kubectl cp <ns>/<pod>:/tmp/cores/core.<pid> ./core.<pid>
# 2. Run this script (GDB starts automatically with backtrace)
./scripts/milvus-debug.sh ./core.<pid> \
milvusdb/milvus:v2.6.14 milvusdb/milvus:v2.6.14-debug
```
## Test plan
- [x] `bash -n scripts/milvus-debug.sh` (syntax check passes)
- [x] Mirrors the documented procedure in the
strip-image-coredump-debug-guide Feishu doc
- [ ] Manual validation on a real coredump (waiting for v2.6.14
production crash; can be exercised with any coredump for now)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Signed-off-by: Zhikun Yao <zhikun.yao@zilliz.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
## Summary
- Use `boost::system::error_code` overload of `remove_all()` in
`ChunkManagerWrapper` destructor to prevent SIGABRT crash
- Fix applied to all 3 copies: `storage_test_utils.h`,
`InvertedIndexTest.cpp`, `JsonFlatIndexTest.cpp`
## Problem
When running C++ unit tests in parallel shards,
`ChunkManagerWrapper::~ChunkManagerWrapper()` can crash with:
```
boost::filesystem::remove: Directory not empty [system:39]: "4000_4000_3_100"
*** Signal 6 (SIGABRT)
```
This is a TOCTOU race condition in test teardown, same pattern as
#48368.
## Fix
Use the `error_code` overload: `boost::filesystem::remove_all(path, ec)`
which silently ignores errors instead of throwing in destructors.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Signed-off-by: Zhikun Yao <zhikun.yao@zilliz.com>
## Summary
Revert `ci(mergify): upgrade configuration to current format (#46385)`
which removed the `misc:` section and broke mergify rule evaluation —
all PRs stuck on "Your rules are under evaluation".
Restore the `misc:` section with YAML anchors (the working format) and
include 3.0 branch CI rules.
**Root cause**: The format upgrade removed `misc:` and inlined anchors
into `pull_request_rules:`. This caused mergify to get stuck evaluating
rules indefinitely.
## Test plan
- [ ] After merge, verify mergify processes PRs again (ci-passed labels
appear)
- [ ] Verify 3.0 branch PRs get ci-passed with 4 checkers
Signed-off-by: Zhikun Yao <zhikun.yao@zilliz.com>
Add parallel execution capability for C++ unit tests using GTest
sharding, enabling faster CI feedback while maintaining test isolation.
Changes:
- Add run_cpp_ut.sh: New script for parallel UT execution without
coverage
- Update run_cpp_codecov.sh: Add optional parallel support (disabled by
default)
- Add GetTestTempBasePath/GetTestTempPath helpers for shard-specific
temp paths
- Initialize ArrowFileSystemSingleton in test global setup
- Fix flaky ThreadLocalGEOSContextTest with synchronization barrier
- Update test files to use dynamic temp paths instead of hardcoded /tmp/
The coverage script (run_cpp_codecov.sh) defaults to sequential mode for
accurate coverage data. The new run_cpp_ut.sh script defaults to
parallel mode (3 shards) for fast CI feedback.
Signed-off-by: Zhikun Yao <zhikun.yao@zilliz.com>
Update DATE_VERSION, LATEST_DATE_VERSION, GPU_DATE_VERSION, and
LATEST_GPU_DATE_VERSION to use the latest builder image version.
Signed-off-by: Zhikun Yao <zhikun.yao@zilliz.com>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
Replace `apt-get upgrade -y gpgv` with proper installation command. The
upgrade command syntax was incorrect and caused build failures with exit
code 100.
---------
Signed-off-by: Zhikun Yao <zhikun.yao@zilliz.com>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
