tool version for CI runs and nix dev setup
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- build-system, ci-cd
Research direction
Start by comparing the tool versions used in the nix package with those used by the nightly and weekly CI runs, then inspect the generated reports linked in the issue. Done means the CI reports identify the Xcelium and VCS versions, the nix and CI versions are aligned, and the publication or internal-visibility decision is resolved.
Written by the indexing model from the issue text.
Description
While I was debugging flash_controller I noticed that CI doesn't run the same tool version than what we were using locally through the nix package.
I think it would be nice to:
- report the toolversion of xcelium and VCS in the nightly/weekly runs (e.g. here
XCELIUM-23.09.002instead of justXCELIUM) - align the version of nix and CI
@machshev @mkj121
I'm not sure if we are allowed to publish the exact tool version. If not, is there a way to make this information available internally?
- Dominant language
- Python
- Stars
- 14
- Forks
- 21
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lowRISC/dvsim
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Better log visibility on the license type usage profilePossibly taken @AlexJones0 claimed this 6 days ago. Open
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 75/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 3 days
-
Negation with "not" and "no" is ignored during sentiment analysisPossibly taken @vivek-3728 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
techcsispit/mess-mood#11 · 1 comment ·
-
changelog investigate
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ramnes/notion-sdk-py#408 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
btclib-org/btclib-wallet#267 ·
Maintainers usually reply within 1 day
-
good first issue tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
knnmelprop/YAADO#111 ·