Skip to content

Record the profile auth docker configure selects for Docker - #7383

Merged
yolocs merged 1 commit into
mainfrom
stack/docker-shared-workspace-profiles
Nov 20, 2026
Merged

yolocs merged 1 commit into
mainfrom
stack/docker-shared-workspace-profiles

Conversation

@yolocs

@yolocs yolocs commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

Changes

databricks auth docker configure <profile> no longer fails when several profiles match the selected workspace. It records the chosen profile for the registry in the [__settings__] section of .databrickscfg, next to default_profile, and leaves profile sections untouched:

[__settings__]
docker_profile.1234567890123456.container.us-west-2.cloud.databricks.com = prod

Running it with another profile switches the selection:

Warning: Docker credential helper for 1234567890123456.container.us-west-2.cloud.databricks.com switched from profile dev to prod
Configured Docker credential helper for 1234567890123456.container.us-west-2.cloud.databricks.com

databricks auth docker token (the Docker credential helper) picks the profile for a registry like this:

  • A recorded profile wins. If it is missing, no longer targets the registry's workspace, or is no longer supported, the helper fails instead of falling back to another identity.
  • With no recorded profile, a single supported match is used, as before. This covers setups configured with older CLI versions.
  • Otherwise it fails with ... Select the profile for Docker with: databricks auth docker configure <profile-name>.

databricks auth docker host --profile P shows the profile the helper uses for the registry (Credential helper profile: prod, and profile in JSON output). It reports the helper as configured only if Docker's config.json selects it for the registry, it is on PATH, and it would use P.

databricks auth logout --delete removes entries that name the deleted profile, the same way it clears default_profile. The helper then falls back to the no-recorded-profile rules above.

Why

Docker gives the credential helper only the registry host, which encodes the workspace ID, so the helper cannot tell which of several matching profiles was meant. auth login now saves workspace_id on every profile, so two logins to one workspace were enough to block auth docker configure. Recording the choice at configure time means docker push uses the profile that was configured, whatever the order in .databrickscfg, and the helper never switches identity on its own.

The choice is a CLI setting rather than part of a profile's identity, so it lives in [__settings__] like default_profile. Keying it by registry host keeps one entry per registry, and re-pointing a profile at another workspace cannot carry the choice with it. Being in .databrickscfg, it follows DATABRICKS_CONFIG_FILE.

This replaces the "remove the duplicate profile" hint that #7363 added in v1.25.0.

Follow-up: matching compares only the workspace ID and loopback vs remote host, not the deployment's DNS zone, so a profile on another Databricks deployment with the same workspace ID also matches, whether or not it is recorded.

Tests

  • Unit: ProfileForRegistry (recorded profile wins; missing, other-workspace and unsupported recorded profiles fail; no entry keeps the previous rules), GetDockerProfile and SetDockerProfile (new entry, switch, no-op without a write, other registries untouched and read as unset, default_profile kept), ClearDockerProfiles (clears only entries for the given profile, no write when nothing matches or the file is missing), and Inspect (Docker config, PATH and profile selection are all required, and the reported profile in each case).
  • Acceptance: cmd/auth/docker/{configure,configure-errors,token,help}. Configure switches to another profile and back, with host reporting the profile Docker uses and whether it matches, and prints the resulting .databrickscfg. auth logout --delete of the recorded profile clears its entry. A stale entry makes host report not configured and the helper fail. Token errors when several profiles match and none is recorded, and uses the recorded profile over an earlier logged-in one.
  • go test ./cmd/... ./libs/dockercredentials/... ./libs/auth/... ./libs/databrickscfg/... and go test ./acceptance -run 'TestAccept/(cmd|air|auth)/' pass, including air/image-push, which parses the auth docker configure output. Lint, deadcode, whitespace and changelog checks pass.

This pull request and its description were written by Isaac.

@yolocs
yolocs force-pushed the stack/docker-shared-workspace-profiles branch from 849da49 to 71222b5 Compare November 5, 2026 21:25
@github-actions

github-actions Bot commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

Commit: 46c7f24ad | Workflow run

Regression test report

Selected 4 changed tests (limit=20, 0 not selected)

4 tests: regression=3 unreleased=0 coverage=1 failing=0
test branch main (7f25e1e) latest (v1.27.0)
TestAccept/cmd/auth/docker/configure ✅ ❌ ❌
TestAccept/cmd/auth/docker/configure-errors ✅ ✅ ✅
TestAccept/cmd/auth/docker/help ✅ ❌ ❌
TestAccept/cmd/auth/docker/token ✅ ❌ ❌
TestAccept/cmd/auth/docker/configure: branch ✅ | main (7f25e1e) ❌ | latest (v1.27.0) ❌

main (7f25e1e):

acceptance_test.go:1400: Diff:
        --- cmd/auth/docker/configure/output.txt
        +++ /tmp/TestAcceptcmdauthdockerconfigure268272587/002/output.txt
        @@ -65,14 +65,10 @@
         auth_type    = databricks-cli
         workspace_id = [WORKSPACE_ID]
         
        -[__settings__]
        -docker_profile.[WORKSPACE_ID].container.us-west-2.localhost = docker-test
        -
         >>> databricks auth docker host --profile docker-test --output json
         {
           "host": "[WORKSPACE_ID].container.us-west-2.localhost",
        -  "configured": true,
        -  "profile": "docker-test"
        +  "configured": true
         }
         
         >>> print_requests.py --get //api
        @@ -162,82 +155,6 @@
         === Profiles sharing the workspace
         
         >>> databricks auth docker configure shared
        -Warning: Docker credential helper for [WORKSPACE_ID].container.us-west-2.localhost switched from profile docker-test to shared
        -Configured Docker credential helper for [WORKSPACE_ID].container.us-west-2.localhost
        -Updated Docker config: [TEST_TMP_DIR]/home/docker/config.json
        -Installed Docker credential helper: [TEST_TMP_DIR]/home/bin/docker-credential-databricks
        +Error: multiple Databricks profiles match workspace ID [WORKSPACE_ID]: docker-test and shared. Docker credential helper requires exactly one profile per workspace. Remove the duplicate profile with: databricks auth logout --profile <profile-name> --delete
         
        ->>> databricks auth docker host --profile docker-test
        -Registry host: [WORKSPACE_ID].container.us-west-2.localhost
        -Credential helper configured: NO
        -Credential helper profile: shared
        -
        ->>> databricks auth docker host --profile shared
        -Registry host: [WORKSPACE_ID].container.us-west-2.localhost
        -Credential helper configured: YES
        -Credential helper profile: shared
        -
        ->>> databricks auth docker configure docker-test
        -Warning: Docker credential helper for [WORKSPACE_ID].container.us-west-2.localhost switched from profile shared to docker-test
        -Configured Docker credential helper for [WORKSPACE_ID].container.us-west-2.localhost
        -Updated Docker config: [TEST_TMP_DIR]/home/docker/config.json
        -Installed Docker credential helper: [TEST_TMP_DIR]/home/bin/docker-credential-databricks
        -
        ->>> print_requests.py --get --oneline //api
        -{"headers": {"X-Databricks-Workspace-Id": ["[WORKSPACE_ID]"]}, "method": "GET", "path": "/api/2.1/unity-catalog/metastore_summary"}
        -{"headers": {"X-Databricks-Workspace-Id": ["[WORKSPACE_ID]"]}, "method": "GET", "path": "/api/2.1/unity-catalog/metastore_summary"}
        -{"headers": {"X-Databricks-Workspace-Id": ["[WORKSPACE_ID]"]}, "method": "GET", "path": "/api/2.1/unity-catalog/metastore_summary"}
        -{"headers": {"X-Databricks-Workspace-Id": ["[WORKSPACE_ID]"]}, "method": "GET", "path": "/api/2.1/unity-catalog/metastore_summary"}
        -
        ->>> cat [TEST_TMP_DIR]/home/.databrickscfg
        -; The profile defined in the DEFAULT section is to be used as a fallback when no profile is explicitly specified.
        -[DEFAULT]
        -
        -[docker-test]
        -host         = [DATABRICKS_URL]
        -auth_type    = databricks-cli
        -workspace_id = [WORKSPACE_ID]
        -
        -[__settings__]
        -docker_profile.[WORKSPACE_ID].container.us-west-2.localhost = docker-test
        -
        -[shared]
        -host         = [DATABRICKS_URL]
        -auth_type    = databricks-cli
        -workspace_id = [WORKSPACE_ID]
        -
        ->>> docker-credential-databricks get
        -{
        -  "Secret": "oauth-token",
        -  "Username": "oauthtoken"
        -}
        -
        -=== Deleting the recorded profile clears its Docker selection
        -
        ->>> databricks auth logout --profile docker-test --delete --auto-approve
        -Logged out of and deleted profile "docker-test".
        -
        ->>> cat [TEST_TMP_DIR]/home/.databrickscfg
        -; The profile defined in the DEFAULT section is to be used as a fallback when no profile is explicitly specified.
        -[DEFAULT]
        -
        -[__settings__]
        -
        -[shared]
        -host         = [DATABRICKS_URL]
        -auth_type    = databricks-cli
        -workspace_id = [WORKSPACE_ID]
        -
        ->>> databricks auth docker host --profile shared
        -Registry host: [WORKSPACE_ID].container.us-west-2.localhost
        -Credential helper configured: YES
        -Credential helper profile: shared
        -
        -=== Recorded profile that no longer exists
        -
        ->>> databricks auth docker host --profile shared
        -Registry host: [WORKSPACE_ID].container.us-west-2.localhost
        -Credential helper configured: NO
        -
        ->>> musterr docker-credential-databricks get
        -Error: profile "gone" selected for Docker registry [WORKSPACE_ID].container.us-west-2.localhost is missing or no longer targets workspace ID [WORKSPACE_ID]. Select the profile for Docker with: databricks auth docker configure <profile-name>
        +Exit code: 1
        
    acceptance_test.go:1178: 
        LOG.configure-again: Configured Docker credential helper for 900800700600.container.us-west-2.localhost
        LOG.configure-again: Updated Docker config: /tmp/TestAcceptcmdauthdockerconfigure268272587/001/home/docker/config.json
        LOG.configure-again: Installed Docker credential helper: /tmp/TestAcceptcmdauthdockerconfigure268272587/001/home/bin/docker-credential-databricks
FAIL

latest (v1.27.0): same output as main (7f25e1e)

TestAccept/cmd/auth/docker/help: branch ✅ | main (7f25e1e) ❌ | latest (v1.27.0) ❌

main (7f25e1e):

acceptance_test.go:1400: Diff:
        --- cmd/auth/docker/help/output.txt
        +++ /tmp/TestAcceptcmdauthdockerhelp756397943/002/output.txt
        @@ -65,14 +65,11 @@
         This command installs docker-credential-databricks and configures Docker to use
         it for the selected workspace's Artifact Registry host. If the selected profile
         does not already include a workspace_id, the command resolves and saves it so
        -the Docker helper can map the registry host back to the profile. The command
        -also records the profile for the registry host in the [__settings__] section of
        -the configuration file, so the helper uses it when other profiles match the same
        -workspace; run the command with another profile to switch. The registry region
        -is inferred from the workspace's metastore. Select the workspace with [PROFILE]
        -or --profile; --host, --account-id, and --workspace-id are not supported. The
        -deprecated --region flag is retained for compatibility; omit it because it will
        -be fully removed in the next release.
        +the Docker helper can map the registry host back to the profile. The registry
        +region is inferred from the workspace's metastore. Select the workspace with
        +[PROFILE] or --profile; --host, --account-id, and --workspace-id are not
        +supported. The deprecated --region flag is retained for compatibility; omit it
        +because it will be fully removed in the next release.
         
         Usage:
           databricks auth docker configure [PROFILE] [flags]
        @@ -93,9 +90,7 @@
         >>> [CLI] auth docker host --help
         (Experimental) Show the Databricks Artifact Registry host and Docker credential helper status for a profile.
         
        -The output names the profile the credential helper uses for the registry. The
        -helper counts as configured only if Docker's config.json selects it for the
        -registry and it uses this profile. The --profile flag is required.
        +The --profile flag is required.
         
         Usage:
           databricks auth docker host [flags]

latest (v1.27.0): same output as main (7f25e1e)

TestAccept/cmd/auth/docker/token: branch ✅ | main (7f25e1e) ❌ | latest (v1.27.0) ❌

main (7f25e1e):

acceptance_test.go:1400: Diff:
        --- cmd/auth/docker/token/output.txt
        +++ /tmp/TestAcceptcmdauthdockertoken101615255/002/output.txt
        @@ -54,17 +54,11 @@
         === Multiple profiles for the workspace
         
         >>> musterr [CLI] auth docker token
        -Error: multiple Databricks profiles match workspace ID [WORKSPACE_ID]: docker-test and duplicate. Select the profile for Docker with: databricks auth docker configure <profile-name>
        +Error: multiple Databricks profiles match workspace ID [WORKSPACE_ID]: docker-test and duplicate. Docker credential helper requires exactly one profile per workspace. Remove the duplicate profile with: databricks auth logout --profile <profile-name> --delete
         
         === Recorded profile for the workspace
         
         >>> [CLI] auth docker token --no-force-refresh
        -{
        -  "Secret": "duplicate-access-token",
        -  "Username": "oauthtoken"
        -}
        +Error: multiple Databricks profiles match workspace ID [WORKSPACE_ID]: docker-test and duplicate. Docker credential helper requires exactly one profile per workspace. Remove the duplicate profile with: databricks auth logout --profile <profile-name> --delete
         
        -=== Recorded profile that no longer exists
        -
        ->>> musterr [CLI] auth docker token
        -Error: profile "gone" selected for Docker registry [WORKSPACE_ID].container.us-west-2.localhost is missing or no longer targets workspace ID [WORKSPACE_ID]. Select the profile for Docker with: databricks auth docker configure <profile-name>
        +Exit code: 1

latest (v1.27.0): same output as main (7f25e1e)

@eng-dev-ecosystem-bot

eng-dev-ecosystem-bot commented Nov 5, 2026 •

Copy link
Copy Markdown
Collaborator

✅ Integration test report

Commit: 46c7f24

Run: 44651672559

Env 💚​RECOVERED ✅​pass 🙈​skip Time
💚​ aws linux-2core-8gb 1 272 23 5:00
💚​ aws-windows-latest-4core-16gb 1 274 21 5:24
💚​ azure linux-2core-8gb 1 271 23 4:25
💚​ azure-windows-latest-4core-16gb 1 273 21 4:15
💚​ gcp linux-2core-8gb 1 272 23 4:41
💚​ gcp-windows-latest-4core-16gb 1 274 21 4:08
Test Name aws linux-2core-8gb aws-windows-latest-4core-16gb azure linux-2core-8gb azure-windows-latest-4core-16gb gcp linux-2core-8gb gcp-windows-latest-4core-16gb
💚​ TestAccept 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
Top 4 slowest tests (at least 2 minutes):
duration env testname
4:16 aws-windows-latest-4core-16gb TestAccept
4:13 azure-windows-latest-4core-16gb TestAccept
4:06 gcp-windows-latest-4core-16gb TestAccept
2:00 gcp linux-2core-8gb TestAccept

@yolocs
yolocs force-pushed the stack/docker-shared-workspace-profiles branch from 71222b5 to 79702a7 Compare November 5, 2026 22:12
@yolocs
yolocs marked this pull request as ready for review November 5, 2026 22:13
@yolocs
yolocs requested review from a team as code owners November 5, 2026 22:13

@pietern pietern left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can have unintended side effects. Let's say you configure Docker assuming profile B, but profile A is earlier in the .databrickscfg for the same workspace host. What happens? Does a docker push use profile A?

I recommend using the "default profile" switcher (run databricks auth switch to see what happens) to be the tie-breaker, if it exists, and keep the error otherwise.

@yolocs

yolocs commented Nov 9, 2026

Copy link
Copy Markdown
Contributor Author

This can have unintended side effects. Let's say you configure Docker assuming profile B, but profile A is earlier in the .databrickscfg for the same workspace host. What happens? Does a docker push use profile A?

I recommend using the "default profile" switcher (run databricks auth switch to see what happens) to be the tie-breaker, if it exists, and keep the error otherwise.

@pietern Yes, it will indeed have potential unintended effects. The problem originates from the credential helper protocol which can only use hostname (not profile) to pick the profile to get the auth token. And our user feedback suggested they'd prefer allowing profiles linking to the same workspace.

Your suggest would only work if one of such profiles is the default profile, right?

@rugpanov
rugpanov removed their request for review November 11, 2026 19:59
@yolocs
yolocs force-pushed the stack/docker-shared-workspace-profiles branch 2 times, most recently from 49a2dc9 to 4b40835 Compare November 12, 2026 22:05
@yolocs yolocs changed the title Allow auth docker configure when profiles share a workspace Record the profile auth docker configure selects for Docker Nov 12, 2026
@yolocs
yolocs force-pushed the stack/docker-shared-workspace-profiles branch from 4b40835 to 68233ed Compare November 12, 2026 22:46
@yolocs

yolocs commented Nov 12, 2026

