Filter by reset
- Everywhere
143 - Issues
38 - Pull Requests
36 - Comments
69
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
Nightly CI Pipeline Timeout in test-migration-es-ms.rec (No .rep File for Debugging)
Description Nightly CI pipeline running the test-migration-es-ms.rec test in the Nightly tests of mysqldump and elasticdump job started to crash on April 9, 2025 due to execution time overrun (timeout after 5-6 hours). Normally the job would run for 8-9 …
bug
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.
We should look into all changes made and actualize readme to make it follow what we currently have.
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
Skip adding succeed tests to summary
We should add to summary only those tests that failed same we do in comments
Description: HTTP requests sent through Buddy without ; echo at the end cause the request to hang indefinitely, and the test does not complete. The query works correctly when executed via MySQL CLI (mysql -h0 -P9306 -e "show version;"). The issue occurs …
bug
CLT improvements and bug fixes
We should add some improvements to CLT and investigate bugs Currently we cannot see OK in outputs by default, looks like at some point in time it stopped working We should add possibility to disable single line matching as requested by @PavelShilin89
Let's add support for ---comment--- totally ignored by CLT when replaying the test. It will make it much easier to understand what the author means when testing something.
Make CLT to run from global PATH
Currently when we add path to CLT in PATH we are still unable to use it due to failed to find required files to run in specified path
Issue with wrong rec generated in manual mode
We have issue with recording in manual mode as follows: ./clt record -t test.rec load ––– input ––– echo 1 > /dev/null ––– output ––– - clt> ––– input ––– sleep 1 ––– output –––
Refactor: Deprecate PTY and use fork
Currently, we use PTY to read low-level data and try to understand if commands have finished or not due to the original idea of supporting interactive mode. We are moving forward and probably will not need it. To make the tool simpler and more error-proof …
Currently, we check the output of each command with strict matching and regular expressions, which means all output needs to match exactly for each command. The idea is to introduce custom checkers/validators that can be represented as linked aliases or …
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.
In some cases it makes sense to provide multiple entries in test_prefix in the CLT action. Let's add support of arrays in test_prefix .…
bug
In CLT we don't have ability to select desired editor
est::size_S
I faced with a job that stuck and ran for more than 4 hours. We need to add some execution time limits
Visualize CLT test results in PRs
Currently if a CLT test fails it's not visible in the PR, e.g.: Let's improve the action, so we put test results right to the PR for better visibility and faster decision making.
est::size_M
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