[CI] Update Pillow, pytest-rerunfailures, junitparser, xgboost, onnx and pytorch

[mshr-h]

Fix #18775 (comment) , update xgboost, onnx and pytorch

[gemini-code-assist]

Summary of Changes

Hello @mshr-h, 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 addresses a continuous integration (CI) issue by modifying the Python package installation script. It removes specific version constraints for Pillow, pytest-rerunfailures, and junitparser, enabling the CI environment to install the latest compatible versions of these libraries. This change aims to resolve potential dependency conflicts or outdated package issues that were causing CI failures, ensuring a more robust and up-to-date build process.

Highlights

• Dependency Unpinning: Unpinned the Pillow package, removing the explicit version constraint ==9.1.0 to allow installation of newer versions.
• Dependency Unpinning: Unpinned the pytest-rerunfailures package, removing the explicit version constraint ==10.2 to allow installation of newer versions.
• Dependency Unpinning: Unpinned the junitparser package, removing the explicit version constraint ==2.4.2 to allow installation of newer versions.

🧠 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/install/ubuntu_install_python_package.sh
  • Removed explicit version pinning for Pillow.
  • Removed explicit version pinning for pytest-rerunfailures.
  • Removed explicit version pinning for junitparser.

Activity

• This change was implemented to fix an issue reported in a GitHub comment, specifically addressing https://github.com/apache/tvm/pull/18775#issuecomment-3901181065.

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 unpins Pillow, pytest-rerunfailures, and junitparser in the CI environment. While using the latest versions of dependencies can help identify integration issues early, unpinning them completely can lead to non-reproducible builds. This can make it difficult to diagnose CI failures when they are caused by an upstream dependency update. I've added a comment suggesting to instead upgrade these packages to their latest stable versions and keep them pinned. This approach provides the benefits of newer packages while maintaining a deterministic and stable CI environment.

[gemini-code-assist]

Unpinning dependencies can lead to non-reproducible builds and make it difficult to debug CI failures caused by upstream changes. To ensure build stability, it's a best practice to pin dependencies to specific versions.

Instead of removing the version pins for Pillow, pytest-rerunfailures, and junitparser, could you please update these packages to their latest stable versions and pin them? This will provide the benefits of newer versions while keeping the CI environment deterministic.