Flaky test: Test_summaryModel/Result:_Confirm

[rynowak]

Steps to reproduce

See logs: https://github.com/radius-project/radius/actions/runs/11768735276/job/32778890465?pr=8038

Observed behavior

=== FAIL: pkg/cli/cmd/radinit Test_summaryModel/Result:_Confirm (0.05s)
    --- FAIL: Test_summaryModel/Result:_Confirm (0.05s)
panic: interface conversion: tea.Model is nil, not *radinit.summaryModel [recovered]
	panic: interface conversion: tea.Model is nil, not *radinit.summaryModel

goroutine 75 [running]:
testing.tRunner.func1.2({0x463d200, 0xc0004645a0})
	/home/runner/go/pkg/mod/golang.org/[email protected]/src/testing/testing.go:1632 +0x3fc
testing.tRunner.func1()
	/home/runner/go/pkg/mod/golang.org/[email protected]/src/testing/testing.go:1635 +0x6b6
panic({0x463d200?, 0xc0004645a0?})
	/home/runner/go/pkg/mod/golang.org/[email protected]/src/runtime/panic.go:785 +0x132
github.com/radius-project/radius/pkg/cli/cmd/radinit.Test_summaryModel.func3(0xc00063b040, {0x49ddd06, 0x9}, 0xd)
	/home/runner/work/radius/radius/pkg/cli/cmd/radinit/display_test.go:73 +0x518
github.com/radius-project/radius/pkg/cli/cmd/radinit.Test_summaryModel.func4(0xc00063b040)
	/home/runner/work/radius/radius/pkg/cli/cmd/radinit/display_test.go:78 +0x49
testing.tRunner(0xc00063b040, 0xc000651c30)
	/home/runner/go/pkg/mod/golang.org/[email protected]/src/testing/testing.go:1690 +0x227
created by testing.(*T).Run in goroutine 74
	/home/runner/go/pkg/mod/golang.org/[email protected]/src/testing/testing.go:1743 +0x826

=== FAIL: pkg/cli/cmd/radinit Test_summaryModel (0.05s)

Desired behavior

Test passes reliably.

Workaround

No response

rad Version

This shouldn't be a required field.

Operating system

No response

Additional context

No response

Would you like to support us?

• Yes, I would like to support you

AB#13669

[radius-triage-bot]

👋 @rynowak Thanks for filing this bug report.

A project maintainer will review this report and get back to you soon. If you'd like immediate help troubleshooting, please visit our Discord server.

For more information on our triage process please visit our triage overview

[radius-triage-bot]

👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

[ytimocin]

On-call will start working on this. On-call can hand it off to the next on-call but then if the issue is still not resolved it should go into the sprint planning.

[rynowak]

We should probably start with logging a bug on the upstream project. All of our tests that cover bubbletea have failed at one point or another. It's probably a data-race in their testing framework.