Expired Helix queue windows.10.amd64.client21h1.open failing 6.0 CI run #79646

Activity

2. ghost added

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Dec 14, 2022
3. CarnaViire

   changed the title [-]Expired Helix queue `windows.10.amd64.client21h1.open failing 6.0 CI run[/-] [+]Expired Helix queue windows.10.amd64.client21h1.open failing 6.0 CI run[/+] on Dec 14, 2022
4. CarnaViire

   added

   area-Infrastructure

   on Dec 14, 2022
6. ViktorHofer commented on Dec 14, 2022

   

   ViktorHofer

   on Dec 14, 2022

   Member

   More actions

   Looks like we also use that queue in main:

   runtime/eng/pipelines/libraries/helix-queues-setup.yml

   Line 180 in 8e15d9f

   - Windows.10.Amd64.Client21H1.Open

   @CarnaViire do you want to submit PRs targeting 6.0, 7.0 and main to fix that?
7. CarnaViire commented on Dec 14, 2022

   

   CarnaViire

   on Dec 14, 2022

   MemberAuthor

   More actions

   @ViktorHofer it is stated there as the only machine for net48 builds. Is there something it should be changed to?
   Also, I wonder why I don't see similar failures in main and 7.0 CI 🤔 is net48 only running for 6.0 branch?

   (While I can attempt to submit the fix, I will be OOF starting this Friday, so I might not be the best person to do that)
8. ViktorHofer commented on Dec 14, 2022

   

   ViktorHofer

   on Dec 14, 2022

   Member

   More actions

   That message also appears in main and release/7.0 but it was downgraded to not fail the build: https://dnceng-public.visualstudio.com/public/_build/results?buildId=111851&view=logs&j=4260d0c6-5941-59c0-51d5-62bf49c37870&t=691348e9-db6c-5b8a-8ed1-66f42a3b255d&l=46

   @dotnet/dnceng to which Windows Client version should we upgrade to, away from windows.10.amd64.client21h1.open?
9. MattGal commented on Dec 14, 2022

   

   MattGal

   on Dec 14, 2022

   Member

   More actions

   https://github.com/orgs/dotnet/teams/dnceng to which Windows Client version should we upgrade to, away from windows.10.amd64.client21h1.open?

   There are now windows.10.amd64.client.open and windows.10.amd64.client, which should not expire til the end of life of Windows 10.

   As a side note, to not break the build, I'd suggest setting "TreatWarningsAsErrors" as false in the "Send to Helix" stages of your build. Due to no more rollouts this year, the queue won't actually be fully removed until around 1/11/2023 which would make addressing this less urgent.

   Feel free to ping me directly on Teams for any questions.

   👍React with 👍1Reacted by Viktor Hofer
10. ghost added

    in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged

    on Dec 14, 2022
11. ghost removed

    in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged

    on Jan 4, 2023
12. akoeplinger commented on Jan 11, 2023

    

    akoeplinger

    on Jan 11, 2023

    Member

    More actions

    This was fixed by #79665
13. akoeplinger

    closed this as completedon Jan 11, 2023
14. ghost removed

    untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

    on Jan 11, 2023
15. ghost locked as resolved and limited conversation to collaborators on Feb 10, 2023