Do not leave any queries after test finish (and add a check into clickhouse-test)#34924
Conversation
c19a714 to
ea6ed46
Compare
|
Any clue on why CI did not started any checks? |
|
f7330a5 to
4cef19f
Compare
|
|
After #34092 had been merged, there can be few tests failures in fast-test, can someone add |
|
@mergify update |
✅ Branch has been successfully updatedHey, I reacted but my real name is @Mergifyio |
|
95d46f7 to
715200b
Compare
|
Signed-off-by: Azat Khuzhin <[email protected]>
Look at log_comment/current_database for this check under --no-left-queries-check v2: add no-left-queries-check tag support Signed-off-by: Azat Khuzhin <[email protected]>
Signed-off-by: Azat Khuzhin <[email protected]>
This should fix issues like [1], where because one query from the previous test was left the next fails, in this particular report the problem was that 01281_group_by_limit_memory_tracking fails due to the query from 01301_aggregate_state_exception_memory_leak was running in background. [1]: https://s3.amazonaws.com/clickhouse-test-reports/34919/311f884d3d4215f7f82c2dd66ea51d071d313241/stateless_tests__thread__actions__[2/3].html v2: wait for queries in 01249_flush_interactive Signed-off-by: Azat Khuzhin <[email protected]>
@alexey-milovidov may you can take a look now please? |
|
@alexey-milovidov friendly ping |
|
This PR hits a bash bug (that had been fixed in bash 5.1), you may find details in this gist - https://gist.github.com/azat/affbda3f8c6b5c38648d4ab105777d88 |
Changelog category (leave one):