Copy link
Copy Markdown
Contributor Author

@pietern I'm now trying a better way to disambiguate the profile. It saves a new value in .databrickscfg. PTAL.

@yolocs
yolocs requested a review from pietern November 12, 2026 23:43
@pietern pietern added the auth label Nov 16, 2026
@yolocs
yolocs force-pushed the stack/docker-shared-workspace-profiles branch from 68233ed to c10c14a Compare November 18, 2026 17:24
@yolocs
yolocs requested a review from parthban-db November 19, 2026 21:27

@parthban-db parthban-db left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM modulo comments; all of them are non-blocking. Thanks @yolocs for moving it to [__settings__]!

Note: this review was done by AI (Claude).

Comment thread libs/dockercredentials/configure.go Outdated
if err != nil {
log.Debugf(ctx, "Docker credential helper cannot resolve %s to a profile: %v", registryHost, err)
}
configured = err == nil && selected.Name == profileName

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can auth docker host print the profile the helper resolves to, instead of folding it into Configured? NO can now mean Docker isn't set up, it's set up for another profile, several profiles match with none recorded, or the recorded profile is gone, and the reason is only logged at debug level. Something like Credential helper profile: shared, plus a profile field in the JSON output, would make it clear which profile Docker uses.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 46c7f24. host now prints Credential helper profile: <name> and a profile JSON field, and leaves them out when the helper can't resolve a profile.

Comment thread libs/dockercredentials/profile.go Outdated
return profile.Profile{}, fmt.Errorf("no Databricks profile found for workspace ID %s from registry host %s. Run databricks auth login --host <workspace-url> and set workspace_id for that profile", registry.WorkspaceID, registry.Host)
}

recorded, err := databrickscfg.GetDockerProfile(ctx, registry.Host, env.Get(ctx, "DATABRICKS_CONFIG_FILE"))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] ProfileForRegistry takes a profiler for the profiles but reads the recorded selection from DATABRICKS_CONFIG_FILE itself. That's why the tests now need both an InMemoryProfiler and a real file. Can we pass the recorded profile in, so both come from one place? The two callers can call GetDockerProfile.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 46c7f24. Both callers now call GetDockerProfile and pass the result in, so the tests no longer need a config file.

Comment thread libs/databrickscfg/ops.go Outdated
configFile.DeleteSection(profileName)
}

if settings, err := configFile.GetSection(databricksSettingsSection); err == nil {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] Logout clears default_profile with ClearDefaultProfile after DeleteProfile. Why are the Docker entries handled inside DeleteProfile instead? Let's do both the same way: either add a ClearDockerProfiles next to ClearDefaultProfile, or move both into DeleteProfile.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Went with ClearDockerProfiles next to ClearDefaultProfile, called from logout right after it (46c7f24). Moving both into DeleteProfile would mean removing ClearDefaultProfile, which felt out of scope here.

}
}

func TestInspectRequiresDockerConfigAndProfile(t *testing.T) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] Why a different table? TestInspectRequiresHelperOnPath tests the same Inspect call, so installed and onPath can be fields in this table.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 46c7f24. Merged into one TestInspect table.

Comment thread libs/databrickscfg/ops.go Outdated
return writeConfigFile(ctx, configFile)
}

// GetDockerProfile returns the profile recorded for the Docker registry host, or "" if none is recorded.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] Can we wrap these comments at about 80 characters, like the rest of ops.go? Ditto profile.go:59 and configure.go:42.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 46c7f24.

auth docker configure no longer fails when several profiles match the workspace. It records the selected profile for the registry host as docker_profile.<registry-host> in the [__settings__] section of .databrickscfg, alongside default_profile, and warns when the selection switches. auth docker token uses the recorded profile and fails instead of falling back when it no longer matches. auth docker host shows the profile the helper uses and reports the helper as configured only if Docker's config selects it and it uses that profile. auth logout --delete removes entries naming the deleted profile, next to clearing default_profile.

Co-authored-by: Isaac <no-reply@databricks.com>
@yolocs
yolocs force-pushed the stack/docker-shared-workspace-profiles branch from c10c14a to 46c7f24 Compare November 20, 2026 01:10
@yolocs
yolocs added this pull request to the merge queue Nov 20, 2026
Merged via the queue into main with commit d96e1fe Nov 20, 2026
28 checks passed
@yolocs
yolocs deleted the stack/docker-shared-workspace-profiles branch November 20, 2026 01:44
@eng-dev-ecosystem-bot

Copy link
Copy Markdown
Collaborator

❌ Integration test report

Commit: d96e1fe

Run: 44655915127

Env 🟨​KNOWN 💚​RECOVERED ✅​pass 🙈​skip Time
💚​ aws linux-2core-8gb 27 1619 1419 169:07
🟨​ azure linux-2core-8gb 6 21 1599 1427 161:54
💚​ gcp linux-2core-8gb 27 1606 1425 173:12
27 interesting tests: 21 RECOVERED, 6 KNOWN
Test Name aws linux-2core-8gb azure linux-2core-8gb gcp linux-2core-8gb
🟨​ TestAccept 💚​R 🟨​K 💚​R
🟨​ TestAccept/bundle/deployment/bind/alert 💚​R 🟨​K 💚​R
🟨​ TestAccept/bundle/deployment/bind/alert/DMS= 💚​R 🟨​K 💚​R
🟨​ TestAccept/bundle/deployment/bind/alert/DMS=true 💚​R 🟨​K 💚​R
💚​ TestAccept/bundle/generate/alert 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/generate/alert/DMS= 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/generate/alert/DMS=true 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/alerts/basic 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/alerts/basic/DMS= 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/alerts/basic/DMS=true 💚​R 💚​R 💚​R
🟨​ TestAccept/bundle/resources/alerts/with_file 💚​R 🟨​K 💚​R
🟨​ TestAccept/bundle/resources/alerts/with_file/DMS= 💚​R 🟨​K 💚​R
💚​ TestAccept/bundle/resources/alerts/with_file/DMS=true 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-omitted 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-omitted/DMS= 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-omitted/DMS=true 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-toggle 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS= 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS=true 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started/DMS= 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started/DMS=true 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/postgres_synced_tables/basic 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/postgres_synced_tables/basic/DMS= 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/postgres_synced_tables/recreate 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/postgres_synced_tables/recreate/DMS= 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/postgres_synced_tables/recreate/DMS=true 💚​R 💚​R 💚​R
Top 50 slowest tests (at least 2 minutes):
duration env testname
9:41 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
9:38 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
9:11 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
8:37 gcp linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
8:20 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
8:03 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
7:48 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
7:11 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=
7:03 aws linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
7:02 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=true
6:39 gcp linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
6:29 gcp linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
6:21 aws linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=
6:13 azure linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
6:09 aws linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
5:57 gcp linux-2core-8gb TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=cluster.yml.tmpl/READPLAN=1
5:36 gcp linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=
5:29 azure linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
5:24 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
5:14 aws linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
5:08 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
4:59 azure linux-2core-8gb TestAccept/pipelines/run/refresh-flags
4:50 azure linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
4:28 gcp linux-2core-8gb TestAccept/pipelines/run/refresh-flags
4:27 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS=
4:19 aws linux-2core-8gb TestAccept/pipelines/run/refresh-flags
4:15 aws linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
3:55 aws linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
3:41 azure linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
3:40 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS=true
3:34 gcp linux-2core-8gb TestAccept/bundle/deploy/spark-jar-task/DMS=
3:29 azure linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
3:27 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started-omitted/DMS=
3:25 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS=true
3:22 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS=
3:20 aws linux-2core-8gb TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN=
3:18 aws linux-2core-8gb TestAccept/bundle/deploy/spark-jar-task/DMS=
3:14 gcp linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS=
3:10 gcp linux-2core-8gb TestAccept/bundle/deploy/spark-jar-task/DMS=true
3:09 gcp linux-2core-8gb TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN=1
3:07 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started-omitted/DMS=true
3:05 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/resize-terminated-fallback/DMS=true
3:04 azure linux-2core-8gb TestAccept/bundle/deploy/spark-jar-task/DMS=true
3:02 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/deploy/update-after-create/DMS=true
2:59 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/deploy/data_security_mode/DMS=
2:56 aws linux-2core-8gb TestAccept/bundle/deploy/spark-jar-task/DMS=true
2:54 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started-omitted/DMS=true
2:54 azure linux-2core-8gb TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN=
2:53 aws linux-2core-8gb TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN=
2:52 gcp linux-2core-8gb TestAccept/bundle/templates/default-python/combinations/serverless/DLT=no/DMS=/NBOOK=no/PY=yes/READPLAN=

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants