This PR focuses on cleaning up the integration tests. With this PR we cover packages operations, examples operations, and build/test/lint/report for ice40 and ecp5.
As part of the cleanup, the various paio text fixtures where consolidate into one called apio_runner which makes it easy to add new functionality and allows to wrap apio invocation with test code (e.g. to avoid extended PATH propogation from one test to the next).
Caveats:
We need a gowin test example apio-examples that has a testbench (similar to Alhambra II / ledon) so we can extend the project tests to gowing.
Apio doesn't handle well spaces in packages directory so the tests do not cover it (unicode is ok and is covered). I created an issue for this https://github.com/FPGAwars/apio/issues/474 and added a check that causes apio to exist with an error message if a home, packges, or project directory contains a white space.
This PR focuses on cleaning up the integration tests. With this PR we cover packages operations, examples operations, and build/test/lint/report for ice40 and ecp5.
As part of the cleanup, the various paio text fixtures where consolidate into one called apio_runner which makes it easy to add new functionality and allows to wrap apio invocation with test code (e.g. to avoid extended PATH propogation from one test to the next).
Caveats: