Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(tidb-engine-ext): add cargo cache for tidb-eninge-ext #3204

Conversation

purelind
Copy link
Collaborator

@purelind purelind commented Nov 5, 2024

Add cargo home cache for tidb-engine-ext to mitigate download failures caused by the network.

Copy link

ti-chi-bot bot commented Nov 5, 2024

I have already done a preliminary review for you, and I hope to help you do a better job.

The pull request adds a cargo cache for tidb-engine-ext to mitigate download failures caused by the network. It does this by setting the CARGO_HOME environment variable and mounting a persistent volume claim for the cache.

There do not seem to be any potential problems with this pull request. However, it might be a good idea to test that the cache is working as expected before merging the pull request.

One suggestion for improvement would be to add a comment in the pull request asking the submitter to test the cache and confirm that it is working as expected. Additionally, it might be helpful to include some instructions in the pull request description for how to test the cache.

@ti-chi-bot ti-chi-bot bot added the size/S label Nov 5, 2024
Copy link

ti-chi-bot bot commented Nov 5, 2024

I have already done a preliminary review for you, and I hope to help you do a better job.

Based on the PR title and description, it seems that the main change in this PR is adding a cargo cache for tidb-engine-ext to mitigate download failures due to network issues. The changes in the PR include adding environment variables for CARGO_NET_GIT_FETCH_WITH_CLI and CARGO_HOME, as well as adding volume mounts for cargo-cache.

Regarding potential problems, one thing to consider is whether the persistent volume claim (PVC) for cargo-home-linux-amd64 is available and correctly configured. If the PVC does not exist or is not properly configured, it could cause issues during the build process, leading to build failures.

Additionally, it is unclear from the PR description whether the added volume mount for cargo-cache will conflict with other volume mounts in the build environment. If there are any conflicts, it could cause issues during the build process as well.

As for fixing suggestions, you could first confirm that the PVC for cargo-home-linux-amd64 is available and properly configured. If not, you could suggest creating a new PVC or modifying the existing one. Additionally, you could suggest testing the added volume mount for cargo-cache to ensure that there are no conflicts with other volume mounts. If there are conflicts, you could suggest modifying the mount point or finding a different solution.

Overall, the changes in this PR seem reasonable and could potentially improve the build process for tidb-engine-ext. However, it is important to ensure that the added volume mount and PVC are properly configured to avoid any issues during the build process.

Copy link

ti-chi-bot bot commented Nov 5, 2024

I have already done a preliminary review for you, and I hope to help you do a better job.

Based on the pull request title and description, the key changes made in this pull request are adding cargo cache for tidb-engine-ext to mitigate download failures caused by the network. This is achieved by adding two environment variables CARGO_HOME and CARGO_NET_GIT_FETCH_WITH_CLI, and a new volume mount to the Kubernetes pod.

There are no obvious potential problems with this pull request, and the changes seem sensible. However, it would be good to ensure that the persistent volume claim cargo-home-linux-amd64 exists, as this is referenced in the volume mount for both presubmits and release-6.1-latest-presubmits.

One suggestion for improvement would be to provide some documentation or additional information on why cargo cache is important and how it works, as this would help other contributors understand the changes being made.

Copy link

ti-chi-bot bot commented Nov 5, 2024

I have already done a preliminary review for you, and I hope to help you do a better job.

Based on the diff provided, the key changes in this PR are:

  • A new volume mount has been added to the presubmit and release-6.1-latest-presubmits.yaml files for cargo-cache.
  • A new environment variable, CARGO_HOME, has been added to the presubmit and release-6.1-latest-presubmits.yaml files.

The PR aims to add cargo home cache for tidb-engine-ext to mitigate download failures caused by the network.

There are no potential problems that I could identify in the provided diff.

For fixing suggestions, I would recommend adding a brief explanation in the PR description about what cargo home cache is and how it could help in mitigating download failures caused by the network. Additionally, a brief testing plan should be included in the PR description to ensure that this change works as expected.

Copy link

ti-chi-bot bot commented Nov 5, 2024

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@purelind
Copy link
Collaborator Author

purelind commented Nov 5, 2024

/hold

Copy link

ti-chi-bot bot commented Nov 5, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-11-05 09:49:41.556002653 +0000 UTC m=+948094.395158221: ✖️🔁 reset by purelind.

@ti-chi-bot ti-chi-bot bot removed the lgtm label Nov 5, 2024
Copy link

ti-chi-bot bot commented Nov 5, 2024

New changes are detected. LGTM label has been removed.

@purelind purelind added the lgtm label Nov 5, 2024
@purelind
Copy link
Collaborator Author

purelind commented Nov 5, 2024

/unhold

@ti-chi-bot ti-chi-bot bot merged commit 5f3c1f6 into PingCAP-QE:main Nov 5, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

1 participant