Skip to content

air: Show the experiment and accelerators in the air list info pane - #7598

Closed
dimk0 wants to merge 4 commits into
mainfrom
air-info-pane-experiment-accelerators
Closed

dimk0 wants to merge 4 commits into
mainfrom
air-info-pane-experiment-accelerators

Conversation

@dimk0

@dimk0 dimk0 commented Nov 13, 2026

Copy link
Copy Markdown
Member

Changes

The air list info pane (i) now fills the Experiment and Accelerators fields, and the Configuration box, from the run's ai_runtime_task, as air get already does. Before, the pane showed N/A for both on every run.

Why

Found while verifying #7582 in a real terminal against a workspace (internal ticket CNXT-2621): air get <run-id> showed a run's experiment and accelerators, but the info pane for the same run showed N/A. runDetailText built the pane from buildGetData alone and never called enrichFromAiRuntimeTask, which air get has used since the commands moved out of experimental.

Tests

  • New unit test TestInfoPaneShowsExperimentAndAcceleratorsLikeAirGet: fails on main, passes with the fix.
  • go test ./cmd/air, go test ./acceptance -run TestAccept/air, and golangci-lint on cmd/air pass.
  • Manually: built the CLI, opened the pane on a run in a staging workspace in a tmux terminal; it shows Experiment read-benchmark-…-v1 and Accelerators 8x H100 instead of N/A.

This PR was written by Claude Code.

This pull request and its description were written by Isaac.

The pane built its fields from the run alone and never called
enrichFromAiRuntimeTask, so Experiment and Accelerators were always N/A
while `air get` showed them for the same run.

Co-authored-by: Isaac <no-reply@databricks.com>
@dimk0
dimk0 requested review from a team as code owners November 13, 2026 09:51
@dimk0
dimk0 requested a review from anton-107 November 13, 2026 09:51
Co-authored-by: Isaac <no-reply@databricks.com>
@github-actions github-actions Bot added the AIR Databricks AI Runtime CLI label Nov 13, 2026
@eng-dev-ecosystem-bot

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

Copy link
Copy Markdown
Collaborator

✅ Integration test report

Commit: 26c8d91

Run: 43436323727

Env 🔄​flaky 💚​RECOVERED ✅​pass 🙈​skip Time
💚​ aws linux-2core-8gb 1 270 15 8:06
💚​ aws-windows-latest-4core-16gb 1 272 13 4:56
🔄​ azure linux-2core-8gb 2 1 267 15 10:33
💚​ azure-windows-latest-4core-16gb 1 271 13 5:10
💚​ gcp linux-2core-8gb 1 270 15 6:58
💚​ gcp-windows-latest-4core-16gb 1 272 13 4:11
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
🔄​ TestSyncIncrementalFileOverwritesFolder ✅​p ✅​p 🔄​f ✅​p ✅​p ✅​p
🔄​ TestSyncIncrementalSyncPythonNotebookToFile ✅​p ✅​p 🔄​f ✅​p ✅​p ✅​p
Top 3 slowest tests (at least 2 minutes):
duration env testname
3:40 azure linux-2core-8gb TestFilerRecursiveDelete/workspace_files
2:24 aws-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsDelete
2:04 aws-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsReadDir

Dima Kotlyarov and others added 2 commits November 13, 2026 13:14
Co-authored-by: Isaac <no-reply@databricks.com>
The fragment belongs to PR #7601's branch, not this one; here it fails
the changelog validator because its link does not include #7598.

This reverts commit 95e6c90.

Co-authored-by: Isaac <no-reply@databricks.com>
@caroline-db

Copy link
Copy Markdown
Contributor

This duplicates #7587, which predates this PR and has stronger coverage for the Configuration box. Can we close this one in favor of #7587?

@dimk0

dimk0 commented Nov 13, 2026

Copy link
Copy Markdown
Member Author

Agreed, this is a duplicate. #7587 (opened ~2h earlier for the same info-pane N/A problem) makes the same enrichFromAiRuntimeTask call in runDetailText, carries its own test, and is already approved. Closing in favor of #7587.

@dimk0 dimk0 closed this Nov 13, 2026
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.

3 participants