Repository navigation
acceptance: always distinguish UUIDs in test output - #7021
Conversation
| matches := repl.Old.FindAllString(s, -1) | ||
| if len(matches) <= 1 { | ||
| // Assign a stable [N] suffix per distinct matched value, in order of first | ||
| // appearance. Number only when there is more than one distinct value: a lone |
There was a problem hiding this comment.
I'd send this change as separate PR, to separate all those diffs unrelate to UUIDs.
| "name": "schema-[UNIQUE_NAME]", | ||
| "owner": "[USERNAME]", | ||
| "schema_id": "[UUID]", | ||
| "updated_at": [UNIX_TIME_MILLIS][0], |
There was a problem hiding this comment.
created_at and updated_at contain the same timestamp, so there is only one distinct value. The generic change adds suffixes only when there are multiple distinct values; repeated occurrences of a single value stay unsuffixed. That behavior and these timestamp golden changes now live in #7420. This PR only adds UUID numbering to metastore_id and schema_id in this file.
✅ Integration test reportCommit: aedd90c
Top 14 slowest tests (at least 2 minutes):
|
26ab8ff to
fc3f149
Compare
767640b to
8fabaa1
Compare
|
Commit: Regression test reportSelected 20 changed tests (limit=20, 76 not selected) 25 tests: regression=0 unreleased=0 coverage=25 failing=0
|
fc3f149 to
5c0a683
Compare
8fabaa1 to
4190d12
Compare
denik
left a comment
There was a problem hiding this comment.
Can you test this for flakiness? For example, by pushing 5 empty commits one after another.
a67dc51 to
95981fe
Compare
21ca39e to
aedd90c
Compare
Numbered UUIDs from main (#7021); restores the volume_id skip in change-name and the recorded schema_id in user_agent/simple, which the rebase dropped. Co-authored-by: Isaac <no-reply@databricks.com>
main now numbers repeated UUIDs in acceptance output (#7021). The pipelines test command stack is based on an older main, so its goldens are regenerated here. This commit becomes empty once that stack is rebased. Co-authored-by: Isaac <no-reply@databricks.com>
❌ Integration test reportCommit: 688c228
18 interesting tests: 14 flaky, 4 FAIL
Top 50 slowest tests (at least 2 minutes):
|
Changes
Remove the temporary
UniqueUUIDoption and always distinguish UUIDs, updating acceptance goldens with numeric suffixes.In the materialization-set
batchandremoval_scopetests, register the deployed set ID as[SET1_ID]withread_id.pyand remove the compact-UUID TOML replacements. This makes the dashed local IDs and compact cloud IDs use the same named replacement before request/operation UUIDs are numbered.Why
Expected output should distinguish different UUIDs consistently. #7423 handles the immutable and template comparisons. The materialization-set fix addresses the deterministic cloud mismatch found during the five sequential CI repetitions.
Tests
./task fmt,./task checks,./task lint, and the materialization-set acceptance tests passed. The full local suite was blocked by the unrelated completion-test SIGPIPE and temporary-home cleanup;inittimepassed on retry. Cloud CI validation is pending.This PR was written by Isaac and revised with Codex.