We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After starting SQL Server 2017 with its credentials on Docker:
docker run -m 2GB -e ACCEPT_EULA=1 -d --name {{ .Env.SQL_SERVER_NAME }} -p:1433:1433 -e SA_PASSWORD={{ .Env.SQLCMDPASSWORD }} mcr.microsoft.com/mssql/server:2017-latest
I'm running the test in Ubuntu 22.04 with:
go test -timeout 30s -run ^TestIncludeFileNoExecutions$
The test TestIncludeFileNoExecutions in go-sqlcmd v1.8.2 is flaky, sometimes failing inconsistently.
TestIncludeFileNoExecutions
Currently we are skipping this test with:
go test -skip=^TestIncludeFileNoExecutions$
The text was updated successfully, but these errors were encountered:
unfortunately I think there's a race condition in go-mssqldb at the root of it. It passes most of the time.
Sorry, something went wrong.
No branches or pull requests
Environment
How to reproduce
After starting SQL Server 2017 with its credentials on Docker:
I'm running the test in Ubuntu 22.04 with:
go test -timeout 30s -run ^TestIncludeFileNoExecutions$
Issue Description
The test
TestIncludeFileNoExecutions
in go-sqlcmd v1.8.2 is flaky, sometimes failing inconsistently.Workaround
Currently we are skipping this test with:
go test -skip=^TestIncludeFileNoExecutions$
The text was updated successfully, but these errors were encountered: