Lars Asplund
Lars Asplund
Considering that the SourceRank based on the package is calculated differently than the SourceRank calculated based on the repository we should maybe consider some differentiation. For example call it RepoSourceRank...
@sibeov Since you're not looking into re-running a set of failing tests as outlined in #740 you can simply do ``` console python run.py --fail-fast ``` It stops on the...
@JimLewis With the current interface one would have to make one call for each output. Given that we working on the lowest level with little data transformation it shouldn't be...
@JimLewis I had a look at handling logging hierarchies. VUnit includes the hierarchy in the log, for example ``` console 0 fs - top:bottom - INFO - Hello from VUnit...
@JimLewis WRT to %%. You would always pass the prefix as one of the nameless parameters to `write_to_log`. It will then be up to the third party implementation to decide...
@JimLewis @umarcor I think we're starting to fall into the trap of being over-ambitious in the first step (me included). My goal is to: 1. Have **all** logs from framework...
Looks good from my point of view. The only alternative solution I can come to think of is to push an extra dummy "token" into the queue after the request...
vhdl_parser.py: components should not be converted to lower-case while instantiating Verilog modules
As a workaround you can either change the Verilog name to lowercase or you can use the [add_dependency_on](http://vunit.github.io/py/vunit.html?highlight=add_dep#vunit.ui.source.SourceFile.add_dependency_on) method to enforce a correct compile_order.
vhdl_parser.py: components should not be converted to lower-case while instantiating Verilog modules
The problem is that we have a potential dependency error today and a potential "same name" error with your suggested solution (I recall people actually using the case sensitivity in...
vhdl_parser.py: components should not be converted to lower-case while instantiating Verilog modules
I cannot speak for FuseSOC but in general there will always be cases not supported by the standard flow of tools and there is a need for the frontend tools...