-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Enhancement]: fix/re-enable unit test GetVectorFromChunkCache #33210
Labels
Comments
@bigsheeper can you help with item 1 and 2 in the above TODOs? |
this issue is to track item 1, 2 and 4 only. |
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. |
sre-ci-robot
pushed a commit
that referenced
this issue
Sep 28, 2024
issue: #33210 --------- Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
sre-ci-robot
pushed a commit
that referenced
this issue
Oct 8, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
Is there an existing issue for this?
What would you like to be added?
unit test
GetVectorFromChunkCache
intest_sealed.cpp
was skipped due to a potential mem leak inAWS::InitSDK
. I tried to re-enable it wondering if the AWS leak has been fixed, but this test failed due to failing connect to object store. this issue needs to be fixed.Once the object store issue is fixed, we need to re-assess if the AWS mem leak still exist. Currently the entire gtest is suffering from mem leak, see #33139, but ASAN is turned off in CI, so we can enable the tests.
So TODOs are:
GetVectorFromChunkCache
(and several other skipped tests)GetVectorFromChunkCache
againWhy is this needed?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: