vmware / vmware/splinterdb

`test_data_message_to_string` and other key/message printing need some love

Open
#148 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
732
Forks
67
PR merge metrics
No merged PRs in 30d

Description

These functions don't adapt to the tests run and can lead to some incorrect printing of the keys and messages.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating test_data_message_to_string and the related key/message-printing functions in the C test code. Review how the tests are run and compare the current printed keys and messages with the expected test-specific output; done means the diagnostics adapt to the tests and no longer print incorrect values.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.