[CI] Remove stale test scripts (i386, hexagon, mypy)

[tqchen]

Summary

Remove 9 test scripts from tests/scripts/ that are no longer used in CI —
i386 and hexagon architectures were removed from CI, mypy moved to pre-commit,
and several others are unreferenced.

[gemini-code-assist]

Summary of Changes

Hello, 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 streamlines the CI process by removing several outdated and unreferenced test scripts. It specifically targets scripts related to i386 and Hexagon architectures, which are no longer supported in CI, and moves mypy checks to pre-commit hooks, resulting in a cleaner and more efficient test suite.

Highlights

• Removed Stale Architecture Tests: Eliminated test scripts for i386 and Hexagon architectures, as these are no longer part of the CI pipeline.
• Mypy Integration Streamlined: Removed the standalone mypy test script, as mypy checks have been integrated into pre-commit hooks for more immediate feedback.
• Cleanup of Unreferenced Scripts: Deleted several other test scripts that were no longer called or used within the CI system, improving maintainability.
• Documentation Updates: Updated Hexagon-related README to remove references to the now-deleted build and test scripts, providing direct build instructions instead.

🧠 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.

Changelog

• docker/lint.sh
  • Removed the explicit 'mypy' case from the linting script, as it's now handled by pre-commit.
• tests/python/contrib/test_hexagon/README.md
  • Removed references to 'task_build_hexagon_api.sh' and 'task_config_build_hexagon.sh'.
  • Removed reference to 'task_python_hexagon.sh'.
  • Replaced script calls with direct 'cmake' commands for building TVM and Hexagon API.
• tests/scripts/ci.py
  • Removed 'task_opencl_cpp_unittest.sh' from the 'unittest' command group.
  • Removed the entire 'hexagon' command group, including its 'post_build' and 'test' options.
• tests/scripts/task_build_hexagon_api.sh
  • Removed the script.
• tests/scripts/task_clean.sh
  • Removed the script.
• tests/scripts/task_config_build_gpu_vulkan.sh
  • Removed the script.
• tests/scripts/task_config_build_hexagon.sh
  • Removed the script.
• tests/scripts/task_config_build_i386.sh
  • Removed the script.
• tests/scripts/task_mypy.sh
  • Removed the script.
• tests/scripts/task_opencl_cpp_unittest.sh
  • Removed the script.
• tests/scripts/task_python_hexagon.sh
  • Removed the script.
• tests/scripts/task_python_nightly.sh
  • Removed the script.

Activity

• No specific activity (comments, reviews, progress updates) has been recorded for this pull request yet.

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 is a good cleanup effort, removing several stale test scripts from the CI process. The changes are mostly straightforward removals of unused files and their references. However, while updating the documentation for Hexagon testing, the instructions for building inside the Docker container have become incomplete. I've added a review comment with a suggestion to fix the documentation to ensure users can still follow the build and test process for Hexagon.