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

Add arch info in missing framework error #57150

Merged
merged 2 commits into from
Aug 12, 2021
Merged

Conversation

mateoatr
Copy link
Contributor

Adds the architecture information for missing framework errors.

@ghost
Copy link

ghost commented Aug 10, 2021

Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov
See info in area-owners.md if you want to be subscribed.

Issue Details

Adds the architecture information for missing framework errors.

Author: mateoatr
Assignees: -
Labels:

area-Host

Milestone: -

string expectedUrlQuery;
string expectedUrlParameter = null;
string expectedStdErr = null;
int expectedErrorCode = 0;
Copy link
Member

Choose a reason for hiding this comment

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

Any reason this variable moved down?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There was no particular reason for moving the declaration order I can change it back. The variable was declared but nothing in the test was checking that the actual exit code was the one expected.

.Should().Fail()
.And.HaveStdErrContaining($"- https://aka.ms/dotnet-core-applaunch?{expectedUrlQuery}")
.And.HaveStdErrContaining(expectedStdErr)
.And.ExitWith(expectedErrorCode);
Copy link
Member

Choose a reason for hiding this comment

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

I don't think this will work properly on some (Unix) systems where the exit codes are 0-255

string expectedUrlQuery;
string expectedUrlParameter = null;
string expectedStdErr = null;
Copy link
Member

Choose a reason for hiding this comment

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

Can you also change the name of this test ErrorReportedInDialog -> ErrorReportedInStdErr?

@agocke
Copy link
Member

agocke commented Aug 11, 2021

While we're here, can we also include the version in the download URL?

Something like {url}?version=...&arch=...&os=...?

@mateoatr
Copy link
Contributor Author

While we're here, can we also include the version in the download URL?

Something like {url}?version=...&arch=...&os=...?

We already put the framework version on the URL, is this something different? A URL example would be: https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=6.0.0-ci&arch=x64&rid=centos.7-x64.

@agocke
Copy link
Member

agocke commented Aug 11, 2021

Nope that should be good enough. I just wanted to make sure we had some information that the site could use to narrow down the needed runtime.

Do we have that for the case where there is no runtime, or only when there's a missing framework?

@mateoatr
Copy link
Contributor Author

Yes. For missing runtime we put the arch, the rid and the apphost version. E.g., https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=win10-x64&apphost_version=6.0.0

@mateoatr mateoatr merged commit e06ef79 into dotnet:main Aug 12, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Sep 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants