-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add dotnet package update command #49287
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Azure DevOps' test view on the CI build isn't showing the failed test, but looking at the Helix console log, I see this, but only on Windows, so I think the test is passing on Linux and Mac:
Reforatting the diff: '-r=[The target runtime to run for.]:RUNTIME_IDENTIFIER:->dotnet_dynamic_complete' \
- '--project=[The path to the project file to run (defaults to the current directory if there is only one project).]: : ' \
- '--launch-profile=[The name of the launch profile (if any) to use when launching the application.]: : ' \
- '-lp=[The name of the launch profile (if any) to use when launching the application.]: : ' \
+ '--project=[The path to the project file to run (defaults to the current directory if there is only one project).]:project: ' \
+ '--launch-profile=[The name of the launch profile (if any) to use when launching the application.]:launch-profile: ' \
+ '-lp=[The name of the launch profile (if any) to use when launching the application.]:launch-profile: ' \
'--no-launch-profile[Do not attempt to use launchSettings.json to configure the application.]' \ However, we can see that this pull request is not modifying lines 846 to 850. Additionally, when I run the test locally, I can't reproduce the failure, but this test keeps failing on CI, even after multiple retries. Any ideas, @baronfel ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we've got a known issue for this specifically - several of us have hit this same issue. I have no rationale for why this happens. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sorry, I didn't think to search for a known issue first: |
Uh oh!
There was an error while loading. Please reload this page.