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

Update dependency edu.berkeley.cs:chiseltest to v0.6.2 #10

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 23, 2024

This PR contains the following updates:

Package Type Update Change
edu.berkeley.cs:chiseltest (source) test minor 0.3.2 -> 0.6.2

Release Notes

ucb-bar/chisel-testers2 (edu.berkeley.cs:chiseltest)

v0.6.2: ChiselTest v0.6.2

Compare Source

Highlights

  • [new in 0.6.2] add support for Opaque types in peek poke tester (#​667)
  • [new in 0.6.1] add support for Opaque types (#​661)
  • Bump to Chisel v3.6.0
    • Note: ChiselTest only supports the Scala FIRRTL Compiler (SFC)
  • Add support for bitwuzla solver (#​545)
  • Support zero-width data (#​552)

Other Changes

  • Remove Icarus debug messages (#​607)
  • RawTester.test now accepts a testname (#​533)
  • Update utest to 0.8.1 (#​554)
  • upgrade scalatest version to 3.2.15 (#​599)

On Maven

v0.6.1: ChiselTest v0.6.1

Compare Source

Highlights

  • [new in 0.6.1] add support for Opaque types (#​661)
  • Bump to Chisel v3.6.0
    • Note: ChiselTest only supports the Scala FIRRTL Compiler (SFC)
  • Add support for bitwuzla solver (#​545)
  • Support zero-width data (#​552)

Other Changes

  • Remove Icarus debug messages (#​607)
  • RawTester.test now accepts a testname (#​533)
  • Update utest to 0.8.1 (#​554)
  • upgrade scalatest version to 3.2.15 (#​599)

v0.6.0: ChiselTest v0.6.0

Compare Source

Highlights

  • Bump to Chisel v3.6.0
    • Note: ChiselTest only supports the Scala FIRRTL Compiler (SFC)
  • Add support for bitwuzla solver (#​545)
  • Support zero-width data (#​552)

Other Changes

  • Remove Icarus debug messages (#​607)
  • RawTester.test now accepts a testname (#​533)
  • Update utest to 0.8.1 (#​554)
  • upgrade scalatest version to 3.2.15 (#​599)

v0.5.6: ChiselTest v0.5.6

Compare Source

Feature

  • Allow patched versions of Verilator (#​582)

BugFix

  • Fix issues in IPCSimulatorContext (VCS) simulations (#​570)
  • partialPoke/Expect: add more tests, improve implementation (#​589)
  • VCS Q-2020.03 (at least) fails because it can't find nullptr (#​572)
  • Remove quotes around VcsCFlags (#​574)
  • vcs: fix vpd generation (#​610)
  • Delay first rising clock edge by 1 half-period in VPI Harness (#​591)

v0.5.5

Compare Source

v0.5.4: ChiselTest v0.5.4

Compare Source

Feature

  • ChiselEnum: implement peek and better error message (#​542)
  • added +plusarg support for Icarus (#​531)

BugFix

v0.5.3

Compare Source

v0.5.2

Compare Source

v0.5.1: ChiselTest v0.5.1

Compare Source

Feature

  • Scala type peek poke (#​480)
    You can now more easily peek and poke with Scala values, eg. myUInt.poke(100) and myUInt.peekInt()

BugFix

  • formal: test non power of two memories and fix replay bug (#​490)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/edu.berkeley.cs-chiseltest-0.x branch from cbc1cbe to ab55efa Compare April 12, 2024 03:55
@renovate renovate bot changed the title Update dependency edu.berkeley.cs:chiseltest to v0.6.1 chore(deps): update dependency edu.berkeley.cs:chiseltest to v0.6.1 May 5, 2024
@renovate renovate bot changed the title chore(deps): update dependency edu.berkeley.cs:chiseltest to v0.6.1 Update dependency edu.berkeley.cs:chiseltest to v0.6.1 Jul 7, 2024
@jyrj jyrj force-pushed the renovate/edu.berkeley.cs-chiseltest-0.x branch from ab55efa to 91f70b1 Compare September 24, 2024 21:59
Copy link

coderabbitai bot commented Sep 24, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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.

@renovate renovate bot force-pushed the renovate/edu.berkeley.cs-chiseltest-0.x branch from 91f70b1 to 0a97de3 Compare September 24, 2024 23:57
@renovate renovate bot changed the title Update dependency edu.berkeley.cs:chiseltest to v0.6.1 Update dependency edu.berkeley.cs:chiseltest to v0.6.2 Sep 24, 2024
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.

0 participants