for clickhouse, continue even if e2e are failing

[arbiv]

null

Summary by CodeRabbit

• Chores
  • Adjusted workflow to allow integration tests to continue on error for Clickhouse warehouses.

[linear]

ELE-4585 Skip anomaly test for Clickhouse

[coderabbitai]

Walkthrough

A conditional was added to the "Run dbt package integration tests" step in the GitHub Actions workflow. Now, the step will continue on error only if the warehouse-type input is set to 'clickhouse'. A comment explains this is temporary until Clickhouse supports anomaly detection.

Changes

File	Change Summary
.github/workflows/test-warehouse.yml	Added conditional continue-on-error for Clickhouse in integration test step; added explanatory comment.

Poem

In the warren of workflows, a rabbit did see,
Clickhouse errors won’t stop the spree.
With a hop and a skip, “continue-on-error” in tow,
Until anomaly detection has its own glow.
🐇✨

---

📜 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 341545d and 98e4ac8.

📒 Files selected for processing (1)

• .github/workflows/test-warehouse.yml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/workflows/test-warehouse.yml

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

• GitHub Check: code-quality
• GitHub Check: test / test

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this 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.

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.

[github-actions]

👋 @arbiv
Thank you for raising your pull request.
Please make sure to add tests and document all user-facing changes.
You can do this by editing the docs files in this pull request.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

.github/workflows/test-warehouse.yml (2)

159-159: Standardize temporary comment with TODO.

Use a TODO prefix and, if possible, reference an issue or date for removal to make this temporary change trackable.

---

160-160: Remove trailing whitespace.

YAMLlint reports trailing spaces at end of this line. Please delete the extra space after }}.

🧰 Tools

🪛 YAMLlint (1.37.1)

[error] 160-160: trailing spaces

(trailing-spaces)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 66406b0 and 341545d.

📒 Files selected for processing (1)

• .github/workflows/test-warehouse.yml (1 hunks)

🧰 Additional context used

🪛 YAMLlint (1.37.1)

.github/workflows/test-warehouse.yml

[error] 160-160: trailing spaces

(trailing-spaces)

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

• GitHub Check: code-quality
• GitHub Check: test / test