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

SDK automation failed at migrate-package formatting step #32973

Open
jeremymeng opened this issue Feb 11, 2025 · 1 comment
Open

SDK automation failed at migrate-package formatting step #32973

jeremymeng opened this issue Feb 11, 2025 · 1 comment
Assignees
Labels
dev-tool Issues related to the Azure SDK for JS dev-tool EngSys This issue is impacting the engineering system.

Comments

@jeremymeng
Copy link
Member

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4553716&view=logs&j=47092895-c7c8-567a-c7a6-8c88f3ec178e&t=d293a8e8-c6af-5091-cdf7-4c66482dd6f2&l=328

It looks that after generation we ran migrate-package command directly without running rush update so dev-tool failed to execute the npm run format command.

@wanlwanl I saw in some other automation run where typespec files was modified there's rush update before migrate-package. Do you know why it is not the same for the above run?

@jeremymeng jeremymeng added dev-tool Issues related to the Azure SDK for JS dev-tool EngSys This issue is impacting the engineering system. labels Feb 11, 2025
@wanlwanl wanlwanl self-assigned this Feb 13, 2025
@wanlwanl
Copy link
Member

wanlwanl commented Feb 13, 2025

It looks that after generation we ran migrate-package command directly without running rush update so dev-tool failed to execute the npm run format command.

I put migration step after rush update step for all sdk automations currently. Great, I can move migration step before rush update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev-tool Issues related to the Azure SDK for JS dev-tool EngSys This issue is impacting the engineering system.
Projects
Status: Backlog
Development

No branches or pull requests

3 participants