lowRISC / lowRISC/opentitan

[CI] Make Verilator lint failures fail CI

Open
#2,314 0 comments 0 reactions 0 assignees View on GitHub
Component:Tooling Earlgrey-PROD Candidate Type:Enhancement
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

We should maintain a code base which is Verilator lint-clean. Add a CI check to ensure that's the case.

This will prevent problems like #2313 when vendoring in new versions of the primitives into Ibex (where Verilator lint warnings are fatal).

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or CI entry points. Start by locating the repository's CI configuration and the existing Verilator lint invocation; the work is done when a Verilator lint failure causes CI to fail and a lint-clean code base passes.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, ci-cd
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.