-
Notifications
You must be signed in to change notification settings - Fork 183
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
[MONITOR-SPEC-PR] [KEEP] Python change log generation failed #9515
Comments
@msyyc , python changelog generation is failed, but it outputs |
Will take a look. Since the failure for changelog doesn't block PR merge, you could ignore it for now. |
Thanks @msyyc , would you mind sharing the current status of this issue? |
The root cause is that compute is multiapi package which costs too much time to generate changelog. But compute will be converted to single api package after 2025/05/01 and at that time changelog will be OK. |
Description:
Python SDK Automation change log generation failed, but it outputs
result: succeeded
.Additional context:
link1: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4400779&view=logs&j=b7f68bce-9df8-5468-1c9f-74766cfc9a39&t=25fc8ae6-51ed-58e2-b772-f4d054412fe3&l=10592
link2: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4400847&view=logs&j=b7f68bce-9df8-5468-1c9f-74766cfc9a39&t=25fc8ae6-51ed-58e2-b772-f4d054412fe3&l=7729
link3: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4413086&view=logs&j=b7f68bce-9df8-5468-1c9f-74766cfc9a39&t=25fc8ae6-51ed-58e2-b772-f4d054412fe3&l=320788
link4: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4404510&view=logs&j=b7f68bce-9df8-5468-1c9f-74766cfc9a39&t=25fc8ae6-51ed-58e2-b772-f4d054412fe3&l=2051
link5: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4412586&view=logs&j=b7f68bce-9df8-5468-1c9f-74766cfc9a39&t=25fc8ae6-51ed-58e2-b772-f4d054412fe3&l=251165
link6: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4407177&view=logs&j=b7f68bce-9df8-5468-1c9f-74766cfc9a39&t=25fc8ae6-51ed-58e2-b772-f4d054412fe3&l=250835
link7: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4418123&view=logs&j=b7f68bce-9df8-5468-1c9f-74766cfc9a39&t=25fc8ae6-51ed-58e2-b772-f4d054412fe3&l=250678
link8: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4419098&view=logs&j=b7f68bce-9df8-5468-1c9f-74766cfc9a39&t=25fc8ae6-51ed-58e2-b772-f4d054412fe3&l=12352
link9: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4430591&view=logs&j=b7f68bce-9df8-5468-1c9f-74766cfc9a39&t=25fc8ae6-51ed-58e2-b772-f4d054412fe3&l=9504
link10: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4430858&view=logs&j=b7f68bce-9df8-5468-1c9f-74766cfc9a39&t=25fc8ae6-51ed-58e2-b772-f4d054412fe3&l=1629
link11: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4437492&view=logs&j=b7f68bce-9df8-5468-1c9f-74766cfc9a39&t=25fc8ae6-51ed-58e2-b772-f4d054412fe3&l=1619
link12: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4459669&view=logs&j=b7f68bce-9df8-5468-1c9f-74766cfc9a39&t=25fc8ae6-51ed-58e2-b772-f4d054412fe3&l=250862
link13: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4461903&view=logs&j=b7f68bce-9df8-5468-1c9f-74766cfc9a39&t=25fc8ae6-51ed-58e2-b772-f4d054412fe3&l=1627
The text was updated successfully, but these errors were encountered: