-
Notifications
You must be signed in to change notification settings - Fork 682
Rebuild Azure Functions project before test run #7748
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
Conversation
366f1f7
to
26b35a6
Compare
26b35a6
to
6750b76
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (2)
.github/workflows/tests.yml:191
- Verify that the condition 'matrix.name == "Playground"' correctly identifies the Azure Functions project. If the matrix contains multiple project types, consider a more robust condition to prevent unintended builds.
+ if: matrix.name == 'Playground'
tests/Aspire.Playground.Tests/ProjectSpecificTests.cs:59
- Confirm that the removal of the ActiveIssue attribute is intentional and that the test now reliably passes. Remove the attribute only after ensuring the underlying issue has been fully resolved.
- [ActiveIssue("https://github.com/dotnet/aspire/issues/7437")]
Can we add the explanation of the problem, and the workaround being used here to the PR description? I'm guessing that it would be essentially what you said in #7437 (comment) . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assuming the tests pass. LGTM.
Addresses #7437 by rebuilding the Functions project again after the build of test projects to force resolution of trigger metadata correctly before the Functions test runs.
This is a workaround for Azure/azure-functions-dotnet-worker#2969.