Skip to content

aitools: keep installing plugins when the skills install fails - #7479

Merged
anton-107 merged 1 commit into
mainfrom
aitools/skills-failure-keeps-plugins
Nov 13, 2026
Merged

anton-107 merged 1 commit into
mainfrom
aitools/skills-failure-keeps-plugins

Conversation

@anton-107

@anton-107 anton-107 commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Stacked on #7478.

Stacked on: aitools: drop the Proceed? confirm after the agent picker in install

Summary

databricks aitools install no longer stops when installing skill files fails. Agents that get a plugin (Claude Code) don't depend on the skill files, so their plugin is still installed. The skills error is still the command's error. The plugin is recorded in the install state without advancing state.Release, because the skill files on disk are still at the old release; otherwise aitools version and a pinned aitools update would report them as up to date. If the global scope has skills on disk but no state file (an install that predates state tracking, or an interrupted first install), the plugin is not recorded at all, so aitools update and the install's legacy checks still see those skills.

 executePlan
   install skills for skills agents
-    on error: return error            # plugin agents never attempted
+    on error: remember skillsErr
   install plugins for plugin agents
-    on state write error: return err
+    on state write error: return errors.Join(skillsErr, err)
+    record plugins; if skillsErr, keep state.Release   # skills on disk are still at the old release
+    if skillsErr and untracked legacy skills on disk: don't create a plugin-only state file
+  if skillsErr: return skillsErr      # stays the top-level error
   if per-agent errors: return agentErrors

Changelog fragment: .nextchanges/cli/aitools-install-skills-failure-keeps-plugins.md.

Evidence

New test TestExecutePlanSkillsFailureStillInstallsPlugins (cmd/aitools/install_test.go): plan with Cursor (skills) and Claude Code (plugin), skills install returns an HTTP 503 manifest fetch error. Run with go test ./cmd/aitools -run TestExecutePlanSkillsFailureStillInstallsPlugins.

  • Before (cmd/aitools/install.go reverted to the parent): fails, no plugin is installed.
    install_test.go:301: "[]" should have 1 item(s), but has 0
    FAIL	github.com/databricks/cli/cmd/aitools
    
    After: passes. The error is still the fetch error (errors.Is), one plugin install is made, Claude Code's outcome is installed, and the saved state records the plugin while Release stays at the earlier v0.2.5.

New test TestExecutePlanSkillsAndStateWriteFailuresAreJoined: the skills install and the state write both fail. The returned error joins both (skills first), and its category is STATE_INVALID, because classifyInstallError ranks errors by type.

New test TestExecutePlanSkillsFailureKeepsUntrackedSkillsVisible: legacy skills on disk with no state file, and the skills install fails. The plugin is installed, but no state file is created, so HasUntrackedSkills (the signal aitools update and the install's legacy checks rely on) is still true. Without the guard, a plugin-only state file is written and the test fails.

Merge Danger

Door: two-way

Revert the commit to bring the old behavior back. Nothing is migrated. After a skills failure the state file now gets the plugin record (with Release unchanged), where before nothing was written. The exception is a global scope with skills on disk and no state file: there nothing is written, and the plugin is recorded by the next install whose skills step succeeds.

Blast Radius: small

  • The exit code doesn't change: a skills failure still fails the command with the same error. If the plugin step later also fails on writing the state, both errors are joined.
  • After a skills failure the command now keeps going and runs the plugin install, so the user waits for that work (and its network calls) before the command exits.
  • Only covered by unit tests with stubbed installers. Not run on Windows or macOS.

This pull request and its description were written by Isaac.

@anton-107
anton-107 requested review from a team and lennartkats-db as code owners November 11, 2026 14:27
@anton-107 anton-107 added the ai-auto PRs made by AI loops & factories, label Nov 11, 2026
@anton-107
anton-107 requested a review from a team as a code owner November 11, 2026 14:27
@anton-107
anton-107 requested a review from misha-db November 11, 2026 14:27
@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from 7c162ba to 593c4fe Compare November 11, 2026 14:34
@anton-107
anton-107 requested a review from a team as a code owner November 11, 2026 14:34
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from 891a0e3 to e15f2f9 Compare November 11, 2026 14:34
@eng-dev-ecosystem-bot

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

Copy link
Copy Markdown
Collaborator

✅ Integration test report

Commit: fbf8382

Run: 43219629804

Env 🔄​flaky 💚​RECOVERED ✅​pass 🙈​skip Time
💚​ aws linux-2core-8gb 1 270 27 16:19
💚​ aws-windows-latest-4core-16gb 1 272 25 11:14
💚​ azure linux-2core-8gb 1 269 27 16:29
🔄​ azure-windows-latest-4core-16gb 1 1 270 25 11:31
💚​ gcp linux-2core-8gb 1 270 27 17:08
🔄​ gcp-windows-latest-4core-16gb 1 1 271 25 15:15
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
🔄​ TestSyncFullFileSync ✅​p ✅​p ✅​p 🔄​f ✅​p ✅​p
🔄​ TestSyncIncrementalFileSync ✅​p ✅​p ✅​p ✅​p ✅​p 🔄​f
Top 25 slowest tests (at least 2 minutes):
duration env testname
3:54 azure linux-2core-8gb TestAccept
3:54 aws linux-2core-8gb TestAccept
3:52 gcp linux-2core-8gb TestAccept
3:46 aws-windows-latest-4core-16gb TestAccept
3:42 azure-windows-latest-4core-16gb TestAccept
3:36 gcp-windows-latest-4core-16gb TestAccept
3:00 aws-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsRead
2:55 gcp linux-2core-8gb TestLock
2:52 gcp-windows-latest-4core-16gb TestFsCpFileToDirFileNotOverwritten/dbfs_to_dbfs
2:32 azure linux-2core-8gb TestFilerWorkspaceFilesExtensionsStat
2:30 gcp-windows-latest-4core-16gb TestImportDirDoesNotOverwrite
2:30 azure linux-2core-8gb TestExportDir
2:23 gcp linux-2core-8gb TestFilerWorkspaceFilesExtensionsReadDir
2:22 gcp-windows-latest-4core-16gb TestImportDirWithOverwriteFlag
2:18 gcp-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsStat
2:15 azure-windows-latest-4core-16gb TestImportDirDoesNotOverwrite
2:15 gcp linux-2core-8gb TestFsCpDir/dbfs_to_dbfs
2:14 gcp-windows-latest-4core-16gb TestFsRmDirRecursively/dbfs
2:14 gcp linux-2core-8gb TestFsCpDirToDirWithOverwriteFlag/dbfs_to_dbfs
2:11 azure-windows-latest-4core-16gb TestFilerRecursiveDelete/dbfs
2:10 aws linux-2core-8gb TestFilerRecursiveDelete/workspace_files_extensions
2:09 aws-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsReadDir
2:09 gcp linux-2core-8gb TestFsCpDirToDirFileNotOverwritten/dbfs_to_local
2:07 gcp linux-2core-8gb TestFilerRecursiveDelete/dbfs
2:06 gcp linux-2core-8gb TestFsCpDirToDirFileNotOverwritten/dbfs_to_dbfs

@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from 593c4fe to deca41f Compare November 11, 2026 16:53
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from e15f2f9 to 0fb3e5c Compare November 11, 2026 16:53
@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from deca41f to e980d56 Compare November 11, 2026 16:55
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from 0fb3e5c to 520f504 Compare November 11, 2026 16:55
@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from e980d56 to e155c53 Compare November 11, 2026 16:57
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from 520f504 to 6709c89 Compare November 11, 2026 16:57
@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from e155c53 to a791ac7 Compare November 11, 2026 19:34
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from 6709c89 to e7d2703 Compare November 11, 2026 19:34
@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from a791ac7 to a45b450 Compare November 11, 2026 19:42
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch 2 times, most recently from 912057b to 5f9958b Compare November 11, 2026 20:03
@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from a45b450 to eb589c2 Compare November 11, 2026 20:07
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from 5f9958b to 6f53d25 Compare November 11, 2026 20:07
@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from eb589c2 to df49877 Compare November 11, 2026 21:04
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from 6f53d25 to bced029 Compare November 11, 2026 21:04

@simonfaltum simonfaltum left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

🤖 Automated review from simonfaltum's review agent (pr-review skill) at bced029. Each finding was verified against the code; simonfaltum may follow up.

Not approving yet: part of the automated review did not complete.

This PR lets databricks aitools install keep installing plugins for plugin agents such as Claude Code when the skills-group install fails, and still returns the skills error as the command's error. The change is small, focused and green in CI. One non-blocking issue: after a skills failure, recording the plugin now advances the shared state.Release, so aitools version and, with a pinned ref, aitools update can report stale skills as up to date. The other comments are small nits: tests for the joined-error paths, a stale test comment, and the changelog wording.

Comments outside the changed lines

  • [nit] cmd/aitools/install_test.go:531: This comment says the skills-group path "returns before appending any per-agent outcome", but this PR removed that early return. The test still passes because a Cursor-only plan has no plugin items. Suggest rewording it, for example: "Cursor is skills-only, so this fails in the skills-group path, which records no per-agent outcome."

Comment thread cmd/aitools/install.go Outdated
@@ -630,7 +631,7 @@ func executePlan(ctx context.Context, src installer.ManifestSource, plan []agent
}
if len(records) > 0 {
if err := recordPluginInstallsFn(ctx, opts.Scope, records, ref); err != nil {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

[nice to have] Now that the plugin step runs after a skills failure, RecordPluginInstalls (libs/aitools/installer/plugin.go:487) still sets state.Release to the new ref, even though InstallSkillsForAgents returned before it saved state. The skills on disk and in state.Skills stay at the old release. Example: Cursor's skills are at v0.2.5, a v0.2.6 install fails during the skills fetch, and the Claude Code plugin is recorded. The state then says v0.2.6, aitools version reports "up to date" (cmd/aitools/version.go:132), and with a pinned ref (cli-compat pin or DATABRICKS_SKILLS_REF) aitools update stops at explicit && state.Release == latestTag (libs/aitools/installer/update.go:101) and prints "Already up to date." without updating Cursor's skills. Before this PR, the early return meant nothing was written after a skills failure. Suggest leaving Release unchanged when recording plugins after a skills failure (for example a flag or a separate record call), and adding a test that checks the saved state after the mixed failure.

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.

Fixed. When the skills install failed, executePlan now records the plugins with an empty ref, and RecordPluginInstalls leaves state.Release unchanged for an empty ref (doc comment updated). TestExecutePlanSkillsFailureStillInstallsPlugins now runs the real RecordPluginInstalls against a temp HOME seeded with a v0.2.5 state, and checks that the saved state has the Claude Code plugin and Release still v0.2.5. Without the fix the test gets v0.2.6. A fresh install whose skills step fails gets Release empty, which matches having no skills installed.

Commit: cad6ebe

Comment thread cmd/aitools/install.go Outdated
ref, err := installer.GetPluginSkillsRef(ctx)
if err != nil {
return outcomes, err
return outcomes, errors.Join(skillsErr, err)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

[nit] The new errors.Join(skillsErr, err) returns (ref lookup here, state write at L634) have no tests. No test stubs recordPluginInstallsFn to fail, and the new test pins DATABRICKS_SKILLS_REF, so the ref lookup always succeeds. A case where the skills install and recordPluginInstallsFn both fail would pin down the joined message and the category picked for it. classifyInstallError ranks errors by type, not by order, so a typed plugin-side error such as StateError can outrank an untyped skills error.

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.

Added TestExecutePlanSkillsAndStateWriteFailuresAreJoined: an untyped skills error, and recordPluginInstallsFn returning a StateError. It pins the joined message (skills error first, then the state error), errors.Is for both, and the category STATE_INVALID, so the type ranking you describe is now explicit in a test. I didn't add a separate test for the ref-lookup path: it uses the same errors.Join(skillsErr, err) return, and making GetPluginSkillsRef fail would mean adding a new seam just for this test.

Commit: cad6ebe

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.

Update after rebasing onto the current #7478: the ref-lookup failure no longer returns an error there (the plugin version is recorded as unknown), so the only joined-error path left is the state write, and TestExecutePlanSkillsAndStateWriteFailuresAreJoined covers it. PR description updated to match.

Commit: 4f38e11

@@ -0,0 +1 @@
* `databricks aitools install` still installs plugins for the other coding agents when installing skill files fails. ([#7479](https://github.com/databricks/cli/pull/7479))

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

[nit] The pr-checklist (.agents/skills/pr-checklist/SKILL.md:75) asks for an imperative verb, or the command in the present tense with "now". "still installs" reads as if the behavior didn't change. Suggest: "* databricks aitools install now installs plugins for the other coding agents even when installing skill files fails. (#7479)"

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.

Applied your wording, PR link kept: "databricks aitools install now installs plugins for the other coding agents even when installing skill files fails."

Commit: cad6ebe

@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from bced029 to cad6ebe Compare November 11, 2026 22:09
@anton-107

Copy link
Copy Markdown
Contributor Author

Outside-diff nit on cmd/aitools/install_test.go:531: reworded the comment to "Cursor is skills-only, so this fails in the skills-group path, which records no per-agent outcome." In the same commit: state.Release is no longer advanced after a skills failure, and there's a new joined-error test (details in the inline threads). The PR description is updated to match.

Commit: cad6ebe

@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from 942cec5 to ddd4225 Compare November 12, 2026 09:00
@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from efae3db to 6aa9729 Compare November 12, 2026 09:06
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from ddd4225 to 45b26f8 Compare November 12, 2026 09:06
@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch 2 times, most recently from f5bf3ea to ac0065e Compare November 12, 2026 09:19
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from 45b26f8 to a3e42ce Compare November 12, 2026 09:30
@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from ac0065e to 2a658e6 Compare November 12, 2026 10:01
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from a3e42ce to cad677d Compare November 12, 2026 10:01
@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from 2a658e6 to 51b22e3 Compare November 12, 2026 11:02
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from cad677d to 2adef03 Compare November 12, 2026 11:02

@rugpanov rugpanov 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.

cmd/aitools/install.go:761: [nit] This comment says that without the top-level error, the consumer sees "an empty agents array". After this PR, the array can hold the plugin agents next to a top-level skills error. Update this comment, and the similar one in install_test.go:721.

Comment thread cmd/aitools/install.go
releaseRef = ""
}
if err := recordPluginInstallsFn(ctx, opts.Scope, records, releaseRef); err != nil {
return outcomes, errors.Join(skillsErr, err)

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.

[nice to have] Skill files and plugin records share one state file per scope. When the skills install fails because that state file cannot be read or parsed, the plugin step still runs marketplace add and plugin install. Then this call fails on the same state file. The plugin is installed but not recorded, so update and uninstall do not manage it, and the JSON output reports it as installed. Before this PR, such a run changed nothing. Go on to the plugins only when the skills step failed on a fetch (*installer.FetchError). Add a test that does not stub recordPluginInstallsFn. In the legacy case at line 668 the plugin is also left unrecorded, on purpose, but only a debug log says so. Print a warning there that tells the user to re-run databricks aitools install.

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.

Agreed, both parts are real gaps. This PR is already approved with the current behavior, so I'd like to handle them in a follow-up instead of changing the gate here:

  • Go on to the plugin step only when the skills step failed on a fetch (*installer.FetchError). That way an unreadable or invalid state file stops the run before marketplace add / plugin install. Add a test that runs the real RecordPluginInstalls.
  • Print a warning in the untracked-skills branch that tells the user to re-run databricks aitools install, instead of only a debug log.

For now, in the state-file case the command still fails: the returned error joins the skills error and the state error.

// such installs. A state file that can't be read counts as no: the caller's
// next state load reports that error itself.
func HasUntrackedSkills(ctx context.Context, cliScope string) bool {
if cliScope != ScopeGlobal {

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 returns false for project scope, because "Project scope never had such installs". But InstallSkillsForAgents saves the state only after its loop, so a first project install that fails on the third skill leaves two skills on disk with no state. Then executePlan records the plugins, and the new project state has no skills. update treats that scope as plugin-only, and uninstall leaves those skill files. Check the project dir for skills without state too, and say in the doc that an interrupted install also leaves untracked skills.

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.

Updated the doc comment: it now says the check covers skills on disk with no state file from either an install that predates state tracking or a first install that failed before saving state. It also says only the global scope is checked, so an interrupted first project install isn't detected. I also aligned the comment at the call site in install.go.

I left the project-scope check itself for a follow-up. It changes when plugins get recorded in project scope, and this PR is already approved with the global-only behavior.

Commit: 1eca02f

@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from 51b22e3 to a4c1544 Compare November 12, 2026 12:28
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from 2adef03 to b9488bb Compare November 12, 2026 12:28
@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from a4c1544 to c635c52 Compare November 12, 2026 12:30
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from b9488bb to 3e7a5e5 Compare November 12, 2026 12:30
@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from c635c52 to b09a485 Compare November 12, 2026 12:31
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from 3e7a5e5 to 916c212 Compare November 12, 2026 12:31
@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from b09a485 to 2ee6302 Compare November 12, 2026 12:32
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from 916c212 to b6d9a96 Compare November 12, 2026 12:32
@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from 2ee6302 to d105006 Compare November 12, 2026 12:34
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch 2 times, most recently from 838c303 to 1eca02f Compare November 12, 2026 12:36
@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from d105006 to 924919a Compare November 12, 2026 12:36
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from 1eca02f to fbf8382 Compare November 12, 2026 12:36
@anton-107

Copy link
Copy Markdown
Contributor Author

Fixed both comments. The install.go one now says that without the top-level error the consumer sees a non-zero exit with no reason, and that the agents array holds at most the plugin agents that were still installed. The test comment in install_test.go now says the agents array is empty there only because the plan has no plugin agent.

Commit: 1eca02f

@anton-107
anton-107 force-pushed the aitools/drop-proceed-confirm branch from 924919a to 05df0d0 Compare November 12, 2026 12:37
@anton-107
anton-107 force-pushed the aitools/skills-failure-keeps-plugins branch from fbf8382 to f3ea264 Compare November 12, 2026 12:37
`databricks aitools install` no longer stops when installing skill files fails. Agents that get a plugin (Claude Code) don't depend on the skill files, so their plugin is still installed. The skills error is still the command's error. The plugin is recorded in the install state without advancing `state.Release`, because the skill files on disk are still at the old release; otherwise `aitools version` and a pinned `aitools update` would report them as up to date. If skills from an install that predates state tracking are on disk with no state file, the plugin is not recorded at all, so `aitools update` and the install's legacy checks still see those skills.

```diff
 executePlan
   install skills for skills agents
-    on error: return error            # plugin agents never attempted
+    on error: remember skillsErr
   install plugins for plugin agents
-    on state write error: return err
+    on state write error: return errors.Join(skillsErr, err)
+    record plugins; if skillsErr, keep state.Release   # skills on disk are still at the old release
+    if skillsErr and untracked legacy skills on disk: don't create a plugin-only state file
+  if skillsErr: return skillsErr      # stays the top-level error
   if per-agent errors: return agentErrors
```

Changelog fragment: `.nextchanges/cli/aitools-install-skills-failure-keeps-plugins.md`.

Co-authored-by: Isaac <no-reply@databricks.com>
@eng-dev-ecosystem-bot

Copy link
Copy Markdown
Collaborator

❌ Integration test report

Commit: eee3c42

Run: 43376105763

Env ❌​FAIL 🟨​KNOWN 💚​RECOVERED ✅​pass 🙈​skip Time
❌​ aws linux-2core-8gb 39 1 11 1512 1289 187:03
❌​ aws-windows-latest-4core-16gb 39 1 11 1431 1316 222:46
❌​ azure linux-2core-8gb 39 1 11 1492 1297 169:47
❌​ azure-windows-latest-4core-16gb 39 1 11 1411 1324 216:39
❌​ gcp linux-2core-8gb 39 1 11 1499 1295 192:37
❌​ gcp-windows-latest-4core-16gb 39 1 11 1418 1322 200:45
51 interesting tests: 39 FAIL, 11 RECOVERED, 1 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/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/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 💚​R 💚​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 💚​R 💚​R 💚​R 💚​R 💚​R
Top 50 slowest tests (at least 2 minutes):
duration env testname
11:22 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
9:54 aws-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
9:47 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
9:17 azure-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
9:03 aws-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
9:00 azure-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
8:58 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
8:51 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
8:48 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
8:34 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
8:10 azure-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
8:08 gcp linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
8:06 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=true
7:35 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
7:32 aws linux-2core-8gb TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN=1
7:25 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
7:19 aws linux-2core-8gb TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN=
7:17 aws linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
7:09 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
7:04 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/resize-terminated-fallback/DMS=true
7:00 aws linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
6:59 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/resize-terminated-fallback/DMS=
6:58 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=true
6:57 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:51 aws linux-2core-8gb TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN=1
6:49 aws linux-2core-8gb TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN=
6:49 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
6:48 azure linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
6:48 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
6:47 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
6:46 gcp linux-2core-8gb TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN=1
6:37 gcp linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=
6:25 gcp linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
6:22 azure-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
6:19 gcp linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
5:55 aws-windows-latest-4core-16gb TestAccept/pipelines/run/refresh-flags
5:46 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
5:32 azure linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
5:29 aws linux-2core-8gb TestAccept/bundle/deploy/spark-jar-task/DMS=
5:28 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
5:27 aws-windows-latest-4core-16gb TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN=1
5:27 gcp linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
5:26 aws linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
5:17 aws linux-2core-8gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
5:12 azure-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
5:11 aws linux-2core-8gb TestAccept/bundle/deploy/spark-jar-task/DMS=true
5:11 aws-windows-latest-4core-16gb TestAccept/bundle/deploy/spark-jar-task/DMS=true
5:10 gcp linux-2core-8gb TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster.yml.tmpl/READPLAN=1
5:08 azure-windows-latest-4core-16gb TestAccept/pipelines/run/refresh-flags

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

Labels

ai-auto PRs made by AI loops & factories,

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants