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

[release/7.0] [workloads] Specify arm64 alias instead of arm in the arm64 pack #80434

Merged
merged 1 commit into from
Jan 11, 2023

Conversation

github-actions[bot]
Copy link
Contributor

Backport of #79555 to release/7.0

/cc @steveisok

Customer Impact

Testing

Risk

IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.

@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@steveisok
Copy link
Member

@carlossanlop this is a tell mode change

@carlossanlop
Copy link
Member

@carlossanlop this is a tell mode change

Ok sounds good. Do you see anything concerning in the CI? There were lots of failures, but a big chunk of them were a git fetch error.

@carlossanlop
Copy link
Member

carlossanlop commented Jan 11, 2023

Lots of CI failures in Apple OSs in the re-run:

Publishing build artifacts failed with an error: Not found PathtoPublish: /Users/runner/work/1/s/artifacts/log/

I opened an issue in arcade to track it: dotnet/arcade#12176

Nothing specific to arm64. I'll merge this @steveisok .

@steveisok
Copy link
Member

Lots of CI failures in Apple OSs in the re-run:

Publishing build artifacts failed with an error: Not found PathtoPublish: /Users/runner/work/1/s/artifacts/log/

I opened an issue in arcade to track it: dotnet/arcade#12176

Nothing specific to arm64. I'll merge this @steveisok .

Should have been fixed with #80454

@carlossanlop
Copy link
Member

Should have been fixed with #80454

The CI of this PR was started on Jan 10th at 6 AM, and the fix you linked was merged on Jan 11th at 12AM. That's why it wasn't reflected here.

@ghost ghost locked as resolved and limited conversation to collaborators Feb 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants