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

Fix Test_Windows_CoreClr_Debug_Single_Machine job #60218

Closed
RikkiGibson opened this issue Mar 17, 2022 · 3 comments · Fixed by #60231
Closed

Fix Test_Windows_CoreClr_Debug_Single_Machine job #60218

RikkiGibson opened this issue Mar 17, 2022 · 3 comments · Fixed by #60231
Assignees
Labels
Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead

Comments

@RikkiGibson
Copy link
Contributor

RikkiGibson commented Mar 17, 2022

After #59903 was merged, all runs of 'Test_Windows_CoreClr_Debug_Single_Machine' started failing. We missed this since it only runs in rolling builds.

Example run

Also failing in #60207

  1. Let's fix the issue causing the job to fail.
  2. Let's introduce some method of reporting so that we know when breaks like this have been checked in.
@RikkiGibson RikkiGibson self-assigned this Mar 17, 2022
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead labels Mar 17, 2022
@JoeRobich
Copy link
Member

roslyn/eng/Versions.props

Lines 200 to 205 in bddc362

<!--
The package "Microsoft.CodeAnalysis.Analyzer.Testing" brings in an earlier version of these NuGet dependencies than
is expected by the NET SDK used in the Workspace.MSBuild UnitTests. In order to test against the same verion of NuGet
as our configured SDK, we must set the version to be the same.
-->
<NuGetCommonVersion>6.1.0</NuGetCommonVersion>

@JoeRobich
Copy link
Member

Updated the message fabric bot places on Arcade updates that change the pinned dotnet SDK version. It now includes a task list of things to update, including the NuGet version.

@JoeRobich
Copy link
Member

Let's introduce some method of reporting so that we know when breaks like this have been checked in.

I would love to know when two consecutive rolling builds of main have CI failures.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants