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

Move TestHarness to chipyard.harness, make chipyard/harness directory #1463

Merged
merged 2 commits into from
May 9, 2023

Conversation

jerryz123
Copy link
Contributor

@jerryz123 jerryz123 commented May 8, 2023

This is done to ease in upcoming work around new harness-level APIs.

Related PRs / Issues:

Type of change:

  • Bug fix
  • New feature
  • Other enhancement

Impact:

  • RTL change
  • Software change (RISC-V software)
  • Build system change
  • Other

Contributor Checklist:

  • Did you set main as the base branch?
  • Is this PR's title suitable for inclusion in the changelog and have you added a changelog:<topic> label?
  • Did you state the type-of-change/impact?
  • Did you delete any extraneous prints/debugging code?
  • Did you mark the PR with a changelog: label?
  • (If applicable) Did you update the conda .conda-lock.yml file if you updated the conda requirements file?
  • (If applicable) Did you add documentation for the feature?
  • (If applicable) Did you add a test demonstrating the PR?
  • (If applicable) Did you mark the PR as Please Backport?

Copy link
Contributor

@abejgonzalez abejgonzalez left a comment

Choose a reason for hiding this comment

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

SFTM

docs/Advanced-Concepts/Harness-Clocks.rst Outdated Show resolved Hide resolved
Co-authored-by: Abraham Gonzalez <abe.j.gonza@gmail.com>
@jerryz123 jerryz123 merged commit 8b805ac into main May 9, 2023
5 checks passed
@jerryz123 jerryz123 deleted the harness-dir branch May 9, 2023 01:17
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.

None yet

2 participants