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

remove tests from MariaDB builds #1064

Merged
merged 1 commit into from
May 29, 2024
Merged

Conversation

shogo82148
Copy link
Owner

@shogo82148 shogo82148 commented May 28, 2024

Summary by CodeRabbit

  • Chores
    • Improved cleanup process by removing the mariadb-test directory during MariaDB build on all platforms (Darwin, Linux, Windows).

Copy link

coderabbitai bot commented May 28, 2024

Walkthrough

The updates across the build scripts for macOS, Linux, and Windows involve the removal of the mariadb-test directory as part of the cleanup process during the MariaDB build. This change ensures that unnecessary test directories are not included in the final build archives, streamlining the build process and reducing the size of the build artifacts.

Changes

File Path Change Summary
.github/build-mariadb-darwin.sh Removal of the mariadb-test directory while archiving the MariaDB build.
.github/build-mariadb-linux.sh Removal of the mariadb-test directory in addition to other cleanup operations.
.github/build-mariadb-windows.ps1 Added conditional check and removal of the mariadb-test directory before removing the mysql-test directory.

In the land of code where binaries grow,
A cleanup was done, to streamline the flow.
No more test clutter in the build's final show,
MariaDB now lighter, for all to bestow.
🐇✨


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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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 full the review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 5c7ded5 and 1ba8d7d.
Files selected for processing (3)
  • .github/build-mariadb-darwin.sh (1 hunks)
  • .github/build-mariadb-linux.sh (1 hunks)
  • .github/build-mariadb-windows.ps1 (1 hunks)
Files skipped from review due to trivial changes (2)
  • .github/build-mariadb-darwin.sh
  • .github/build-mariadb-linux.sh
Additional comments not posted (1)
.github/build-mariadb-windows.ps1 (1)

163-165: Conditional check and removal of mariadb-test directory implemented as expected.

This change aligns with the PR's objective to remove tests from MariaDB builds. Ensure that this directory is not required elsewhere in the build process or by any other scripts.

Verification successful

The search for references to mariadb-test in the repository did not produce any output, indicating that the directory is not referenced elsewhere in the codebase.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify that the `mariadb-test` directory is not required elsewhere in the build process.

# Test: Search for any other references to `mariadb-test` in the repository.
rg --type ps1 --type sh 'mariadb-test'

Length of output: 66



Script:

#!/bin/bash
# Description: Verify that the `mariadb-test` directory is not required elsewhere in the build process.

# Test: Search for any other references to `mariadb-test` in the repository.
rg --type powershell --type sh 'mariadb-test'

Length of output: 80



Script:

#!/bin/bash
# Description: Verify that the `mariadb-test` directory is not required elsewhere in the build process.

# Test: Search for any other references to `mariadb-test` in the repository.
rg --type ps1 --type sh 'mariadb-test'

Length of output: 66



Script:

#!/bin/bash
# Description: Verify that the `mariadb-test` directory is not required elsewhere in the build process.

# Test: Search for any other references to `mariadb-test` in the repository.
rg 'mariadb-test'

Length of output: 17

@shogo82148
Copy link
Owner Author

before:
image

@shogo82148
Copy link
Owner Author

After:
image

@shogo82148 shogo82148 merged commit 9e776b4 into main May 29, 2024
229 of 341 checks passed
@shogo82148 shogo82148 deleted the remove-tests-from-mariadb-builds branch May 29, 2024 01:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant