Skip to content

air: validate list filters and support full accelerator types - #7515

Merged
caroline-db merged 4 commits into
mainfrom
air/list-filter-validation
Nov 13, 2026
Merged

caroline-db merged 4 commits into
mainfrom
air/list-filter-validation

Conversation

@caroline-db

@caroline-db caroline-db commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Changes

  • Preserve case-insensitive substring matching for accelerator families, including legacy run identifiers, and add exact matching for full YAML accelerator types.
  • Search existing runs before validating unmatched accelerator filters against workspace compute options. Return workspace-derived suggestions and document how to discover supported types.
  • Reject empty filters and malformed experiment globs instead of silently returning no runs.

Examples:

$ databricks air list --filter accelerator_type=GPU_1xA10
# Matches only GPU_1xA10 runs.

$ databricks air list --filter accelerator_type=H100
# Matches H100 runs using legacy family matching.

$ databricks air list --filter accelerator_type=1xA10
Error: invalid --filter accelerator_type="1xA10": use "GPU_1xA10"

$ databricks air list --filter accelerator_type=V100
Error: invalid --filter accelerator_type="V100": valid values for this workspace include families (...), full types (...)

Why

Users copying accelerator values from workload YAML or supplying invalid filters received misleading empty results. This adds YAML-compatible filtering and actionable validation without breaking existing family filters or historical runs. Addresses CNXT-2522 and CNXT-2584.

Tests

  • ./task fmt
  • ./task checks
  • ./task lint
  • go test ./cmd/air
  • go test ./acceptance -run "^TestAccept/air/" -tail
  • Focused race tests for list validation paths
  • ./task test: all unit tests passed; the full acceptance suite was blocked by unrelated network-disabled bundle tests that could not download Python build dependencies

This PR was written with Codex.

@caroline-db
caroline-db requested review from a team as code owners November 11, 2026 21:55
@github-actions github-actions Bot added the AIR Databricks AI Runtime CLI label Nov 11, 2026
@github-actions

github-actions Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Commit: b2b3c8012 | Workflow run

Regression test report

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

1 tests: regression=1 unreleased=0 coverage=0 failing=0
test branch main (db52460) latest (v1.26.0)
TestAccept/air/help ✅ ❌ ❌
TestAccept/air/help: branch ✅ | main (db52460) ❌ | latest (v1.26.0) ❌

main (db52460):

acceptance_test.go:1374: Diff:
        --- air/help/output.txt
        +++ /tmp/TestAcceptairhelp2190746007/002/output.txt
        @@ -52,9 +52,7 @@
         Filters:
           Use --filter KEY=VALUE per condition. A run must match every condition.
         
        -  accelerator_type  Accelerator family or full YAML type. Examples:
        -                    A10, H100, GPU_1xA10, GPU_8xH100.
        -                    Workspace types: databricks air run -h config.compute.accelerator_type
        +  accelerator_type  Accelerator type, such as A10 or H100.
           experiment        Case-insensitive glob matched against the experiment name.
           num_accelerators  Total GPU count.
           user              Run creator identifier.
        @@ -65,8 +63,6 @@
         Examples:
           databricks air list --filter accelerator_type=H100
         
        -  databricks air list --filter accelerator_type=GPU_8xH100
        -
           databricks air list --all-status \
             --filter 'experiment=qwen*' \
             --filter num_accelerators=8 \
        
FAIL

latest (v1.26.0):

