lowRISC / lowRISC/opentitan

[bazel] verilator rebuilds too often

Open
#9,653 7 comments 0 reactions 2 assignees View on GitHub

@timothytrippel is already working on this.

Since Sep 28, 2022.

Component:Tooling Priority:P2 Type:Enhancement
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

Something is causing the verilated model to rebuild while I'm working on the verilator tests. It's slow and inconvenient. I think the system is just trying not to use all the memory on a workstation and clearing it from the cache.
Until we set up a remote cache it might be worthwhile to use a disk cache by running bazel with a `--disk_cache=~/some_cache` arg, which is a nice thing to put in a .bazelrc for now.

Sometimes we also appear to build the verilated model for tests that shouldn't depend on it. Because this affects the cw310 tests it's going to impact our CI if we build those tests on the system that runs them.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.