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

yarn devtools:build:chrome failed #55047

Closed
1 of 2 tasks
dreampasssser opened this issue Mar 26, 2024 · 6 comments
Closed
1 of 2 tasks

yarn devtools:build:chrome failed #55047

dreampasssser opened this issue Mar 26, 2024 · 6 comments
Assignees
Labels
area: dev-infra Issues related to Angular's own dev infra (build, test, CI, releasing) windows Issue related to Microsoft's Windows operating system
Milestone

Comments

@dreampasssser
Copy link

dreampasssser commented Mar 26, 2024

Is this a bug report or a feature request?

  • Bug Report
  • Feature Request

Please provide the steps to reproduce the issue [Bug Report only]

  1. Several days ago, I checked out the latest main branch(SHA: 0461bff) to build a devtools for chrome.
  2. I did all the things in prerequisite-software in DEVELOPER.md. And add C:\msys64\usr\bin to the PATH environment variable(Win11 system).
  3. Then I excuted yarn --frozen-lockfile in git-bash. In order to complete it successfully, I deleted one line("sauce-connect": "https://saucelabs.com/downloads/sc-4.9.1-linux.tar.gz",) in package.json. I known it's for test, so I think it's no matter, I just want to build a devtools.
  4. Then I changed system to developer mode and excuted yarn devtools:build:chrome, and it returned me BazelWorkspaceStatusAction stable-status.txt failed: Failed to determine workspace status: Process exited with status 1.

Please provide the expected behavior vs the actual behavior you encountered [Bug Report only]

It is expected that I excute yarn devtools:build:chrome successfully.

Please provide a screenshot if possible [Bug Report only]

image

Please provide the exception or error you saw [Bug Report only]

In the screenshot above

Is this a browser-specific issue? If so, please specify the device, browser, and version. [Bug Report only]

no

Description [Feature Request only]

No response

Proposed solution [Feature Request only]

No response

Alternatives considered [Feature Request only]

No response

@alxhub alxhub added area: dev-infra Issues related to Angular's own dev infra (build, test, CI, releasing) windows Issue related to Microsoft's Windows operating system labels Mar 26, 2024
@ngbot ngbot bot modified the milestone: needsTriage Mar 26, 2024
@AleksanderBodurri AleksanderBodurri self-assigned this Mar 27, 2024
@AleksanderBodurri
Copy link
Member

Thanks for the report 🙏 Could you run yarn --frozen-lockfile && yarn bazel clean --expunge and then try to build DevTools again?

If that still fails try out the --verbose_failures flag to see if the error message surfaces

@dreampasssser
Copy link
Author

@AleksanderBodurri

Wow~, it works, but it cannot to be packed into a devtools-chrome.zip when I run (cd dist/bin/devtools/projects/shell-browser/src/prodapp && zip -r ~/devtools-chrome.zip *). There is no devtools-chrome.zip to be generated. And the screenshot is below:

屏幕截图 2024-03-30 092548

@JeanMeche
Copy link
Member

zip generation looks fine. Did look in the right directory ?

Anyway this issue is solved now.

@dreampasssser
Copy link
Author

@JeanMeche @AleksanderBodurri

Oh, I'm so sorry, I did looked in a wrong directory. Thank you!

@AleksanderBodurri
Copy link
Member

No worries at all 😁

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Apr 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: dev-infra Issues related to Angular's own dev infra (build, test, CI, releasing) windows Issue related to Microsoft's Windows operating system
Projects
None yet
Development

No branches or pull requests

4 participants