Repository navigation
ci: снять порог времени для длинных фрагментов в snippet_benchmark - #46
Merged
Merged
Conversation
Длинные фрагменты по-прежнему проверяются на результат (std485 в ответе), время сравнивается только у короткого фрагмента с базовой ревизией.
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
1 participant
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.
Порог времени для фрагментов 4 000 и 32 000 символов срывал CI на долях миллисекунды на раннерах GitHub, хотя поиск не менялся. По решению владельца он снят: длинные фрагменты проверяются только на результат (std485 в ответе), время сравнивается лишь у короткого фрагмента с базовой ревизией.
Локально: snippet_benchmark проходит, tests.test_mcp_publication — OK.
Нужен для выкладки калиброванного поиска (IngvarConsulting/unica#1419).