You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Across the unified run, all 10 of 10 tests passed with zero failures, indicating stable sql-engine runtime compatibility, cold-start bootstrap, startup/authentication flow, session lifecycle handling, reconnect behavior, and extended-protocol bind execution. The most important findings were that the server consistently reached query-ready state (including GSS fallback and reconnect storms), auto-created and served the default database from an empty data directory, preserved metadata/result consistency across bind and literal variants, correctly rejected invalid logins before successful recovery, and showed no session-leak signals during reset/disconnect scenarios, with the caveat that authentication and some reset paths were exercised under deterministic test adjustments (e.g., role-check bypasses, SCRAM disabled, and reset simulated via DISCARD ALL rather than direct wire-level reset opcodes).
✅ Passed (10)
Category
Summary
Screenshot
Engine
Startup authentication reached query-ready state and the first query succeeded.
Engine
GSS negotiation fallback completed safely and the session executed queries.
Engine
Bind-variable execution path returned the expected result via extended protocol binding.
Engine
Alternating SSL failure and reconnect success cycles stayed deterministic and query-ready.
Engine
Mixed bind and literal executions remained consistent across repeats and reconnects.
Session
Connected, ran sequential queries, and reconnected cleanly with no lifecycle-breaking errors.
Session
Invalid credentials were rejected, then valid login and query execution succeeded.
Session
Reset-path review found serialized message handling and reset logic that preserves selected DB context.
Session
Reset/disconnect cleanup review found deferred connection teardown and no session-leak signal.
Startup
With empty DOLTGRES_DATA_DIR, server started and accepted postgres connection to sqllogictest; bootstrap database was queryable immediately.
These are tests that we're marking as Successful, however they do not match the expected output in some way. This is due to small differences, such as different wording on the error messages, or the column names being incorrect while the data itself is correct. ↩
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
☕ An Automated Dependency Version Bump PR 👑
Initial Changes
The changes contained in this PR were produced by `go get`ing the dependency.
```bash
go get github.com/dolthub/[dependency]/go@[commit]
```