Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Erroneous cyclic dependency when using VHDL configurations

Aperta
  • Qualcosa non va?
#1,183 5 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Ambito
testing-qa

Direzione di ricerca

Start with the attached MVP project, especially the VHDL files showing the tb_top and testcase_top component and configuration relationship, then trace how VUnit builds dependencies for VHDL configurations. Compare it with vhdl_configuration and tb_selecting_test_runner_with_vhdl_configuration.vhd, where the configuration is in a separate file. Done means the reported false circular dependency is handled for the attached setup; the issue does not name a test to run.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Hello,

we're using VHDL configurations in our Simulation Setup. With the current VUnit-5.0.0.dev10 this Setup fails with this error:

Re-compile not needed

Traceback (most recent call last):
  File "C:\Python311\Lib\site-packages\vunit\ui\__init__.py", line 737, in main
    all_ok = self._main(post_run)
             ^^^^^^^^^^^^^^^^^^^^
  File "C:\Python311\Lib\site-packages\vunit\ui\__init__.py", line 783, in _main
    all_ok = self._main_run(post_run)
             ^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Python311\Lib\site-packages\vunit\ui\__init__.py", line 1055, in _main_run
    self._run_test(test_list, report, simulator_if)
  File "C:\Python311\Lib\site-packages\vunit\ui\__init__.py", line 1233, in _run_test
    latest_dependency_updates = self._get_latest_dependency_updates()
                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Python311\Lib\site-packages\vunit\ui\__init__.py", line 890, in _get_latest_dependency_updates
    source_files_in_order = self._dependency_graph.toposort()
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Python311\Lib\site-packages\vunit\dependency_graph.py", line 35, in toposort
    self._visit(
  File "C:\Python311\Lib\site-packages\vunit\dependency_graph.py", line 103, in _visit
    visit(node)
  File "C:\Python311\Lib\site-packages\vunit\dependency_graph.py", line 90, in visit
    visit(other_node)
  File "C:\Python311\Lib\site-packages\vunit\dependency_graph.py", line 90, in visit
    visit(other_node)
  File "C:\Python311\Lib\site-packages\vunit\dependency_graph.py", line 90, in visit
    visit(other_node)
  [Previous line repeated 2 more times]
  File "C:\Python311\Lib\site-packages\vunit\dependency_graph.py", line 83, in visit
    raise CircularDependencyException(path_ordered[start:] + [node])
vunit.dependency_graph.CircularDependencyException

This circular dependency is caused by the following construct:
tb_top instantiates testcase_top via component instantiation. testcase_top is split in a file for the enitity and multiple files with different architectures. There is one architecture per file with individual names (the testcases themself). In the architecture file is the needed configuration for the testcase_top instantiation aswell. This is the cause of the apparently false circular dependency. tb_top -> testcase_top -> tb_top.

In the provided example vhdl_configuration -> tb_selecting_test_runner_with_vhdl_configuration.vhd this behaviour does not occur. In this example the configuration is in a separate file (test_reset_behavioral.vhd) and the circular dependency error does not occur.
Sadly this is a worse solution due to the need to edit two files when adding a testcase.

What is the intended behaviour?

I have attached a MVP project displaying the described behaviour.

tb_dff.zip

Thank you for your help and Kind Regards,
~ Raik

Lingua principale
VHDL
Stelle
850
Fork
305
Merge medio
2g 10h
PR unite (30g)
7

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di VUnit/vunit

Tutte le issue di VUnit/vunit

Issue simili

Altre issue su Testing & QA

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.