Skip to content

[auto-bump] [no-release-notes] dependency by jycor#2749

Open
coffeegoddd wants to merge 1 commit into
mainfrom
jycor-9f0b9e79
Open

[auto-bump] [no-release-notes] dependency by jycor#2749
coffeegoddd wants to merge 1 commit into
mainfrom
jycor-9f0b9e79

Conversation

@coffeegoddd
Copy link
Copy Markdown
Contributor

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]
```

@github-actions
Copy link
Copy Markdown
Contributor

Main PR
covering_index_scan_postgres 1311.59/s 1315.19/s +0.2%
index_join_postgres 187.41/s 188.71/s +0.6%
index_join_scan_postgres 196.36/s 197.61/s +0.6%
index_scan_postgres 12.28/s 12.30/s +0.1%
oltp_point_select 2405.19/s 2391.79/s -0.6%
oltp_read_only 1768.51/s 1780.18/s +0.6%
select_random_points 127.11/s 127.39/s +0.2%
select_random_ranges 867.64/s 862.93/s -0.6%
table_scan_postgres 11.99/s 12.00/s 0.0%
types_table_scan_postgres 5.51/s 5.50/s -0.2%

@itoqa
Copy link
Copy Markdown

itoqa Bot commented May 22, 2026

Ito Test Report ✅

7 test cases ran. 7 passed.

The unified QA run passed all executed tests (7/7, 0 failures, with one additional check-only segment reporting no confirmed defects), indicating no verified production logic defects in scope. Key validations showed first-boot auto-creation of the default database, correct authentication behavior (valid SCRAM login succeeds and out-of-order SCRAM frames are rejected without residual session auth), correct COPY FROM STDIN commit and post-error recovery behavior, and correct SERIAL/sequence wiring plus boundary enforcement, while noting these results were obtained after local environment remediation with temporary role/auth bypasses (and SCRAM disabled in the SERIAL-focused run) to stabilize test setup.

✅ Passed (7)
Category Summary Screenshot
Authentication After restoring the stopped nested container and starting Doltgres, postgres/password successfully authenticated to sqllogictest on 127.0.0.1:5432 and SELECT current_user returned postgres@127.0.0.1. AUTHENTICATION-1
Authentication Raw wire-protocol probe sent an out-of-order SASLResponse before SASLInitialResponse; server closed the connection (EOF), subsequent query on same socket was unusable, and a fresh connection authenticated normally. AUTHENTICATION-2
Copy Using psql against sqllogictest, COPY FROM STDIN accepted multi-row text input and returned COPY 3; subsequent SELECT confirmed rows persisted after CopyDone. COPY-1
Copy Injected invalid COPY data chunk to force failure; COPY returned type-conversion error, no partial rows remained, and normal SQL executed immediately afterward in the same session. COPY-2
Sequence CREATE TABLE serial_t(id SERIAL...) produced a nextval-backed default and insert without id generated id=1 via public.serial_t_id_seq. SEQUENCE-1
Sequence Using smallserial/serial/bigserial tables, inserts at each subtype max succeeded after setting sequence to max-1, and one-beyond inserts consistently failed with sequence maximum errors. SEQUENCE-2
Startup Startup flow successfully created and selected getting_started on first boot via the normal CLI path. STARTUP-1

Commit: da068c9

View Full Run


Tell us how we did: Give Ito Feedback

@github-actions
Copy link
Copy Markdown
Contributor

Main PR
Total 42090 42090
Successful 18197 18197
Failures 23893 23893
Partial Successes1 5392 5392
Main PR
Successful 43.2335% 43.2335%
Failures 56.7665% 56.7665%

Footnotes

  1. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants