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

Tracking CI follow-ups from #47212 #47220

Closed
3 tasks done
m-redding opened this issue Nov 18, 2024 · 0 comments
Closed
3 tasks done

Tracking CI follow-ups from #47212 #47220

m-redding opened this issue Nov 18, 2024 · 0 comments
Labels
Client This issue points to a problem in the data-plane of the library. EngSys This issue is impacting the engineering system.

Comments

@m-redding
Copy link
Member

m-redding commented Nov 18, 2024 •
edited
Loading

There are some ci failures in #47212

Since that PR is running over 1600 pipelines and has 480,000 loc changes, I would prefer not to address the ci failures in that PR. Instead, I am opening a tracking issue to make sure I follow up on all failed CIs.
@github-actions github-actions bot added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Nov 18, 2024
@m-redding m-redding mentioned this issue Nov 18, 2024
Merged
@m-redding m-redding changed the title Tracking CI follow-ups from https://github.com/Azure/azure-sdk-for-net/pull/47212 Tracking CI follow-ups from #47212 Nov 18, 2024
@m-redding m-redding added Client This issue points to a problem in the data-plane of the library. EngSys This issue is impacting the engineering system. and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Client This issue points to a problem in the data-plane of the library. EngSys This issue is impacting the engineering system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@m-redding