chore:remove taggedFilterSuite

[tchow-zlai]

Summary

Checklist

• Added Unit Tests
• Covered by existing CI
• Integration tested
• Documentation update

Summary by CodeRabbit

• Tests

  • Streamlined several test suites by standardizing their execution without legacy tagging filters.
  • Ensured that core test logic remains consistent while simplifying the test execution process.

• Chores

  • Removed redundant tagging functionalities to reduce complexity and improve test maintainability.
  • Increased test timeout from 900 seconds to 3000 seconds to allow for longer test execution.

[coderabbitai]

Walkthrough

The pull request simplifies test classes by removing the TaggedFilterSuite trait and its associated tagName method from FetcherTest, JoinTest, and MutationsTest. Additionally, the TaggedFilterSuite.scala file has been deleted. Test logic remains unchanged, but tests will no longer be filtered by tags.

Changes

File(s)	Change Summary
spark/.../FetcherTest.scala spark/.../JoinTest.scala spark/.../MutationsTest.scala	Removed TaggedFilterSuite inheritance and deleted the tagName method from each class.
spark/.../TaggedFilterSuite.scala	Deleted the trait that provided tag-based test filtering.
.bazelrc	Updated test timeout from 900 seconds to 3000 seconds.

Sequence Diagram(s)

sequenceDiagram
    participant TR as Test Runner
    participant TS as Test Suite
    TR->>TS: Request test execution
    TS-->>TR: Execute tests (no tag filtering)

Loading

Possibly related PRs

• Tweak spark test setup to tags and run tests appropriately #56: Involved modifications around test tagging, addressing similar filtering mechanisms.
• Bazel migration for spark module #196: Related changes in test structure, focusing on the removal of the tagName method across test classes.

Suggested reviewers

• nikhil-zlai
• piyush-zlai
• kumar-zlai

Poem

Code now flows, unburdened and free,
The tags are gone, as simple as can be.
Tests run clear without any disguise,
Simplified paths light up our skies.
Cheers to clarity in our repository skies!

Warning

Review ran into problems

🔥 Problems

GitHub Actions and Pipeline Checks: Resource not accessible by integration - https://docs.github.com/rest/actions/workflow-runs#list-workflow-runs-for-a-repository.

Please grant the required permissions to the CodeRabbit GitHub App under the organization or repository settings.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between f35eaee and 870e100.

📒 Files selected for processing (1)

• spark/src/test/scala/ai/chronon/spark/test/FetcherTest.scala (2 hunks)

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

• spark/src/test/scala/ai/chronon/spark/test/FetcherTest.scala

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

• GitHub Check: bazel_config_tests
• GitHub Check: spark_tests
• GitHub Check: scala_compile_fmt_fix

---

🪧 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.

[piyush-zlai]

Minor nits, thanks for cleaning up!