* First working yml for github actions
* Remove redundant lines
* Test with building ghdl from source
* Re-enable all versions of python
* Re-enable all versions of python
* python-3.11 not available yet
* Add weekly cron on Sunday
Co-authored-by: Douglas Kastle <douglas.kastle@gmail.com>
* palce xfail on rename_after ... test
* Adding a commmnet to force commit
* alternate approach in testOBufInterface
* reverting _analyze.py
reaming the simulation objects
* typos
* final commit to 'finish' PR submission
* And of course I forgot the 'xfail'
* cleaning up wild import in test_tristate.py to provoke another Travis/CI run
* There is something wrong with the 'xfail' so I just commented out the offender
* uncommented the second test in test_tristate.py
* Changed the object names in the testbench, hoping to narrow down where it fails
* Changing more object names
* myhdl.c: added #ifdef _WIN32 clause to get the pipes working in WIndows 10, properly (auto-)formatted the source
util.py: changed the myhdl.vpi path to defaukt to iverilog's known system path
test_tristate.py: the TestTristate class re-used the tristate_obuf.o for the test with the interface; which put iverilog on the wrong foot ...
* util.py: make a distinction between Windows and Linux systems where to get myhdl.vpi
https://docs.pytest.org/en/latest/yieldfixture.html
> Since pytest-3.0, fixtures using the normal fixture decorator can use a yield statement to provide fixture values and execute teardown code, exactly like yield_fixture in previous versions.
>
> Marking functions as yield_fixture is still supported, but deprecated and should not be used in new code.
Fixes in _verify.py:
- change VHDL run command to work with mcode backend and supress metavlue warnings
- added missing args/kwargs parameter passing in VerficationClass
Testcases:
Additional test init_reset_tb in conversion/general/test_initial_values.py to verify correct assisgnment of init values
in @always_seq processes with a reset
* Added test which triggers 'Part select expressions must be constant.' error message
* Added ability to make a +: operator
* Removed unnecessary print statement from test
* Changed verify to analyze
