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

fix:ci ubuntu cache miss #175

Merged
merged 1 commit into from
Jan 20, 2025
Merged

fix:ci ubuntu cache miss #175

merged 1 commit into from
Jan 20, 2025

Conversation

lqxhub
Copy link
Collaborator

@lqxhub lqxhub commented Jan 18, 2025

修复 CI中 Ubuntu ccache key 找不到的错误

Summary by CodeRabbit

  • Chores
    • Updated GitHub Actions workflow configuration for build process
    • Modified caching strategy for build artifacts

Copy link

coderabbitai bot commented Jan 18, 2025

Walkthrough

The pull request modifies the GitHub Actions workflow configuration in .github/workflows/kiwidb.yml, specifically altering the cache restoration strategy for the build_on_ubuntu job. The key change involves simplifying the cache key generation by removing the compiler-specific conditional and now using only a hash of source files for cache identification.

Changes

File Change Summary
.github/workflows/kiwidb.yml Simplified ccache key generation by removing compiler-specific condition and using only source file hash

Possibly related PRs

Suggested labels

☢️ Bug

Suggested reviewers

  • AlexStocks

Poem

🐰 In the realm of GitHub's flow,
A cache key change, soft and low
No compiler's trace, just pure hash might
Workflows dance with renewed delight!
Simplicity reigns, cache restored bright 🔑


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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.

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: 1

🔭 Outside diff range comments (1)
.github/workflows/kiwidb.yml (1)

Line range hint 144-150: Inconsistent error handling between Ubuntu and macOS E2E tests.

The Ubuntu job correctly propagates test failures with || exit 1, while the macOS job might mask failures. Consider standardizing the error handling across both jobs.

Apply this pattern to the macOS job's Go E2E test section:

  run: |
    set +e
    cd ../tests
    go mod tidy
-   go test -timeout 15m --ginkgo.v
+   go test -timeout 15m --ginkgo.v || exit 1
    sh print_log.sh
🧰 Tools
🪛 actionlint (1.7.4)

119-119: the runner of "actions/cache@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9937125 and 1711028.

📒 Files selected for processing (1)
  • .github/workflows/kiwidb.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: build_on_macos
  • GitHub Check: build_on_ubuntu

@@ -119,7 +119,7 @@ jobs:
uses: actions/cache@v3
with:
path: ~/.ccache
key: ${{ runner.os }}-ccache-${{ hashFiles('**/*.cpp','**/*.cc','**/*.c', '**/*.h') }}-${{ matrix.compiler || 'gcc' }}
key: ${{ runner.os }}-ccache-${{ hashFiles('**/*.cpp','**/*.cc','**/*.c', '**/*.h') }}
Copy link

Choose a reason for hiding this comment

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

💡 Codebase verification

Cache key strategies should be consistent across jobs

The different cache key strategies between Ubuntu and macOS jobs appear unnecessary as both:

  • Use identical build configurations and ccache settings
  • Don't specify custom compiler settings
  • Run the same build script with identical flags

Consider updating the macOS job to use the same simplified cache key strategy for consistency.

🔗 Analysis chain

LGTM! Simplified cache key configuration.

The removal of compiler-specific cache key should help resolve the cache miss issues. The change looks reasonable as Ubuntu typically uses gcc by default.

However, let's verify if the different cache key strategy between Ubuntu (generic) and macOS (compiler-specific) jobs is intentional:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if different compilers are used in the build process
# Look for compiler configuration in build scripts

echo "Checking build script for compiler settings:"
cat ./etc/script/build.sh

echo -e "\nChecking for compiler-related environment variables in workflow:"
rg "CC=|CXX=" .github/workflows/kiwidb.yml

Length of output: 3122


Script:

#!/bin/bash
# Check matrix configuration and build command usage
echo "Checking matrix and build configurations:"
rg "matrix:" -A 5 .github/workflows/kiwidb.yml

echo -e "\nChecking build command invocations:"
rg "build.sh" -A 2 .github/workflows/kiwidb.yml

echo -e "\nChecking job configurations for compiler settings:"
rg "build_on_(ubuntu|macos):" -A 20 .github/workflows/kiwidb.yml

Length of output: 1703

Copy link
Collaborator

@marsevilspirit marsevilspirit left a comment

Choose a reason for hiding this comment

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

LGTM

@AlexStocks AlexStocks merged commit a71e593 into unstable Jan 20, 2025
4 of 6 checks passed
@AlexStocks AlexStocks deleted the ci_cache branch January 20, 2025 03:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants