fix: update test workflows to fix failure

[shenxianpeng]

After #113, test workflows failed. This PR will fix the failure of it.

Summary by CodeRabbit

• Chores
  • Enhanced automated testing by expanding trigger conditions, ensuring more comprehensive test coverage.
  • Updated compatibility tests to include newer Python versions, now supporting Python 20 and revising previous exclusions.
  • Refreshed integrity checks for key assets across supported platforms.
  • Updated the release version tag for clang-tools.
  • Changed the source URL for downloading clang-tools binaries.

[coderabbitai]

Walkthrough

This update modifies the CI workflow configuration and adjusts SHA-512 checksum files. In the workflow file, a new file path trigger ("clang_tools/init.py") has been added, and the Python version matrix has been updated to include version 20 while modifying an exclusion for macOS. Additionally, the SHA-512 checksum values for the clang-format-12 binaries (Linux, macOS, and Windows) have been revised to reflect updated file contents.

Changes

File(s)	Change Summary
.github/.../python-test.yml	Added "clang_tools/__init__.py" to trigger paths; updated Python version matrix (Python 20 added; comment removed for macOS exclusion of version 19)
tests/clang-format-12_*sha512sum	Updated SHA-512 checksum values for clang-format-12 binaries on Linux, macOS, and Windows
clang_tools/__init__.py	Updated release_tag from "master-4eaa4a54" to "master-2da3e7b"
clang_tools/install.py	Modified base URL in clang_tools_binary_url function from "https://github.com/cpp-linter/clang-tools-static-binaries/releases/download/" to "https://github.com/muttleyxd/clang-tools-static-binaries/releases/download/"

Sequence Diagram(s)

sequenceDiagram
    participant PR as "Pull Request"
    participant GH as "GitHub Actions"
    participant Job as "Installation Job"

    PR->>GH: Submit PR with changes (including clang_tools/__init__.py)
    GH->>GH: Detect changes based on updated trigger paths
    GH->>Job: Initiate testing with Python versions [8...20]
    Job-->>GH: Return test results

Loading

Poem

I'm a bunny in the code, hopping in delight,
New triggers and versions make my workflow bright.
I nibble through the changes with a gentle sway,
Checksums and tests now dance in a new array.
Hop along with CodeRabbit, bugs be gone— hooray!

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 67b5508 and 7e979d4.

📒 Files selected for processing (2)

• clang_tools/__init__.py (1 hunks)
• clang_tools/install.py (1 hunks)

✅ Files skipped from review due to trivial changes (2)

• clang_tools/install.py
• clang_tools/init.py

⏰ Context from checks skipped due to timeout of 90000ms (6)

• GitHub Check: install (20, macos-latest)
• GitHub Check: install (16, macos-latest)
• GitHub Check: install (19, macos-latest)
• GitHub Check: install (14, macos-latest)
• GitHub Check: install (11, macos-latest)
• GitHub Check: Codacy Static Code Analysis

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud