Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support newer Verilator in backwards compatible way #3897

Merged
merged 1 commit into from
May 23, 2024

Conversation

ktbarrett
Copy link
Member

xref #3896.

@ktbarrett ktbarrett requested a review from a team May 16, 2024 17:11
Copy link

codecov bot commented May 16, 2024

Codecov Report

Attention: Patch coverage is 0% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 64.77%. Comparing base (8acffb4) to head (5e1ba3e).

Files Patch % Lines
cocotb/share/lib/vpi/VpiCbHdl.cpp 0.00% 1 Missing ⚠️
Additional details and impacted files
@@              Coverage Diff               @@
##           stable/1.9    #3897      +/-   ##
==============================================
- Coverage       64.79%   64.77%   -0.02%     
==============================================
  Files              49       49              
  Lines            9131     9133       +2     
  Branches         2461     2459       -2     
==============================================
  Hits             5916     5916              
+ Misses           2627     2623       -4     
- Partials          588      594       +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@ktbarrett
Copy link
Member Author

Strange it isn't covering the new line, cocotb_build_libs.py says the define is VERILATOR?

@marlonjames
Copy link
Contributor

marlonjames commented May 17, 2024

Verilator CI isn't being run. You can see it's missing from the output of the generate script.

The Verilator CI changes weren't backported yet.

@ktbarrett ktbarrett added this to the 1.9 milestone May 17, 2024
@ktbarrett
Copy link
Member Author

@marlonjames Do we trust to merge this as is, or should we wait until Verilator CI changes are backported?

Copy link
Contributor

@marlonjames marlonjames left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm okay with this, assuming we don't want to wait and bump the minimum Verilator version for 1.9.

@ktbarrett ktbarrett merged commit a5a1a56 into cocotb:stable/1.9 May 23, 2024
22 of 23 checks passed
@ktbarrett ktbarrett deleted the verilator-writes-1.9 branch May 23, 2024 23:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants