Skip to content

Install a .NET 6 runtime for the MSBuild Workspace unit tests.#63369

Merged
JoeRobich merged 3 commits intomainfrom
dev/jorobich/fix-single-machine
Aug 15, 2022
Merged

Install a .NET 6 runtime for the MSBuild Workspace unit tests.#63369
JoeRobich merged 3 commits intomainfrom
dev/jorobich/fix-single-machine

Conversation

@JoeRobich
Copy link
Copy Markdown
Member

@JoeRobich JoeRobich commented Aug 12, 2022

@ghost ghost added the Area-Infrastructure label Aug 12, 2022
@dibarbet

This comment was marked as off-topic.

@azure-pipelines

This comment was marked as off-topic.

1 similar comment
@azure-pipelines

This comment was marked as off-topic.

@JoeRobich JoeRobich requested a review from a team as a code owner August 12, 2022 23:30
steps:
- checkout: none

# A .NET 6 runtime is needed since our unit tests target net6.0
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Should we just be upgrading to something newer here?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

We could update our tests to target net7.0, but that seems like a more disruptive change. In the scheme of things the SingleMachine CI jobs aren't strictly necessary and may not be providing value over the Helix CI. They were mainly intended to ensure our infra changes didn't break the ability to run tests locally.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

FWIW i was chatting with @dibarbet about this the other day.

They were mainly intended to ensure our infra changes didn't break the ability to run tests locally.

Exactly. More broadly it was to make sure that we had some sanity check in place to make sure people could develop locally: build, test and run. We lost that to a large extent when we moved to Helix. The single machine tests exists to make sure we can develop locally.

That means we don't even need to run all tests here. We just need to run enough that we're convinced we haven't broken things.

@JoeRobich JoeRobich merged commit 24eacfa into main Aug 15, 2022
@ghost ghost added this to the Next milestone Aug 15, 2022
@dibarbet dibarbet modified the milestones: Next, 17.4 P2 Sep 1, 2022
@JoeRobich JoeRobich deleted the dev/jorobich/fix-single-machine branch September 2, 2022 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants