Repository navigation
docs: the benchmark tooling moved to mmdbbench; the engine tag of a JVM wheel for an A/B - #403
Merged
Merged
Conversation
…VM wheel for an A/B (#402) A JVM wheel built from a dispatch without arcadedb-tag takes the jars of the latest image, so it carries another engine than the release it is compared with. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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.
Closes #402
The README says that the benchmark tooling moved to humemai/mmdbbench instead of staying in the old repository. The CI page gets the dispatch command for a JVM wheel that must carry the engine of a release (
-f arcadedb-tag=26.11.1), with the reason.uvx pre-commit run --fileson both files passes. The page is documentation only, so no test changes.🤖 Generated with Claude Code