Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

flaky CommunityToolkit.Aspire.Hosting.Azure.StaticWebApps.Tests.SwaHostingComponentTests.CanAccessFrontendSuccessfully #157

Closed
Alirexaa opened this issue Oct 25, 2024 · 1 comment · Fixed by #165
Assignees

Comments

@Alirexaa
Copy link
Member

build: https://github.com/CommunityToolkit/Aspire/actions/runs/11509898723/job/32040808825

test-results-windows-latest.zip

[xUnit.net 00:01:25.84]     CommunityToolkit.Aspire.Hosting.Azure.StaticWebApps.Tests.SwaHostingComponentTests.CanAccessFrontendSuccessfully [FAIL]
  Failed CommunityToolkit.Aspire.Hosting.Azure.StaticWebApps.Tests.SwaHostingComponentTests.CanAccessFrontendSuccessfully [30 s]
  Error Message:
   System.TimeoutException : The operation has timed out.
  Stack Trace:
     at CommunityToolkit.Aspire.Hosting.Azure.StaticWebApps.Tests.SwaHostingComponentTests.CanAccessFrontendSuccessfully() in /_/tests/CommunityToolkit.Aspire.Hosting.Azure.StaticWebApps.Tests/SwaHostingComponentTests.cs:line 16
--- End of stack trace from previous location ---
Results File: D:\a\Aspire\Aspire\test-results\CommunityToolkit.Aspire.Hosting.Azure.StaticWebApps.Tests-net8.0.trx
@aaronpowell
Copy link
Member

Probably need to update the timeout window.

Hopefully #74 and/or #73 can solve it in a better way

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

Successfully merging a pull request may close this issue.

2 participants