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

[MONITOR-SPEC-PR] [KEEP] Python change log generation failed #9515

Open
jianingwang123 opened this issue Dec 11, 2024 · 5 comments
Open

[MONITOR-SPEC-PR] [KEEP] Python change log generation failed #9515

jianingwang123 opened this issue Dec 11, 2024 · 5 comments

Comments

@jianingwang123
Copy link

jianingwang123 commented Dec 11, 2024

Description:
Python SDK Automation change log generation failed, but it outputs result: succeeded.

"changelog": {
        "content": "change log generation failed!!!",
        "hasBreakingChange": false,
        "breakingChangeItems": []
      },
      "version": "10.3.1",
      "artifacts": [
        "sdk/keyvault/azure-mgmt-keyvault/dist/azure-mgmt-keyvault-10.3.1.zip",
        "sdk/keyvault/azure-mgmt-keyvault/dist/azure_mgmt_keyvault-10.3.1-py3-none-any.whl"
      ],
      "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

@msyyc
Copy link
Member

msyyc commented Dec 13, 2024

Will take a look. Since the failure for changelog doesn't block PR merge, you could ignore it for now.

@wanlwanl
Copy link
Member

Thanks @msyyc , would you mind sharing the current status of this issue?

@wanlwanl wanlwanl added P1 and removed P0 labels Dec 25, 2024
@wanlwanl wanlwanl removed their assignment Dec 25, 2024
@msyyc
Copy link
Member

msyyc commented Dec 26, 2024

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.

@jianingwang123 jianingwang123 changed the title [MONITOR-SPEC-PR] Python change log generation failed [MONITOR-SPEC-PR] [KEEP] Python change log generation failed Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

3 participants