lowRISC / lowRISC/opentitan

[bazel] Re-factor `test_dispatch` functions

Open
#19,908 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Earlgrey-PROD Triaged Priority:P2 SW:Build System Type:Task
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

Currently there is quite a bit of duplicated logic among the different test_dispatch functions. Refactor into common logic.

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

Search the repository for the Bazel-related `test_dispatch` functions and compare their duplicated logic. Identify the common behavior to consolidate, then verify the Bazel test targets still pass and that the separate dispatch functions retain their expected behavior.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, testing
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.