Remove copyright notice from tests

[jan-janssen]

Summary by CodeRabbit

• Chores
  • Removed metadata comments and author information from multiple test files to streamline code readability.
  • No changes were made to the functionality or logic of the tests.

[coderabbitai]

Walkthrough

The changes involve the removal of metadata comments and author information from the top of multiple test files in the repository. This includes coding declarations, copyright notices, author details, versioning information, maintainer details, email addresses, statuses, and dates. The remaining content in each file consists primarily of import statements and class definitions, with no alterations to the functionality of the tests themselves.

Changes

Files	Change Summary
tests/test_basic.py, tests/test_flux.py, tests/test_gent.py, tests/test_lsf.py, tests/test_moab.py, tests/test_multi.py, tests/test_remote.py, tests/test_sge.py, tests/test_slurm.py, tests/test_torque.py	Removal of metadata comments including coding declarations, copyright notices, author information, and other related details from the top of the files. The functionality of the tests remains unchanged.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant TestSuite
    participant TestCases

    User->>TestSuite: Run tests
    TestSuite->>TestCases: Execute test cases
    TestCases-->>TestSuite: Return results
    TestSuite-->>User: Display results

Loading

Poem

In the code where rabbits play,
Metadata hopped away,
Clean and clear, the tests now stand,
Ready for the next command.
With each import, a joyful cheer,
Hopping forward, never fear! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 043358c and f83ba5b.

📒 Files selected for processing (10)

• tests/test_basic.py (0 hunks)
• tests/test_flux.py (0 hunks)
• tests/test_gent.py (0 hunks)
• tests/test_lsf.py (0 hunks)
• tests/test_moab.py (0 hunks)
• tests/test_multi.py (0 hunks)
• tests/test_remote.py (0 hunks)
• tests/test_sge.py (0 hunks)
• tests/test_slurm.py (0 hunks)
• tests/test_torque.py (0 hunks)

💤 Files not reviewed due to no reviewable changes (10)

• tests/test_basic.py
• tests/test_flux.py
• tests/test_gent.py
• tests/test_lsf.py
• tests/test_moab.py
• tests/test_multi.py
• tests/test_remote.py
• tests/test_sge.py
• tests/test_slurm.py
• tests/test_torque.py

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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