dolt/integration-tests at 83602c2f80ee4c05251702a46621b7450db2a0cf - dolt - Gitea

mirror of https://github.com/dolthub/dolt.git synced 2026-03-06 10:29:33 -06:00

Files

Aaron Son 83602c2f80 [no-release-notes] integration-tests/bats: ls.bats: Fix a flakey failure where an unlucky hash could cause a negative assertion to fail.

ls.bats was using test table names like `t1` and `t2` and making assertions
against the output of `dolt ls`. But the output of `dolt ls` also sometimes
includes a commit hash, which can itself contain these strings.

Change it so that we use names which will never appear in a commit hash.

2023-11-30 16:23:39 -08:00

bats

[no-release-notes] integration-tests/bats: ls.bats: Fix a flakey failure where an unlucky hash could cause a negative assertion to fail.

2023-11-30 16:23:39 -08:00

compatibility

Update bats tests. These tests test handling data conflicts, but the behavior that was in the test (row deletion + column deletion) is no longer a conflict. This commit changes the behavior to something else that is a conflict.

2023-11-15 14:36:19 -08:00

data-dump-loading-tests

fix failing bats tests

2023-10-18 12:12:23 -07:00

go-sql-server-driver

integration-tests/go-sql-server-driver: sql-server-cluster-users-and-grants.yaml: branch_control_block_on_write_replication: Add an assertion on a connection to server2 after the branch control perms replicate, to ensure we don't send the TERM signal to the server process at the end of the test before it is fully started up.