Skip to content

Conversation

@superrxan
Copy link

Replace this text with your description here...

Code-Reviewer Section

The general pull request guidelines can be found here.

Please check each of the following things and check all boxes before accepting a PR.

  • The PR has a description, explaining both the problem and the solution.
  • The description mentions which forms of testing were done and the testing seems reasonable.
  • Every function/class/actor that was touched is reasonably well documented.

For Release-Branches

If this PR is made against a release-branch, please also check the following:

  • This change/bugfix is a cherry-pick from the next younger branch (younger release-branch or main if this is the youngest branch)
  • There is a good reason why this PR needs to go into a release branch and this reason is documented (either in the description above or in a linked GitHub issue)

Copy link
Contributor

@jzhou77 jzhou77 left a comment

Choose a reason for hiding this comment

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

This workload does very simple read and write. Why do we need this new one? The existing workloads should already capture the functionality, e.g., CycleWorkload.

@superrxan
Copy link
Author

sorry, I just start learning the DST, want porting it to our own code. this is just a test.

@jzhou77
Copy link
Contributor

jzhou77 commented Dec 11, 2025

sorry, I just start learning the DST, want porting it to our own code. this is just a test.

No worries. Since the intent is not to merge the PR, I'll convert it to draft and you can close it when your test is over.

@jzhou77 jzhou77 marked this pull request as draft December 11, 2025 16:48
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.

2 participants