chore(pm): update e2e

[elrrrrrrr]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @elrrrrrrr, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates an existing end-to-end test script to introduce a more rigorous evaluation of the utoo install command. By systematically testing a range of manifests-concurrency-limit values, the changes aim to ensure the command's robustness and gather performance data under varying concurrency conditions.

Highlights

• Enhanced utoo install Testing: The end-to-end test script for utoo-pm.sh has been updated to include a comprehensive test for the utoo install command, iterating through various manifests-concurrency-limit values.
• Concurrency Limit Evaluation: The script now systematically tests utoo install with concurrency limits ranging from 10 to 200, aiming to assess its performance and stability under different conditions.
• Performance Measurement: Each utoo install execution within the new testing loop is timed, allowing for performance analysis and comparison across different concurrency settings.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the end-to-end test script to add performance testing for utoo install with various --manifests-concurrency-limit values for the ant-design project. This change aligns its testing with the existing setup for ant-design-x. The implementation is correct, but it introduces a large block of duplicated code. My feedback focuses on refactoring this repeated logic into a reusable shell function to improve the script's maintainability.

[gemini-code-assist]

This block of code is almost identical to the one used for ant-design-x (lines 27-36). To avoid code duplication and improve maintainability, this logic should be extracted into a reusable shell function.

You can define a function at the top of the script (e.g., after the color definitions) like this:

function test_concurrency_limits() {
  local project_name="$1"
  echo -e "${YELLOW}Testing different manifests-concurrency-limit values for ${project_name}...${NC}"
  for limit in 10 20 40 60 70 80 90 100 120 200; do
    echo -e "${YELLOW}--- Testing manifests-concurrency-limit=$limit ---${NC}"
    rm -rf node_modules package-lock.json
    rm -rf ~/.cache/nm
    time utoo install --ignore-scripts --manifests-concurrency-limit $limit || { echo -e "${RED}FAIL: utoo install failed for ${project_name} with limit=$limit${NC}"; exit 1; }
    echo -e "${GREEN}PASS: limit=$limit completed for ${project_name}${NC}"
    echo ""
  done
}

Then, you can replace this entire block with a single call to this function. The same function can then be used to refactor the test for ant-design-x.

Suggested change

	# Test different manifests-concurrency-limit values
	echo -e "${YELLOW}Testing different manifests-concurrency-limit values...${NC}"
	for limit in 10 20 40 60 70 80 90 100 120 200; do
	echo -e "${YELLOW}--- Testing manifests-concurrency-limit=$limit ---${NC}"
	rm -rf node_modules package-lock.json
	rm -rf ~/.cache/nm
	time utoo install --ignore-scripts --manifests-concurrency-limit $limit || { echo -e "${RED}FAIL: utoo install failed with limit=$limit${NC}"; exit 1; }
	echo -e "${GREEN}PASS: limit=$limit completed${NC}"
	echo ""
	done
	test_concurrency_limits "ant-design"