Package Sdk/3.1.422-servicing-016036 for MAC OS is missed

Hi @dotnet/dnceng,

During automatic Arcade update,[main] Update dependencies from dotnet/arcade by dotnet-maestro · Pull Request #292 · dotnet/install-scripts (github.com) I have noticed tests failure for MAC OS machine Pipelines - Run 20220713.1 logs (azure.com).

I have checked scripts installation for Ubuntu and Mac OS ./dotnet-install.sh -Channel "release/3.1.4xx" -Verbose

and it fails for the second env only: Download failed: https://dotnetcli.azureedge.net/dotnet/Sdk/3.1.422-servicing-016036/dotnet-dev-osx-x64.3.1.422-servicing-016036.tar.gz

This version is resolved from https://dotnetcli.azureedge.net/dotnet/Sdk/release/3.1.4xx/latest.version file

Could you check if the package exists?

[riarenas]

This refers to a new build of the release branch of the installer repository.

No deployment involved and @marcpopMSFT can probably answer when a new build is expected.

[riarenas]

It might have been lost in the other discussion so mentioning it again in case this is related. @adiaaida and I looked into this build (the latest successful public release/3.1.4xx): https://dev.azure.com/dnceng/internal/_build/results?buildId=1868892&view=results and we found that for some reason, a Darwin asset manifest wasn’t uploaded, and thus the publishing infra didn’t publish any OSX related files. My initial investigations seem to suggest a #vso logging command got dopped by the console and didn’t trigger the manifest upload.

I tried running the same SHA: https://dev.azure.com/dnceng/internal/_build/results?buildId=1883680&view=results, but as these are stable builds, we would’ve attempted to publish duplicate packages to feeds, so it failed. Do we need to run a new build that does a version bump so we stop getting conflicts? or is it OK to wait until a new build of 3.1.4xx happens naturally?

Or is that completely unrelated to the missing packages?