chore: updates for 1.12

[avik-pal]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @avik-pal, 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 includes several updates to the Boltz repository, focusing on improving the testing infrastructure, managing dependencies, and reorganizing the test suite. These changes aim to enhance the maintainability and reliability of the project.

Highlights

• Buildkite Configuration: The .buildkite/testing.yml file has been updated to streamline CUDA GPU testing by removing reactant-specific configurations and simplifying test arguments.
• Dependabot Configuration: The .github/dependabot.yml file now includes Julia as a supported package ecosystem, enabling automated dependency updates for Julia projects in the repository.
• Project.toml Updates: The Project.toml file has been updated to version 1.8.0, with updates to dependencies including MLDataDevices and the addition of a workspace configuration for test and docs projects.
• Test Suite Restructuring: The test suite has been reorganized, with qa_tests.jl renamed and moved to test/core/qa.jl, and layer-specific tests moved into the test/layers/ directory. This change improves the organization and maintainability of the test suite.
• Dependency Management: The test Project.toml file has been updated to remove CPUSummary, LuxCUDA, ReTestItems, and Zygote as dependencies, and add Boltz and ParallelTestRunner as dependencies. Additionally, a [sources] section was added to specify the path for the Boltz dependency.

Ignored Files

• Ignored by pattern: .github/workflows/** (2)
  • .github/workflows/CI.yml
  • .github/workflows/CompatHelper.yml

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 introduces a significant and highly beneficial refactoring of the entire testing infrastructure. The migration from ReTestItems.jl to ParallelTestRunner.jl greatly simplifies the test execution logic. Splitting large, monolithic test files into smaller, more focused files for each component is an excellent change that will improve maintainability. The dependency updates and project configuration changes, such as adding a Julia workspace, are also welcome modernizations. I've identified one critical issue in the new test utilities that would cause tests to fail, and one minor suggestion for code simplification. Overall, these are excellent changes.