acceptance_test.go:1374: Diff:
        --- air/help/output.txt
        +++ /tmp/TestAcceptairhelp2366898560/002/output.txt
        @@ -2,31 +2,23 @@
         === help
         
         >>> [CLI] air --help
        -Run GPU workloads on Databricks serverless compute.
        +Run and manage AI Runtime training workloads on Databricks serverless GPU compute.
         
        -Describe a workload in a YAML file and submit it with "databricks air run".
        -Follow a run with "databricks air logs" and "databricks air get", or see your
        -active runs with "databricks air list".
        +These commands are under active development.
         
         Usage:
           databricks air [command]
         
        -Run workloads:
        -  run             Submit a workload from a YAML config
        -
        -Manage runs:
        +Available Commands:
           cancel          Cancel one or more runs
        -  get             Show a run's status, configuration, and timing
        -  list            List your active runs
        -  logs            Stream or fetch a run's logs
        +  convert-to-dabs Convert an AIR run YAML into a Databricks Asset Bundle
        +  get             Show status, configuration, and timing details for a specified run
        +  images          Manage container images for AI Runtime
        +  list            List active runs for the current user
        +  logs            Stream or fetch logs for a run
        +  pools           View provisioned GPU pools
        +  run             Submit a training workload from a YAML config
         
        -Package and deploy:
        -  convert-to-dabs Convert a workload YAML into a Databricks Asset Bundle
        -  images          Push container images for custom environments
        -
        -Provisioned capacity:
        -  pools           View GPU pools provisioned for your workspace
        -
         Flags:
           -h, --help   help for air
         
        @@ -38,12 +23,6 @@
         
         Use "databricks air [command] --help" for more information about a command.
         
        -Learn more:
        -  YAML fields and example  databricks air run -h config
        -  Quickstart (AWS)         https://docs.databricks.com/aws/en/machine-learning/ai-runtime/quickstart
        -  Quickstart (Azure)       https://learn.microsoft.com/azure/databricks/machine-learning/ai-runtime/quickstart
        -  Coding agent skill       databricks aitools install --skills-only --skills databricks-ai-runtime
        -
         === list help
         
         >>> [CLI] air list --help
        @@ -52,9 +31,7 @@
         Filters:
           Use --filter KEY=VALUE per condition. A run must match every condition.
         
        -  accelerator_type  Accelerator family or full YAML type. Examples:
        -                    A10, H100, GPU_1xA10, GPU_8xH100.
        -                    Workspace types: databricks air run -h config.compute.accelerator_type
        +  accelerator_type  Accelerator type, such as A10 or H100.
           experiment        Case-insensitive glob matched against the experiment name.
           num_accelerators  Total GPU count.
           user              Run creator identifier.
        @@ -65,8 +42,6 @@
         Examples:
           databricks air list --filter accelerator_type=H100
         
        -  databricks air list --filter accelerator_type=GPU_8xH100
        -
           databricks air list --all-status \
             --filter 'experiment=qwen*' \
             --filter num_accelerators=8 \
        @@ -88,9 +63,9 @@
         === get help
         
         >>> [CLI] air get --help
        -Show a run's status, configuration, and timing.
        +Show status, configuration, and timing details for a specified run.
         
        -JOB_RUN_ID is the job run ID returned by "databricks air run".
        +JOB_RUN_ID is the job run ID returned by "air run".
         
         Usage:
           databricks air get JOB_RUN_ID [flags]
        @@ -107,18 +81,14 @@
         === pools help
         
         >>> [CLI] air pools --help
        -View GPU pools provisioned for your workspace.
        +View provisioned GPU pools
         
        -A GPU pool is dedicated accelerator capacity that your Databricks account team
        -provisions. Pools are optional: a run uses one only when its YAML sets
        -compute.pool_id.
        -
         Usage:
           databricks air pools [flags]
           databricks air pools [command]
         
         Available Commands:
        -  get         Show a GPU pool and its accelerator usage
        +  get         Show a GPU pool, including its accelerator usage (POOL_ID may be omitted when the workspace has exactly one pool)
           list        List the GPU pools available to the current workspace
         
         Flags:
        @@ -135,7 +99,7 @@
         === images help
         
         >>> [CLI] air images --help
        -Push container images for custom environments
        +Manage container images for AI Runtime
         
         Usage:
           databricks air images [flags]
        @@ -159,7 +123,7 @@
         
         >>> [CLI] air images push --help
         This CLI command is in Preview. For current feature status and requirements, see:
        -  AWS: https://docs.databricks.com/aws/en/machine-learning/ai-runtime/connecting/cli/docker-images
        +  AWS: https://docs.databricks.com/aws/en/machine-learning/ai-runtime/cli/docker-images
           Azure: https://learn.microsoft.com/azure/databricks/machine-learning/ai-runtime/connecting/cli/docker-images
         
         Push a container image to Databricks Artifact Registry under the specified Unity Catalog catalog and schema.
        @@ -195,7 +159,7 @@
         Stream logs from an active run until it completes, or fetch logs from a
         completed run.
         
        -JOB_RUN_ID is the job run ID returned by "databricks air run".
        +JOB_RUN_ID is the job run ID returned by "air run".
         
         Usage:
           databricks air logs JOB_RUN_ID [flags]
        
FAIL

@eng-dev-ecosystem-bot

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

Copy link
Copy Markdown
Collaborator

✅ Integration test report

Commit: b2b3c80

Run: 43320726919

Env 🔄​flaky 💚​RECOVERED ✅​pass 🙈​skip Time
💚​ aws linux-2core-8gb 1 270 16 14:04
🔄​ aws-windows-latest-4core-16gb 1 1 271 14 10:36
🔄​ azure linux-2core-8gb 1 1 268 16 13:37
🔄​ azure-windows-latest-4core-16gb 1 1 270 14 10:42
🔄​ gcp linux-2core-8gb 1 1 269 16 12:57
💚​ gcp-windows-latest-4core-16gb 1 272 14 10:06
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
🔄​ TestSyncIncrementalFileSync ✅​p 🔄​f 🔄​f ✅​p ✅​p ✅​p
🔄​ TestSyncIncrementalSyncFileToPythonNotebook ✅​p ✅​p ✅​p 🔄​f ✅​p ✅​p
🔄​ TestSyncNestedFolderSync ✅​p ✅​p ✅​p ✅​p 🔄​f ✅​p
Top 25 slowest tests (at least 2 minutes):
duration env testname
3:55 gcp linux-2core-8gb TestAccept
3:49 aws linux-2core-8gb TestAccept
3:49 azure linux-2core-8gb TestAccept
3:46 aws-windows-latest-4core-16gb TestAccept
3:45 gcp-windows-latest-4core-16gb TestAccept
3:38 azure-windows-latest-4core-16gb TestAccept
3:25 gcp-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsStat
2:59 gcp linux-2core-8gb TestFilerRecursiveDelete/workspace_files
2:42 azure-windows-latest-4core-16gb TestFilerRecursiveDelete/workspace_files_extensions
2:38 gcp-windows-latest-4core-16gb TestFilerReadDir/workspace_files_extensions
2:32 aws linux-2core-8gb TestFilerWorkspaceFilesExtensionsReadDir
2:32 aws-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsStat
2:27 gcp linux-2core-8gb TestFilerRecursiveDelete/workspace_files_extensions
2:26 azure linux-2core-8gb TestImportDir
2:25 aws linux-2core-8gb TestFilerRecursiveDelete/workspace_files
2:25 aws-windows-latest-4core-16gb TestFilerRecursiveDelete/workspace_files
2:25 azure linux-2core-8gb TestFilerWorkspaceFilesExtensionsReadDir
2:10 aws linux-2core-8gb TestImportDirWithOverwriteFlag
2:09 azure linux-2core-8gb TestFilerRecursiveDelete/workspace_files_extensions
2:08 azure-windows-latest-4core-16gb TestExportDir
2:08 gcp-windows-latest-4core-16gb TestFilerWorkspaceNotebook/rJupyterNb.ipynb
2:04 aws linux-2core-8gb TestFilerReadWrite/workspace_files_extensions
2:03 gcp-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsDelete
2:02 azure linux-2core-8gb TestFilerWorkspaceFilesExtensionsStat
2:02 gcp linux-2core-8gb TestImportDirWithOverwriteFlag

@caroline-db
caroline-db removed the request for review from shreyas-goenka November 11, 2026 22:33
Comment thread cmd/air/list_filter.go Outdated
}

func validAcceleratorFilterHint() string {
return "use a family name (A10, H100, B300, RTX6000) or a full type; " + validGPUTypesHint()

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: The family list (A10, H100, B300, RTX6000) is hardcoded here, so it will drift the next time a type is added to gpuTypes. Could we build it from gpuTypes via gpuDisplayName (deduped, since 1x and 8x H100 share a family), the same way validGPUTypesHint builds the full-type list?

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.

updating this to be workspace aware and not hardcoded, especially following steven's changes to avoid hardcoding in cli help as well

Comment thread cmd/air/list.go Outdated

accelerator_type Accelerator type, such as A10 or H100.
accelerator_type Accelerator family or exact full type. Examples: A10, H100,
GPU_1xA10, GPU_8xH100.

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.

Human readability: The air list table shows accelerators as 8x H100, so a user who copies that value into --filter accelerator_type=8x H100 gets an error. The error does list the valid values, but could we either accept the table's display format or say here that the table format isn't accepted as a filter value?

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.

the table shows <num accelerators>x <accelerator family> meaning it would show 16x H100 for a 2 node 8xh100, the 8 here refers to total num accelerators rather than part of the accelerator type. I think we can leave this behavior for now rather than adding a new supported 8x H100 or 8xH100 type, and I'll update the error and help to be more explicit about this.

@caroline-db
caroline-db force-pushed the air/list-filter-validation branch from de3d528 to 038b845 Compare November 12, 2026 20:03
@caroline-db caroline-db changed the title air: validate list filters and support full accelerator types air: validate list filters and support accelerator aliases Nov 12, 2026

@pardis-beikzadeh-db pardis-beikzadeh-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, nits below. Separately, could you file a follow-up for this? air list returns filter errors as plain text even with -o json, while air logs returns a JSON INVALID_ARGS error. That predates this PR, but this PR adds more of these errors.

@@ -0,0 +1 @@
* Support workspace accelerator families, display names, and full types in `air list` filters, and reject invalid filter values. ([#7515](https://github.com/databricks/cli/pull/7515))

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.

The accelerator filter now matches exactly instead of by substring, so accelerator_type=H1 used to match and now errors. Worth saying that here and in the description, since scripts may rely on the old behavior.

Comment thread cmd/air/list_filter.go Outdated
if !ok || key == "" {
return listFilters{}, fmt.Errorf("invalid --filter %q: expected KEY=VALUE", item)
}
if strings.TrimSpace(value) == "" {

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: (1) This runs before the key switch, so --filter acclerator_type= reports "value cannot be empty" instead of "unsupported key". (2) Surrounding whitespace isn't trimmed, so user= me@example.com quietly matches nothing, the empty-result case this PR fixes. Trim value once at the top, and check the key first?

Comment thread cmd/air/list_filter.go Outdated
return listFilters{}, fmt.Errorf("invalid --filter %q: expected KEY=VALUE", item)
}
if strings.TrimSpace(value) == "" {
return listFilters{}, fmt.Errorf("invalid --filter %s: value cannot be empty", key)

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: this one reads invalid --filter KEY: …, but the others read invalid --filter KEY="value": …. Use one format?

@caroline-db caroline-db changed the title air: validate list filters and support accelerator aliases air: validate list filters and support full accelerator types Nov 12, 2026
@caroline-db
caroline-db force-pushed the air/list-filter-validation branch from 3645a5f to b2b3c80 Compare November 12, 2026 22:30
@caroline-db
caroline-db added this pull request to the merge queue Nov 13, 2026
Merged via the queue into main with commit a80bc97 Nov 13, 2026
28 checks passed
@caroline-db
caroline-db deleted the air/list-filter-validation branch November 13, 2026 03:54
@eng-dev-ecosystem-bot

Copy link
Copy Markdown
Collaborator

❌ Integration test report

Commit: a80bc97

Run: 43362097454

Env ❌​FAIL 🟨​KNOWN 💚​RECOVERED ✅​pass 🙈​skip Time
❌​ aws linux-2core-8gb 39 1 11 1512 1289 125:25
❌​ aws-windows-latest-4core-16gb 39 3 9 1431 1316 145:36
❌​ azure linux-2core-8gb 39 1 11 1492 1297 115:17
❌​ azure-windows-latest-4core-16gb 39 1 11 1411 1324 128:14
❌​ gcp linux-2core-8gb 41 1 11 1497 1295 124:07
❌​ gcp-windows-latest-4core-16gb 41 1 11 1416 1322 141:23
55 interesting tests: 43 FAIL, 9 RECOVERED, 3 KNOWN
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 🟨​K 🟨​K 🟨​K 🟨​K 🟨​K 🟨​K
❌​ TestAccept/bundle/invariant/delete_idempotent ✅​p ✅​p ✅​p ✅​p ❌​F ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=vector_search_index.yml.tmpl/READPLAN= ✅​p ✅​p ✅​p ✅​p ❌​F ✅​p
💚​ TestAccept/bundle/resources/apps/lifecycle-started 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-omitted 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-omitted/DMS=true 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-toggle 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS= 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS=true 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started/DMS= 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started/DMS=true 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
❌​ TestAccept/bundle/resources/postgres_branches/update_protected ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_branches/update_protected/DMS= ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_branches/update_protected/DMS=true ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_branches/update_ttl ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_branches/update_ttl/DMS= ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_branches/update_ttl/DMS=true ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_databases/update ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_databases/update/DMS= ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_databases/update/DMS=true ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_endpoints/remove_suspend_timeout ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_endpoints/remove_suspend_timeout/DMS= ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_endpoints/remove_suspend_timeout/DMS=true ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_endpoints/update_autoscaling ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_endpoints/update_autoscaling/DMS= ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_endpoints/update_autoscaling/DMS=true ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_endpoints/update_pg_settings ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_endpoints/update_pg_settings/DMS= ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_endpoints/update_pg_settings/DMS=true ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_endpoints/update_suspend_timeout ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_endpoints/update_suspend_timeout/DMS= ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_endpoints/update_suspend_timeout/DMS=true ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_projects/add_default_endpoint_settings ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_projects/add_default_endpoint_settings/DMS= ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_projects/add_default_endpoint_settings/DMS=true ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_projects/remove_history_retention ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_projects/remove_history_retention/DMS= ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_projects/remove_history_retention/DMS=true ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_projects/update_default_endpoint_suspend ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_projects/update_default_endpoint_suspend/DMS= ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_projects/update_default_endpoint_suspend/DMS=true ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_projects/update_display_name ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_projects/update_display_name/DMS= ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_projects/update_display_name/DMS=true ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_projects/update_history_retention ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_projects/update_history_retention/DMS= ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_projects/update_history_retention/DMS=true ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_roles/recreate-postgres-role ✅​p ✅​p ✅​p ✅​p ✅​p ❌​F
❌​ TestAccept/bundle/resources/postgres_roles/recreate-postgres-role/DMS= ✅​p ✅​p ✅​p ✅​p ✅​p ❌​F
❌​ TestAccept/bundle/resources/postgres_roles/update ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_roles/update/DMS= ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/resources/postgres_roles/update/DMS=true ❌​F ❌​F ❌​F ❌​F ❌​F ❌​F
🟨​ TestAccept/bundle/resources/postgres_synced_tables/recreate 💚​R 🟨​K 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/postgres_synced_tables/recreate/DMS= 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
🟨​ TestAccept/bundle/resources/postgres_synced_tables/recreate/DMS=true 💚​R 🟨​K 💚​R 💚​R 💚​R 💚​R
Top 50 slowest tests (at least 2 minutes):
duration env testname
10:26 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
9:28 aws-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
9:00 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
8:58 aws-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
8:54 aws-windows-latest-4core-16gb TestAccept/bundle/deploy/spark-jar-task/DMS=true
8:54 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
8:52 aws-windows-latest-4core-16gb TestAccept/bundle/deploy/spark-jar-task/DMS=
8:42 azure-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
8:31 azure-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
8:28 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
7:49 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=true
7:46 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
7:15 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=true
7:02 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=
6:53 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=
6:48 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
6:48 gcp linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=
6:46 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
6:44 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
6:44 azure linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
6:40 azure linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=
6:32 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
6:30 aws linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=
6:15 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
6:12 aws linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
6:09 gcp linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
6:06 gcp linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
5:57 gcp linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
5:49 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
5:43 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
5:40 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
5:31 azure linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
5:28 aws linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
5:26 azure-windows-latest-4core-16gb TestAccept/pipelines/run/refresh-flags
5:17 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
5:14 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
5:09 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
5:09 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
5:07 aws linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
5:01 azure-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
4:55 azure linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
4:52 azure-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
4:50 azure linux-2core-8gb TestAccept/pipelines/run/refresh-flags
4:35 gcp-windows-latest-4core-16gb TestAccept/bundle/deploy/spark-jar-task/DMS=true
4:34 gcp linux-2core-8gb TestAccept/bundle/deploy/spark-jar-task/DMS=true
4:31 gcp-windows-latest-4core-16gb TestAccept/pipelines/run/refresh-flags
4:21 gcp linux-2core-8gb TestAccept/pipelines/run/refresh-flags
4:20 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
4:18 azure linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
4:13 azure-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS=true

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

Labels

AIR Databricks AI Runtime CLI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants