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.

Sign up for GitHub

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

Jump to bottom

Restore problems with 17.5.0-pre.1.0 version of windows.vs2022preview.scout.amd64.open #11707

Closed
MattGal opened this issue Nov 23, 2022 · 7 comments
Closed

Restore problems with 17.5.0-pre.1.0 version of windows.vs2022preview.scout.amd64.open #11707

MattGal opened this issue Nov 23, 2022 · 7 comments
Assignees
@MattGal
Labels
Ops - Compliance First-responder-style issues handled by the Operations V-Team due to prioritization or urgency level

Comments

@MattGal
Copy link
Member

MattGal commented Nov 23, 2022 •
edited
Loading

Example build

This came with version 2022.1111.201243 of the windows.vs2022preview.scout.amd64.open image, which took us from 17.4.0-pre.6.0 VS 2022 to 17.5.0-pre.1.0

The error message log suspiciously matches this developer community issue, but that could be a red herring.

##[error].dotnet\sdk\7.0.100-rc.1.22431.12\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(267,5): error NETSDK1004: (NETCORE_ENGINEERING_TELEMETRY=Build) Assets file 'D:\a\_work\1\s\artifacts\obj\Microsoft.CodeAnalysis.UnitTests\project.assets.json' not found. Run a NuGet package restore to generate this file.

We should hold off promoting the scouting image to the "regular" preview version to 17.5.0-pre.1.0 until this is understood. It might just go away with the next version... but without a repro / root cause this is unlikely.

Release Note Description

Rolled back windows.vs2022preview.scout.amd64* Helix queues to mitigate a Nuget bug
@Chrisboh Chrisboh added Ops - Compliance First-responder-style issues handled by the Operations V-Team due to prioritization or urgency level and removed Ops - First Responder labels Dec 2, 2022
@dibarbet dibarbet mentioned this issue Dec 7, 2022
Merged
@MattGal
Copy link
Member Author

MattGal commented Dec 15, 2022

The staging environment now has 17.5.0-pre.2.0 and the next rollout (1/11/2023) will include this, so there is likely no longer a need to keep this issue open as we have successfully skipped the problematic version. I will attempt to test this against the staging environment to see if it works as expected.

@MattGal
Copy link
Member Author

MattGal commented Dec 15, 2022

https://dnceng-public.visualstudio.com/public/_build/results?buildId=113900&view=results will show if this problem goes away using 17.5.0-pre.2.0

@MattGal
Copy link
Member Author

MattGal commented Dec 15, 2022

Rats, 17.5.0-pre.2.0 has the same problem. I'll spend some more time trying to investigate why.

@MattGal MattGal self-assigned this Jan 20, 2023
@MattGal
Copy link
Member Author

MattGal commented Jan 20, 2023

No progress made but this only impacts a specific pipeline and we have found no reason that the image is having problem, so I am going to close this issue. Both preview images will be running 17.5.0-pre.2.0 as of next Wednesday (1/25/2023)

@MattGal MattGal closed this as completed Jan 20, 2023
@MattGal MattGal added the Needs Triage A new issue that needs to be associated with an epic. label Jan 26, 2023
@MattGal
Copy link
Member Author

MattGal commented Jan 26, 2023

Reopening per this Teams conversation to discuss in triage today. The issue is now understood and the request is to revert all our "Preview" VS images to 17.4 versions due to this bug.

The bug these images all have is NuGet/Home#12373. The simplest thing would probably be to just revert this week's rollout; I am prepping a PR for just this now.

@MattGal MattGal reopened this Jan 26, 2023
@MattGal
Copy link
Member Author

MattGal commented Jan 26, 2023

I created a PR rolling back this week's VS 2022 preview changes to have it ready in case we want to roll this out tomorrow with the fix for #12332

@MattGal MattGal removed the Ops - Compliance First-responder-style issues handled by the Operations V-Team due to prioritization or urgency level label Jan 26, 2023
@michellemcdaniel michellemcdaniel added Ops - Compliance First-responder-style issues handled by the Operations V-Team due to prioritization or urgency level and removed Needs Triage A new issue that needs to be associated with an epic. labels Jan 26, 2023
@MattGal
Copy link
Member Author

MattGal commented Jan 31, 2023

Rolled out last week, closing.

@MattGal MattGal closed this as completed Jan 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MattGal MattGal

Labels
Ops - Compliance First-responder-style issues handled by the Operations V-Team due to prioritization or urgency level
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@MattGal @michellemcdaniel @Chrisboh