lowRISC / lowRISC/opentitan

[scripts] Stream Bazel logs in alert classification validation script

Open
#28,600 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

As a general comment (I don't think it needs to be addressed for this PR to be merged, just would be nice to have): Bazel can sometimes take a long time (e.g. a cold build of OpenTitanTool), it would be nice if these Bazel logs could be streamed as well as captured so that the user knows that something is still going on and the script hasn't locked up.

But I'm aware that will require hacking around with e.g. subprocess.Popen and manually handling the different streams, so may be more effort than it's worth at the moment 😅

Originally posted by @AlexJones0 in https://github.com/lowRISC/opentitan/pull/28303#discussion_r2477554679

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 with the alert classification validation script and locate the Bazel invocation that currently captures its output. Check how its subprocess streams are handled; done means Bazel logs remain captured for validation while also being streamed so users can see progress during long builds.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system
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.