Skip to content

direct: separate state flushing from closing - #6764

Draft
denik wants to merge 1 commit into
mainfrom
denik/dstate-flush-close
Draft

denik wants to merge 1 commit into
mainfrom
denik/dstate-flush-close

Conversation

@denik

@denik denik commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

Changes

Separate direct state flushing from closing so DMS version completion can read state features directly.

Why

Remove the duplicate deployment-history cache while preserving flush-before-complete ordering.

Tests

Unit tests and the bundle DMS acceptance suite.

This PR was written with Codex.

@eng-dev-ecosystem-bot

eng-dev-ecosystem-bot commented Sep 21, 2026

Copy link
Copy Markdown
Collaborator

Integration test report

Commit: ccac919

Run: 35600243241

Env ✅​pass 🙈​skip Time
✅​ aws linux 276 15 5:34
✅​ aws windows 278 13 3:12
✅​ azure linux 275 15 6:04
✅​ azure windows 277 13 4:49
✅​ gcp linux 276 15 6:01
✅​ gcp windows 278 13 3:24
Top 6 slowest tests (at least 2 minutes):
duration env testname
4:47 azure windows TestAccept
4:06 gcp linux TestAccept
3:58 azure linux TestAccept
3:53 aws linux TestAccept
3:22 gcp windows TestAccept
3:10 aws windows TestAccept

@denik
denik force-pushed the denik/dstate-flush-close branch from 909c9f9 to ccac919 Compare September 21, 2026 12:32

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants