Filter by reset
- Everywhere
96 - Issues
26 - Pull Requests
20 - Comments
50
Multiple test_prefix and comment_mode
Tests stucks if no next command passed
Implementing a duration and the relative percentage for each command in a test seems like a great idea. We can use our existing block syntax and just overlook it during the test: ––– duration: 0.123ms (10.2%) –––
enhancement
Improve CLT output with user command
It looks like it's possible and might be a good idea to add measurement of 'peak memory' and 'CPU time' usage after each command we run, similar to how we track 'duration'. To make this happen, we could try tracking the PID of the bash process we run and …
enhancementest::size_M
Improve CLT output with user command
Improve CLT output with user command
We should improve our CLI action and provide users with a given command that they can run to validate the test locally. In the same output, we should dump information about the script and real command execution.
Add default delay a few ms between inputs
Possibility to reset mistaken command in record session
It is indeed a great idea to include the option of undoing a mistaken command while we are in recording mode. This can be achieved by implementing a specific key combination that removes the command from the final recorded file. With this feature, we can …
enhancement
Add default delay a few ms between inputs
Checkpointing caching while replay the test
When we run a record file that uses blocks to validate that it works fine, it executes all commands. However, once we add some extra commands or fix the last one, we have to run the whole test again, which wastes significant time in most cases redoing the …
enhancement
Add default delay a few ms between inputs
Add possibility to delay next command to replay
Remove escape sequences from outputs
est::size_S
From: https://gitlab.com/manticoresearch/clt/-/issues/5 While doing a scenario to test mysqldump with combined tasks no mcl, mcl only, mcl id with json, MVA, text fields, we found that it's a good idea to have the possibility to support dynamic variables …
Remove escape sequences from outputs
est::size_S
Add info to README about output MUST contain new line as a limitation
Tests stucks if no next command passed
Add default delay a few ms between inputs
Sometimes, when you replay a CLT test, one input may run too soon after the previous one. It is recommended to add a default delay between inputs, such as 5ms.
Compare only command output and improve diff logic
Reusable blocks in the interactive mode
From: https://gitlab.com/manticoresearch/clt/-/issues/10 We now have support for reusable blocks, but we should also incorporate this feature into interactive mode. The task involves: Contemplating possible implementation methods. As proposed, we could …
Add support of regex patterns through predefined file
Add possibility to pass the directory required to run tests from outside
est::size_S
enhancement
Remove escape sequences from outputs
We should remove all bash sequences from generated output before we write it to the rep file to make it easier and more natural to compare outputs with different IDEs that may not render them or simply do not display them.
est::size_S
bug
Tests stucks if no next command passed
I faced with this behavior in this test It is stuck if: kubectl get deployment my-helm-manticoresearch-balancer -o=jsonpath='{$.spec.template.spec.containers[:1].image}' And like this kubectl get deployment my-helm-manticoresearch-balancer -o=jsonpath …
Infinite loop on empty input/output by cmp tool
bug
There's a problem with the dynamic prompt in the output of the replay file. Any command that includes $VAR or anything with a $ isn't functioning correctly because it's being matched to the prompt. We need to inspect the code and determine how to resolve …
bug
Fix issue with cmp tool when comparing line with empy one
Implement duration calculation and percentage calculation for each ex…
…ecuted command
est::size_S
Fix issue with cmp tool when comparing line with empy one
We have the rare case that while comparing outputs from record and replay it does not return error code
bug
I faced with a job that stuck and ran for more than 4 hours. We need to add some execution time limits
est::size_S