Repository navigation
client-suite.sh runs the tests of the client 2.18.1, and linux-tests.sh builds in memory - #16
Merged
Merged
Conversation
…8.1, from a clone for each tag The suite ran the tests of ChromaDotNet.Client 2.14.0; it now runs those of 2.18.1, the last release. On Windows 2176 pass against ChromaDB and 2173 against VecturaDB, which does not run the three tests that expect a server without the Search API, the sparse vectors and the fork: they did not change in 2.18.1. The clone goes into artifacts/client-<tag>. With a single artifacts/client, the clone of the tag before stayed, and another CLIENT_TAG ran the same tests. The log says the tag of the tests.
…, not in the disk of Docker The copy of the repository where the tests build was in the container, in the disk of Docker, and took all of artifacts but the cache of NuGet, with the outputs of the other scripts. It is now in a tmpfs of 4 GB, and of artifacts it takes only the packages and the clones of the client. The .NET SDK and the packages of NuGet stay in their volumes. In folders of D: mounted in the container, which reads them through the file sharing of Docker, the build of the clone of the client, as the seconds of the suite less the duration of its tests, and the first start of Chroma were slower. On ubuntu:24.04 x64, with the copy in memory and little load on the machine, they took: - SDK and packages in folders of D:: 26 s and 403 ms - SDK and packages in memory too: 7 s and 136 ms - SDK and packages in the volumes: 8 s and 104 ms CLIENT_TAG goes into the container, for build/client-suite.sh to run the clone of the same tag.
ambergrove
approved these changes
Oct 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tests run: