Skip to content

Fix client/server E2E lock root isolation#1048

Merged
stephenamar-db merged 1 commit into
databricks:masterfrom
He-Pin:fix/client-e2e-malformed-timeout
Jun 25, 2026
Merged

Fix client/server E2E lock root isolation#1048
stephenamar-db merged 1 commit into
databricks:masterfrom
He-Pin:fix/client-e2e-malformed-timeout

Conversation

@He-Pin

@He-Pin He-Pin commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Motivation:
It was flasky

Motivation:
Client/server E2E tests launched a server under a test lock directory, but the client process still used the default user.home worker directory. On shared CI hosts this could collide with stale or unrelated sjsonnet workers and leave tests waiting until the 30s client timeout.

Modification:
Give each E2E scenario a short, test-owned user.home, derive the matching mill-worker lockBase for both server and client, wait for the UDS socket before invoking the client, and clean up matching server processes after each scenario. Include server logs in timeout/startup failures.

Result:
The malformed-jsonnet and reuse E2E paths no longer depend on global ~/.sjsonnet state, avoid long UDS paths, and pass repeated stress runs without 30s hangs.
@stephenamar-db stephenamar-db merged commit 05f6320 into databricks:master Jun 25, 2026
5 checks passed
@He-Pin He-Pin deleted the fix/client-e2e-malformed-timeout branch June 25, 2026 17:53
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